Benchmark: Access Enforcement (AC-3)
Description
Enforce approved authorizations for access to systems in accordance with policy.
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 Access Enforcement (AC-3).
Run this benchmark in your terminal:
powerpipe benchmark run azure_compliance.benchmark.nist_sp_800_53_rev_5_ac_3Snapshot and share results via Turbot Pipes:
powerpipe benchmark run azure_compliance.benchmark.nist_sp_800_53_rev_5_ac_3 --shareBenchmarks
Controls
- Function apps should use managed identity
- App Service apps should use managed identity
- Authorize access to security functions and information
- Cognitive Services accounts should have local authentication methods disabled
- Audit Linux machines that have accounts without passwords
- Deploy the Linux Guest Configuration extension to enable Guest Configuration assignments on Linux VMs
- Add system-assigned managed identity to enable Guest Configuration assignments on virtual machines with no identities
- Add system-assigned managed identity to enable Guest Configuration assignments on VMs with a user-assigned identity
- Authentication to Linux machines should require SSH keys
- Virtual machines should be migrated to new Azure Resource Manager resources
- Accounts with owner permissions on Azure resources should be MFA enabled
- Accounts with read permissions on Azure resources should be MFA enabled
- Accounts with write permissions on Azure resources should be MFA enabled
- Service Fabric clusters should only use Azure Active Directory for client authentication
- An Azure Active Directory administrator should be provisioned for SQL servers
- Storage accounts should be migrated to new Azure Resource Manager resources