Security checks / Check reference / Conditional Access
Conditional Access Risky User Not Protected
Medium Severity Microsoft 365 security check in the Conditional Access domain.
High-risk user scenarios lack password change or block. Detected via What-If Users flagged as high-risk can keep signing in without password change or block Leaked credentials remain usable until someone manually intervenes Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.
Check summary
What this check verifies
High-risk user scenarios lack password change or block. Detected via What-If
Why it matters
Users flagged as high-risk can keep signing in without password change or block Leaked credentials remain usable until someone manually intervenes
How to fix it
Add CA policy coverage for this scenario; require MFA or block based on risk level
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 Conditional Access checks
Common questions
What does the Conditional Access Risky User Not Protected check verify?
High-risk user scenarios lack password change or block. Detected via What-If It is a Medium Severity check in the Conditional Access domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.
How do I fix a Conditional Access Risky User Not Protected finding?
Add CA policy coverage for this scenario; require MFA or block based on risk level 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.1.1v1, MS.AAD.2.1v1, MS.AAD.2.2v1, MS.AAD.2.3v1, MS.AAD.3.1v1, MS.AAD.3.2v1, and MCSB controls IM-6, LT-3. 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.