Confidential Technology Company
External Attack Surface Assessment
Sanitized case study — client details withheld for confidentiality.
The ask.
The client had grown quickly through acquisitions and internal product launches and, candidly, didn’t have a full inventory of what they exposed to the internet. They wanted an outside-in view — what would a real attacker see before ever touching a login page?
Approach.
Passive and active reconnaissance across the client’s domain and subdomain footprint (certificate transparency logs, DNS enumeration, ASN mapping, historical DNS records), followed by service fingerprinting on every live host and a manual review of cloud storage exposure and remote-access portals (VPN gateways, admin panels, forgotten staging environments).
What we found.
Two forgotten staging environments running outdated application versions with known CVEs and default credentials still active; an exposed internal admin panel with no IP allowlisting; and a misconfigured cloud storage bucket containing internal build artifacts and configuration files with embedded (non-production, but still sensitive) API keys.
Expired TLS certificates on legacy subdomains, exposed version banners revealing outdated software, an open remote management port on a legacy host, and several subdomains still pointing to decommissioned third-party services (a dangling DNS / subdomain takeover risk).
DNS hygiene issues (missing SPF/DMARC hardening), verbose HTTP headers, and informational service banners.
Why it mattered.
None of these were individually catastrophic — but taken together they represented exactly the kind of forgotten, unmanaged infrastructure that attackers specifically hunt for because it’s overlooked by internal teams who only monitor production. The dangling subdomain finding in particular is a classic pivot point for phishing infrastructure.
Outcome.
We delivered a prioritized asset inventory alongside the findings — many clients get more long-term value from knowing what they own than from the vulnerabilities themselves. The client used this to formalize a quarterly external attack surface review process.
Similar exposure in your environment?
This engagement began with a conversation about scope. Start yours the same way.