A public record and a candidate asset
A fictional tester is permitted to review public third-party records for an organization before an active-testing window. A certificate-transparency entry contains a development hostname, and an old search result associates it with a cloud service. The current project asset list does not include that hostname or provider account. A colleague wants to launch a version scan immediately because the name contains the client’s brand. The tester also observes a generic provider error when reviewing a supplied historical screenshot, but has no evidence that the actual resource can be claimed or that the hostname still belongs to the client. The exercise asks for a qualified reconnaissance conclusion and the next authorization step. It does not authorize contacting the host, registering a resource or testing takeover.
1. What is supported by the public observations?
Read the worked answer
They identify a candidate name and historical association for further investigation. They do not establish current ownership, authorization, exposure or a confirmed claimable takeover condition.
2. What should happen before active validation?
Read the worked answer
Record the source, time and uncertainty, confirm ownership and the actual approved scope through the engagement channel, and determine which additional checks are authorized under the applicable provider conditions.