Benchmark: 2 Identity
Overview
This section covers security best practice recommendations for products in the Azure Identity services category.
Azure Product Category Page: https://azure.microsoft.com/en-us/products/category/identity
Many of the recommendations from this section are marked as "Manual" while the existing Azure CLI and Azure AD PowerShell support through the Azure AD Graph are being deprecated. It is now recommended to use the new Microsoft Graph PowerShell in replacement of Azure AD Graph for PowerShell and API level access. From a security posture standpoint, these recommendations are still very important and should not be discounted because they are "Manual." As automation capability is developed for this Benchmark, the related recommendations will be updated with the respective audit and remediation steps and changed to an "automated" assessment status.
If any problems are encountered running Azure CLI or PowerShell methodologies, please refer to the Introduction section of this Benchmark where you will find additional detail on permission and required cmdlets.
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 Identity.
Run this benchmark in your terminal:
powerpipe benchmark run azure_compliance.benchmark.cis_v300_2Snapshot and share results via Turbot Pipes:
powerpipe benchmark run azure_compliance.benchmark.cis_v300_2 --shareBenchmarks
Controls
- 2.3 Ensure that 'Restrict non-admin users from creating tenants' is set to 'Yes'
- 2.4 Ensure Guest Users Are Reviewed on a Regular Basis
- 2.5 Ensure That 'Number of methods required to reset' is set to '2'
- 2.6 Ensure that account 'Lockout Threshold' is less than or equal to '10'
- 2.7 Ensure that account 'Lockout duration in seconds' is greater than or equal to '60'
- 2.8 Ensure that a Custom Bad Password List is set to 'Enforce' for your Organization
- 2.9 Ensure that 'Number of days before users are asked to re-confirm their authentication information' is not set to '0'
- 2.10 Ensure that 'Notify users on password resets?' is set to 'Yes'
- 2.11 Ensure That 'Notify all admins when other admins reset their password?' is set to 'Yes'
- 2.12 Ensure 'User consent for applications' is set to 'Do not allow user consent'
- 2.13 Ensure 'User consent for applications' Is Set To 'Allow for Verified Publishers'
- 2.14 Ensure That 'Users Can Register Applications' Is Set to 'No'
- 2.15 Ensure That 'Guest users access restrictions' is set to 'Guest user access is restricted to properties and memberships of their own directory objects'
- 2.16 Ensure that 'Guest invite restrictions' is set to 'Only users assigned to specific admin roles can invite guest users'
- 2.17 Ensure That 'Restrict access to Microsoft Entra admin center' is Set to 'Yes'
- 2.18 Ensure that 'Restrict user ability to access groups features in the Access Pane' is Set to 'Yes'
- 2.19 Ensure that 'Users can create security groups in Azure portals, API or PowerShell' is set to 'No'
- 2.20 Ensure that 'Owners can manage group membership requests in the Access Panel' is set to 'No'
- 2.21 Ensure that 'Users can create Microsoft 365 groups in Azure portals, API or PowerShell' is set to 'No'
- 2.22 Ensure that 'Require Multi-Factor Authentication to register or join devices with Microsoft Entra ID' is set to 'Yes'
- 2.23 Ensure That No Custom Subscription Administrator Roles Exist
- 2.24 Ensure a Custom Role is Assigned Permissions for Administering Resource Locks
- 2.25 Ensure That `Subscription leaving Microsoft Entra ID directory` and `Subscription entering Microsoft Entra ID directory` Is Set To 'Permit No One'
- 2.26 Ensure fewer than 5 users have global administrator assignment