Case 42A412 · Identity & AD · L3 Applied

Same Session, Two Countries

Practise as: Incident drillLevel: L3 Applied

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".

  1. 01 What happened?
  2. 02 What is the impact?
  3. 03 What do you do?
What a strong answer covers

Try it out loud first. Then check yourself:

  1. Likely AiTM: a phishing proxy captured the post-MFA session cookie, so the attacker never needed a password or a prompt
  2. Impact: whatever the session reaches; check for inbox rules, new MFA methods, OAuth consents and outbound BEC mail
  3. Contain: revoke all sessions and refresh tokens explicitly, reset the password, disable the user if abuse is active
  4. Scope: find the lure and every other recipient who clicked, using the proxy domain in mail and web proxy logs
  5. 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?

Go deeper

More Identity & AD cards

All Identity & AD cards →

cardosec draws a security topic and gives you a clock: explain it out loud with no notes, then see what you covered and what you missed. Free during early access.

Reviewed 2026-10-09