Case 42A412 · Identity & AD · L3 Applied
Same Session, Two Countries
Live alertEntra ID Protection raises "Anomalous token" for j.patel at 10:14. Sign-in logs show one session ID used from the office IP at 09:31 and from a VPS abroad at 10:12, MFA "satisfied by claim in the token".
- 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:
- Likely AiTM: a phishing proxy captured the post-MFA session cookie, so the attacker never needed a password or a prompt
- Impact: whatever the session reaches; check for inbox rules, new MFA methods, OAuth consents and outbound BEC mail
- Contain: revoke all sessions and refresh tokens explicitly, reset the password, disable the user if abuse is active
- Scope: find the lure and every other recipient who clicked, using the proxy domain in mail and web proxy logs
- Prevent: phishing-resistant MFA, compliant-device Conditional Access and token protection make replayed cookies fail
If the interviewer pushes back
- Which Conditional Access controls would have made the stolen cookie useless, and what would each one break?