Security checks / Check reference / Risky users & sign-ins
Risk Detection Anomalous Token
Critical Severity Microsoft 365 security check in the Risky users & sign-ins domain.
Anomalous token usage detected Token properties or usage patterns do not match expected behavior. Anomalous tokens indicate token theft or replay, often from adversary-in-the-middle phishing The attacker has a valid session without needing the password. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.
Check summary
What this check verifies
Anomalous token usage detected Token properties or usage patterns do not match expected behavior.
Why it matters
Anomalous tokens indicate token theft or replay, often from adversary-in-the-middle phishing The attacker has a valid session without needing the password.
How to fix it
Revoke all refresh tokens; investigate for AiTM phishing; enforce token protection and compliant device requirements
Siemserva flags every tenant where this check fails and, with Senserva Trustworthy AI remediation, can propose a validated fix you approve before it applies.
Ask your own AI about this check
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Compliance framework mappings
Findings from this check serve as evidence for:
References
Related Risky users & sign-ins checks
Common questions
What does the Risk Detection Anomalous Token check verify?
Anomalous token usage detected Token properties or usage patterns do not match expected behavior. It is a Critical Severity check in the Risky users & sign-ins domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.
How do I fix a Risk Detection Anomalous Token finding?
Revoke all refresh tokens; investigate for AiTM phishing; enforce token protection and compliant device requirements Siemserva ranks the finding by Severity and, with Senserva Trustworthy AI, can propose a validated, approve-before-apply configuration fix.
Which compliance frameworks does this check evidence?
Findings from this check map to SCuBA, MCSB, NIST, SOC2, CIS, HIPAA, including SCuBA policy MS.AAD.3.3v2, MS.AAD.3.4v1, MS.AAD.3.5v1, and MCSB controls LT-3, IM-6, IR-1. That mapping is what turns a scan finding into audit evidence.
Can I ask my own AI about this check?
Yes. This page includes a free copy-paste AI prompt carrying the check's facts: what it verifies, the risk, the remediation, and the framework mappings. Paste it into Claude, ChatGPT, or Copilot; cite-worthy detail without giving an AI access to your tenant.
All 672 checks with severities and mappings: the Microsoft 365 security checks catalog.