Case F6271B · Network · L3 Applied
Our Mail Domain Moved Overnight
Live alertYour Certificate Transparency monitor flags a new Let's Encrypt cert for mail.example-corp.com issued at 03:20 UTC. Public DNS now resolves mail to 198.51.100.23, and the registrar log shows an NS change from an unknown IP.
- 01 What happened?
- 02 What is the impact?
- 03 What do you do?
What a strong answer covers
Try it out loud first. Then check yourself:
- DNS infrastructure hijack: registrar or DNS provider account compromised, records repointed, valid cert issued via DV
- Impact: users and mail servers connect to an attacker proxy with a trusted cert, harvesting credentials and email
- Respond: regain the registrar account, revert NS and records, revoke rogue certs, reset creds used during the window
- Scope: lower TTLs do not undo caching; check which records changed, for how long, and logins from captured accounts
- Prevent: MFA and registry lock at the registrar, CAA records, CT and DNS change monitoring, as CISA ED 19-01 urged
If the interviewer pushes back
- Would DNSSEC have prevented this attack? Explain why or why not.