Case 0398ED · Identity & AD · L2 Practitioner

Device Code Phishing

Practise as: Explain itLevel: L2 Practitioner
  1. 01 What is it?
  2. 02 How is it abused?
  3. 03 How do you stop it?
What a strong answer covers

Try it out loud first. Then check yourself:

  1. Device authorization grant (RFC 8628): an input-limited device shows a code, the user enters it on a verification page
  2. Abuse: attacker starts the flow, sends the victim the code with a pretext, then polls and receives the tokens
  3. Victim signs in on the real IdP domain with real MFA, so URL checks and even passkeys do not stop it
  4. Attacker gets access and refresh tokens; the refresh token gives persistence until it is revoked
  5. Stop: block device code flow via Conditional Access except for named needs; hunt sign-ins with protocol deviceCode

If the interviewer pushes back

  • Why does phishing-resistant MFA fail here when it stops AiTM proxies, and what control actually closes the gap?

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