From a public finding to an internal decision
A document on an old campaign site may still identify a former employee as a current contact. We record where the document appeared and what it showed. Your team confirms ownership and decides whether to update the document, retire the site or accept the exposure.
What should a company include after an acquisition?
Start with a list of business names, public domains and approved owners. A legacy customer portal may still receive traffic after a rebrand. Establish who owns the domain and handles customer requests before deciding whether to retire it, redirect it or assign someone to maintain it.
What an external attack surface assessment delivers
A useful inventory connects every exposed asset to an accountable owner. A legacy login page may belong to the acquired business, a hosted platform or an outside supplier. Record what is publicly visible, who can authorize a correction and how to verify that the intended change occurred. Confirm scope before any technical testing. A public-facing inventory alone cannot establish that a system is vulnerable.
When to move from an assessment to continuous monitoring
A single assessment records what the review found at a particular time. Ongoing monitoring is useful when domains, vendors or public services change often. Compare new observations with the approved inventory, investigate changes with the owner and close out items that have been retired. A duplicate finding should not create a second remediation task.
Define the public scope
Agree which domains, brands and executive profiles are included before the review starts.
Triage the evidence
Give the team enough context to verify each finding and decide who should handle it.
Define the boundary of the review
Confirm which company names, public sites and executive profiles belong in scope. Shared service providers and former brands should be identified before the work begins. Once the initial findings are prioritized, continuous watch can focus on the changes that matter.