Benchmark: 2.2 Conditional Access
Overview
For most Azure tenants, and certainly for organizations with a significant use of Microsoft Entra ID, Conditional Access policies are recommended and preferred. To use Conditional Access Policies, a licensing plan is required, and Security Defaults must be disabled. Because of the licensing requirement, all Conditional Access policies are assigned a profile of "Level 2."
Conditional Access requires one of the following plans:
- Microsoft Entra ID P1 or P2
- Microsoft 365 Business Premium
- Microsoft 365 E3 or E5
- Microsoft 365 F1, F3, F5 Security and F5 Security + Compliance
- Enterprise Mobility & Security E3 or E5.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-azure-complianceStart the Powerpipe server:
steampipe service startpowerpipe serverOpen http://localhost:9033 in your browser and select 2.2 Conditional Access.
Run this benchmark in your terminal:
powerpipe benchmark run azure_compliance.benchmark.cis_v300_2_2Snapshot and share results via Turbot Pipes:
powerpipe benchmark run azure_compliance.benchmark.cis_v300_2_2 --shareControls
- 2.2.1 Ensure Trusted Locations Are Defined
- 2.2.2 Ensure that an exclusionary Geographic Access Policy is considered
- 2.2.3 Ensure that an exclusionary Device code flow policy is considered
- 2.2.4 Ensure that A Multi-factor Authentication Policy Exists for Administrative Groups
- 2.2.5 Ensure that A Multi-factor Authentication Policy Exists for All Users
- 2.2.6 Ensure Multi-factor Authentication is Required for Risky Sign-ins
- 2.2.7 Ensure Multifactor Authentication is Required for Windows Azure Service Management API
- 2.2.8 Ensure Multifactor Authentication is Required to access Microsoft Admin Portals