Case 2A8718 · Identity & AD · L3 Applied

Conditional Access Design

Practise as: Deep diveLevel: L3 Applied
  1. 01 Context
  2. 02 Mechanism
  3. 03 Lessons
What a strong answer covers

Try it out loud first. Then check yourself:

  1. Entra Conditional Access is an if-then engine run at token issuance: signals in, then block, grant or session controls
  2. Signals: user, app, device platform and compliance, location, client app, sign-in and user risk; block always wins
  3. Common gaps: broad exclusions, legacy auth left open, device code flow allowed, policies stuck in report-only
  4. Baseline: MFA for all, phishing-resistant MFA for admins, block legacy auth, compliant device for sensitive apps
  5. Lessons: existing tokens live until expiry unless CAE applies; test with What If; keep two monitored break-glass accounts

If the interviewer pushes back

  • A user passes Conditional Access on a compliant laptop, then the token is stolen. Which features limit replay, and how far?

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