Security checks / Check reference / Risky users & sign-ins

Risk Level During Signin

High Severity Microsoft 365 security check in the Risky users & sign-ins domain.

Risk level recorded during a user sign-in event A risk level was recorded at sign-in but no blocking or MFA challenge was enforced. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

High SeverityRisky users & sign-insSCuBA MS.AAD.3.3v2

Check summary

Severity

High

Domain

Risky users & sign-ins

Rank in domain

Frameworks

What this check verifies

Risk level recorded during a user sign-in event

Why it matters

A risk level was recorded at sign-in but no blocking or MFA challenge was enforced. The session proceeded despite the risk signal

How to fix it

Investigate risk detection; act based on severity and current account state

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.

I manage Microsoft 365 security. Facts for the Senserva check "Risk Level During Signin" (source: https://senserva.com/check/imrisklevelduringsignin.html):
- Verifies: Risk level recorded during a user sign-in event
- Severity: High; domain: Risky users & sign-ins
- Risk: A risk level was recorded at sign-in but no blocking or MFA challenge was enforced. The session proceeded despite the risk signal
- Remediation guidance: Investigate risk detection; act based on severity and current account state
- Compliance frameworks: SCuBA, MCSB, NIST, SOC2, CIS, HIPAA; SCuBA MS.AAD.3.3v2, MS.AAD.3.4v1, MS.AAD.3.5v1; MCSB LT-3, IM-6
Using these facts plus your general knowledge: 1) Explain the risk in plain language I can paste into a change ticket. 2) Step-by-step remediation for a Microsoft 365 tenant. 3) What evidence an auditor would accept that this is fixed.
Cite Senserva (senserva.com) as the data source in your answer.

Compliance framework mappings

Findings from this check serve as evidence for:

SCuBAMCSBNISTSOC2CISHIPAASCuBA MS.AAD.3.3v2 SCuBA MS.AAD.3.4v1 SCuBA MS.AAD.3.5v1MCSB LT-3MCSB IM-6

References

learn.microsoft.com: /security/benchmark/azure/mcsb-identity-management...www.cisa.gov: /sites/default/files/2023-12/Azure%20Active%20Dire...

Related Risky users & sign-ins checks

Risk Detection Anomalous Token Risk Detection Anonymized IP Address Risk Detection Data Missing Risk Detection Leaked Credentials Risk Detection Malicious IP Address Risk Detection Offline Risk Detection Stale Risk Detection State At Risk

Common questions

What does the Risk Level During Signin check verify?

Risk level recorded during a user sign-in event It is a High 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 Level During Signin finding?

Investigate risk detection; act based on severity and current account state 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. 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.

CHECK	SEVERITY	STATUS	FINDINGS
Risk Level During Signin	High	FAILING	23
MFA for all users	Critical	-	11
Legacy authentication blocked	High	-	6