Benchmark: PR.AC-1
Description
Identities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users and processes.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-aws-complianceStart the Powerpipe server:
steampipe service startpowerpipe serverOpen http://localhost:9033 in your browser and select PR.AC-1.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.nist_csf_pr_ac_1Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.nist_csf_pr_ac_1 --shareControls
- CodeBuild project environments should not have privileged mode enabled
- EC2 instances should have IAM profile attached
- EC2 instances should not use key pairs in running state
- ECS containers should run as non-privileged
- ECS containers should be limited to read-only access to root filesystems
- ECS task definition container definitions should be checked for host mode
- EMR cluster Kerberos should be enabled
- IAM password policies for users should have strong configurations
- Ensure IAM policy should not grant full access to service
- IAM groups should have at least one user
- IAM groups, users, and roles should not have any inline policies
- IAM AWS managed policies should be attached to IAM role
- Ensure managed IAM policies should not allow blocked actions on KMS keys
- Ensure inline policies attached to IAM users, roles, and groups should not allow blocked actions on KMS keys
- IAM policy should not have statements with admin access
- IAM policy should be in use
- IAM root user should not have access keys
- IAM user access keys should be rotated at least every 90 days
- IAM users should be in at least one group
- IAM user MFA should be enabled
- IAM user should not have any inline or attached policies
- IAM user credentials that have not been used in 90 days should be disabled
- OpenSearch domains should have fine-grained access control enabled
- IAM authentication should be configured for RDS clusters
- RDS DB instances should have iam authentication enabled
- S3 buckets access control lists (ACLs) should not be used to manage user access to buckets
- S3 bucket policy should prohibit public access
- AWS S3 permissions granted to other AWS accounts in bucket policies should be restricted
- Secrets Manager secrets should have automatic rotation enabled
- Secrets Manager secrets should be rotated as per the rotation schedule
- Secrets Manager secrets that have not been used in 90 days should be removed