Skip to main content

⭐ Repository → 📁 Compliance Engine → 📁 CloudAware → 📁 Azure → 📁 Microsoft Entra ID

🛡️ Microsoft Entra ID MFA For Risky Sign-Ins is not required🟢⚪

Description​

Open File

Description​

Entra ID tracks the behavior of sign-in events. If the Entra ID domain is licensed with P2, the sign-in behavior can be used as a detection mechanism for additional scrutiny during the sign-in event. If this policy is set up, then Risky Sign-in events will prompt users to use multi-factor authentication (MFA) tokens on login for additional verification.

Rationale​

Enabling multi-factor authentication is a recommended setting to limit the potential of accounts being compromised and limiting access to authenticated personnel. Enabling this policy allows Entra ID's risk-detection mechanisms to force additional scrutiny on the login event, providing a deterrent response to potentially malicious sign-in events, and adding an additional authentication layer as a reaction to potentially malicious behavior.

Impact​

Risk Policies for Conditional Access require Microsoft Entra ID P2. Additional overhead to support or maintain these policies may also be required if users lose access to their MFA tokens.

Audit​

... see more

Remediation​

Open File

Remediation​

From Azure Portal​

  1. From Azure Home select the Portal Menu in the top left, and select Microsoft Entra ID.
  2. Select Security
  3. Select Conditional Access.
  4. Select Policies.
  5. Click + New policy.
  6. Enter a name for the policy.
  7. Click the blue text under Users.
  8. Under Include, select All users.
  9. Under Exclude, check Users and groups.
  10. Select users this policy should not apply to and click Select.
  11. Click the blue text under Target resources.
  12. Select All cloud apps.
  13. Click the blue text under Conditions.
  14. Select Sign-in risk.
  15. Update the Configure toggle to Yes.
  16. Check the sign-in risk level this policy should apply to, e.g. High and Medium.
  17. Select Done.
  18. Click the blue text under Grant and check Require multifactor authentication then click the Select button.
  19. Click the blue text under Session then check Sign-in frequency and select Every time and click the Select button.
  20. Set Enable policy to Report-only.
  21. Click Create.

... see more

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 CIS Azure v2.1.0 → 💼 1.2.5 Ensure Multi-factor Authentication is Required for Risky Sign-ins - Level 1 (Manual)1no data
💼 CIS Azure v3.0.0 → 💼 2.2.6 Ensure Multi-factor Authentication is Required for Risky Sign-ins (Manual)1no data
💼 CIS Azure v4.0.0 → 💼 6.2.5 Ensure that multifactor authentication is required for risky sign-ins (Manual)1no data
💼 Cloudaware Framework → 💼 Multi-Factor Authentication (MFA) Implementation16no data