Case 6B8127 · Cloud · L2 Practitioner
Subdomain Takeover
- 01 What is it?
- 02 How is it abused?
- 03 How do you stop it?
What a strong answer covers
Try it out loud first. Then check yourself:
- A DNS record still points at a deleted cloud resource: S3 website bucket, Azure App Service name, or released public IP
- Attacker claims the same name or gets the IP reassigned, then serves their content on your subdomain
- Impact: convincing phishing, cookies scoped to the parent domain, and abuse of CORS or CSP allowlists that trust *.you.com
- Stop: remove DNS before deprovisioning, use alias records, and continuously diff DNS against live resources
- Provider controls help, such as Azure App Service domain verification TXT records, but only inventory closes the gap
If the interviewer pushes back
- Why is a takeover worse when the parent site sets session cookies with Domain=.example.com?