Guide Cybersecurity

Defending against MFA bypass: session controls, priority accounts and token theft response

Phishing-resistant sign-in closes one route, but stolen sessions need controls of their own. This guide covers session-layer defences in Microsoft Entra ID, which accounts to protect first, seven controls to implement now and how to respond to suspected token theft.

18 November 2026
6 min read
Key takeaways
  • Device compliance is checked when a token is issued; it does not stop a stolen token being replayed from another machine. Token Protection binds sign-in sessions to the device for supported apps and platforms.
  • Continuous Access Evaluation lets supported services such as Exchange Online, SharePoint Online and Teams act on critical events without waiting for the access token to expire.
  • Start with the accounts that carry the most access: administrators, finance staff and board members can move to phishing-resistant MFA in days.
  • Treat suspected token theft as an incident: revoke sessions, contain the identity, check the device for infostealers and remove anything the attacker left behind.

This page covers the defences against MFA bypass: session-layer controls, the accounts to protect first, seven controls to implement and what to do if you suspect token theft. For how AiTM phishing, session theft and consent phishing work and what each MFA type stops, see how attackers get around MFA. Rolling out and configuring MFA itself is covered in our MFA rollout guide.

Defending against session-layer attacks

Session token theft happens after authentication. The controls that matter here act on how tokens are issued, bound, evaluated and revoked, not on the login itself.

Token Protection: binding sessions to a device

Conditional Access device compliance checks the device when a token is issued. It does not bind the resulting session token or cookie to that device, so a token stolen from a compliant laptop can often be replayed from another machine. Microsoft's separate Token Protection session control addresses this: it requires device-bound sign-in session tokens, so a stolen token cannot be used from a different device. Coverage is limited. It applies to supported native apps on Windows and on managed macOS and iOS devices, for resources such as Exchange Online, SharePoint Online and Teams. Browser support is in preview for a narrow set of apps. It requires Entra ID P1 and has its own device registration requirements. Pilot it in report-only mode, and pair it with policies that block unknown platforms and require compliant devices.

Continuous Access Evaluation

CAE lets supported services such as Exchange Online, SharePoint Online and Teams respond to certain critical events without waiting for the access token to expire: an account disabled or deleted, a password changed or reset, an administrator revoking sessions, or high user risk flagged by ID Protection. It can also enforce IP-based location policies when the network location changes. Microsoft notes that event propagation can take up to 15 minutes. CAE is not universal. It depends on the client and service supporting it, and it does not detect or cancel every stolen token on its own.

Token lifetimes and sign-in frequency

Shortening token lifetimes across the board trades user friction for limited gain. Microsoft itself found that reduced lifetimes hurt experience and reliability without removing the risk. A targeted Conditional Access sign-in frequency policy for sensitive apps and admin portals is more useful, alongside the controls above.

Monitoring for token anomalies

Watch for sessions that suddenly appear from unfamiliar locations, infrastructure or devices shortly after a normal login. Microsoft Entra ID Protection surfaces risky sign-in detections such as anomalous token use and atypical travel, and Microsoft Sentinel or Defender XDR can correlate them with endpoint alerts. Connect high-confidence detections to automated responses: session revocation, forced re-authentication, or an alert to the security team.

Start with privileged accounts

Phishing-resistant MFA delivers its highest value on the accounts that carry the most access. Administrative accounts, elevated service accounts, finance staff and board members make up a small fraction of your users but account for most of the damage a successful credential attack can do.

Rolling out FIDO2 across a large organisation takes time: device distribution, user training, policy rollout. The 20 accounts that matter most can be covered in days. Start with Conditional Access policies requiring phishing-resistant authentication for privileged role access, and use PIM so administrative roles are activated only when needed rather than sitting permanently active.

TOTP-protected admin accounts are a high-value target in AiTM campaigns. The credential, the MFA code and the session token all pass through the same proxy. FIDO2 breaks that chain at sign-in: the credential is scoped to the real site, so the phishing domain gets nothing it can use.

Seven controls to implement now

  • Keep number matching on and tune push MFA: it is on by default in Microsoft Authenticator; add app and location context and alert on repeated denied prompts.
  • Block legacy authentication protocols: older protocols with basic authentication, such as POP, IMAP and SMTP AUTH, cannot enforce MFA and remain a common credential stuffing path where still enabled.
  • Enforce phishing-resistant MFA for privileged accounts: Conditional Access authentication strengths can require FIDO2 passkeys, Windows Hello for Business or certificate-based authentication for admin roles.
  • Enable Microsoft Entra ID Protection risk policies: sign-in and user risk policies, leaked credential detection and automated remediation.
  • Configure CAE and pilot Token Protection: CAE for critical events on supported apps; Token Protection for supported native apps on registered devices.
  • Restrict OAuth application consent: limit user consent to verified publishers and low-risk permissions, turn on the admin consent workflow, and review existing grants.
  • Monitor and respond to anomalous sessions: alert on risky sign-ins and unfamiliar devices, and connect high-confidence alerts to automatic session revocation.
Licensing check

Conditional Access, authentication strengths and Token Protection require Microsoft Entra ID P1, which is included in Microsoft 365 Business Premium and Microsoft 365 E3. Risk-based policies in Microsoft Entra ID Protection need Entra ID P2 (included in Microsoft 365 E5), and Privileged Identity Management needs Entra ID P2 or Microsoft Entra ID Governance. Token Protection also has its own platform, app and device registration requirements. Check what you hold before you plan the rollout.

What to do if you suspect session token theft

Treat suspected token theft as an incident, not just a password reset. A sensible sequence:

  1. Confirm what happened. Review interactive and non-interactive sign-in logs, risk detections, new OAuth consents and audit events for the account.
  2. Revoke sessions and refresh tokens. Revoke the user's sign-in sessions in Entra ID. Access tokens already issued can stay valid briefly, until they expire, in apps that do not support CAE.
  3. Contain the identity. Where justified, disable or restrict the account and reset its credentials, including any authentication methods the attacker may have touched.
  4. Investigate the endpoint. Check the user's device for infostealers and persistence. If malware took the token, reset again once the device is clean.
  5. Look for what the attacker left behind. Review OAuth grants, mailbox rules and forwarding, and any newly registered authentication methods or devices.
  6. Restore access and monitor. Restore access from a trusted device, re-register strong methods, and watch the account closely for renewed activity.
Ryland Deakin
About the author
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile

Common questions

Does FIDO2 stop session theft?

No. FIDO2 resists phishing during authentication, but it does not protect the session after a legitimate login. If an infostealer copies the session cookie from the user's browser, the attacker can replay it without ever touching the passkey. Session theft needs separate controls: endpoint protection, Token Protection where supported, CAE, and fast detection and revocation.

How do I enforce phishing-resistant MFA in Microsoft 365?

In the Microsoft Entra admin center, enable passkeys (FIDO2) under Authentication methods for the users in scope. Then create a Conditional Access policy with the Require authentication strength grant control set to the built-in Phishing-resistant MFA strength, or a custom strength, for your most sensitive applications or for all users. For privileged roles, make it mandatory. Users without a hardware security key can use a passkey in Microsoft Authenticator. Conditional Access requires Entra ID P1.

Identity Security Assessment

Find out if your MFA can be bypassed

We test your Conditional Access policies, authentication strength configuration, and session controls against current AiTM and credential attack techniques and give you a prioritised fix list.