Benchmark: AC-2(6) Dynamic Privilege Management

Usage

Browse dashboards and select AC-2(6) Dynamic Privilege Management:

steampipe dashboard

Or run the benchmarks in your terminal:

steampipe check aws_compliance.benchmark.nist_800_53_rev_5_ac_2_6

Snapshot and share results via Steampipe Cloud:

steampipe login
steampipe check --share aws_compliance.benchmark.nist_800_53_rev_5_ac_2_6

Controls

• DMS replication instances should not be publicly accessible
• EBS snapshots should not be publicly restorable
• EC2 instances should be in a VPC
• EC2 instances should not have a public IP address
• EC2 instances should use IMDSv2
• EMR cluster master nodes should not have public IP addresses
• ES domains should be in a VPC
• IAM groups, users, and roles should not have any inline policies
• IAM policy should not have statements with admin access
• IAM root user should not have access keys
• IAM users should be in at least one group
• IAM user should not have any inline or attached policies
• IAM user credentials that have not been used in 90 days should be disabled
• Lambda functions should be in a VPC
• Lambda functions should restrict public access
• RDS DB instances should prohibit public access
• RDS snapshots should prohibit public access
• Redshift clusters should prohibit public access
• S3 buckets should prohibit public read access
• S3 buckets should prohibit public write access
• S3 public access should be blocked at account level
• S3 public access should be blocked at bucket levels
• SageMaker notebook instances should not have direct internet access
• VPC subnet auto assign public IP should be disabled

Tags