Benchmark: Active Directory
Description
This section contains recommendations for configuring Active Directory resources.
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 Active Directory.
Run this benchmark in your terminal:
powerpipe benchmark run azure_compliance.benchmark.all_controls_activedirectorySnapshot and share results via Turbot Pipes:
powerpipe benchmark run azure_compliance.benchmark.all_controls_activedirectory --shareControls
- Ensure that multifactor authentication is required to access Microsoft Admin Portals
- Ensure that a multifactor authentication policy exists for all users
- Ensure that 'Guest invite restrictions' is set to 'Only users assigned to specific admin roles [...]' or 'No one [..]'
- Ensure that 'Guest users access restrictions' is set to 'Guest user access is restricted to properties and memberships of their own directory objects'
- Ensure that 'User consent for applications' is set to 'Do not allow user consent'
- Ensure that 'User consent for applications' is set to 'Allow user consent for apps from verified publishers, for selected permissions'
- Ensure that a 'Custom banned password list' is set to 'Enforce'
- Ensure disabled user accounts do not have read, write, or owner permissions
- Ensure guest users are reviewed on a monthly basis
- Ensure that account 'Lockout duration in seconds' is greater than or equal to '60'
- Ensure that account 'Lockout threshold' is less than or equal to '10'
- Ensure that 'Users can create Microsoft 365 groups in Azure portals, API or PowerShell' is set to 'No'
- Ensure that multifactor authentication is required for Windows Azure Service Management API
- Ensure that 'Require Multifactor Authentication to register or join devices with Microsoft Entra' is set to 'Yes'
- Ensure that 'security defaults' is enabled in Microsoft Entra ID
- Ensure Multi-factor Authentication is required for Azure Management
- Ensure trusted locations are defined
- Blocked accounts with owner permissions on Azure resources should be removed
- Blocked accounts with read and write permissions on Azure resources should be removed
- Guest accounts with owner permissions on Azure resources should be removed
- Guest accounts with read permissions on Azure resources should be removed
- Guest accounts with write permissions on Azure resources should be removed
- Audit usage of custom RBAC roles
- Ensure that no Custom Subscription Administrator roles exist
- Ensure there are between 2 and 3 subscription owners
- A maximum of 3 owners should be designated for your subscription
- There should be more than one owner assigned to your subscription
- Subscriptions with custom roles should not be overly permissive
- Use of the 'User Access Administrator' role should be restricted
- IAM users should not have built in contributor role
- Ensure that 'Users can create security groups in Azure portals, API or PowerShell' is set to 'No'
- Ensure that 'Users Can Create Tenants' is set to 'No'
- Ensure that 'Users Can Register Applications' is set to 'No'