Skip to content
StrikeOps

No Risk-Based Policies or Alerts for Risky Sign-Ins

MediumTypical severity Cloud and Microsoft 365CWE-778

01Description

The tenant was licensed for Microsoft Entra ID P2, but no Conditional Access policies used sign-in risk or user risk conditions, and the Risky users and Risky sign-ins reports were not being reviewed. Users flagged as high risk, including some flagged for leaked credentials or anomalous sign-ins, remained active without remediation.

02Impact

Microsoft's risk detections, such as leaked credentials, impossible travel, anonymous IP address and token anomalies, flag likely account compromise. When nothing acts on those signals, an attacker using stolen credentials or a stolen session can continue operating while the evidence sits unread in the portal.

03Severity

Typically

Medium

Typically Medium. Medium where the tenant is licensed for Entra ID P2 but risk-based policies are off and risky users are not reviewed. Report as Low or as an improvement where the tenant lacks P2.

04How to verify

  1. 1In the Entra admin center, review Protection > Identity Protection > Risky users and Risky sign-ins for unremediated high and medium risk entries.
  2. 2Review Protection > Conditional Access > Policies for enabled policies using the 'User risk' or 'Sign-in risk' conditions.
  3. 3Optionally list risky users with Microsoft Graph PowerShell (Get-MgRiskyUser) and check their RiskLevel and RiskState values.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Create a Conditional Access policy requiring MFA for medium and high sign-in risk, and a policy requiring a secure password change for high user risk. Risk-based policies require Entra ID P2.
  2. 2Configure risk-based policies in Conditional Access, which Microsoft recommends over the legacy Identity Protection risk policies.
  3. 3Investigate and remediate current high-risk users, then confirm or dismiss each detection.
  4. 4Route Identity Protection alerts to the security team or to Microsoft Defender XDR or Sentinel for triage.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo