Control: 5.2.5 Ensure that multifactor authentication is required for risky sign-ins
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.
Remediation
Remediate from Azure Portal
- From Azure Home select the Portal Menu in the top left and select
Microsoft Entra ID. - Select
Security - Select
Conditional Access. - Select
Policies. - Click
+ New policy. - Enter a name for the policy.
- Click the blue text under
Users. - Under
Include, selectAll users. - Under
Exclude, checkUsers and groups. - Select users this policy should not apply to and click
Select. - Click the blue text under
Target resources. - Select
All cloud apps. - Click the blue text under
Conditions. - Select
Sign-in risk. - Update the
Configuretoggle toYes. - Check the sign-in risk level this policy should apply to, e.g.
HighandMedium. - Select
Done. - Click the blue text under
Grantand checkRequire multifactor authenticationthen click theSelectbutton. - Click the blue text under
Sessionthen checkSign-in frequencyand selectEvery timeand click theSelectbutton. - Set
Enable policytoReport-only. - Click
Create.
After testing the policy in report-only mode, update the Enable policy setting from Report-only to On.
Default Value
MFA is not enabled by default.
Usage
Run the control in your terminal:
powerpipe control run azure_compliance.control.cis_v500_5_2_5Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run azure_compliance.control.cis_v500_5_2_5 --shareSQL
This control uses a named query:
select id as resource, 'info' as status, 'Manual verification required.' as reason, display_name as subscriptionfrom azure_subscription;