Benchmark: CM-6(a)

Usage

Browse dashboards and select CM-6(a):

steampipe dashboard

Or run the benchmarks in your terminal:

steampipe check aws_compliance.benchmark.nist_800_53_rev_5_cm_6_a

Snapshot and share results via Steampipe Cloud:

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

Controls

• AWS account should be part of AWS Organizations
• Auto Scaling groups with a load balancer should use health checks
• Auto Scaling launch config public IP should be disabled
• At least one multi-region AWS CloudTrail should be present in an account
• All S3 buckets should log S3 data events in CloudTrail
• CloudTrail trails should be integrated with CloudWatch logs
• CloudTrail trail logs should be encrypted with KMS CMK
• CloudTrail trail log file validation should be enabled
• Attached EBS volumes should have encryption enabled
• EBS default encryption should be enabled
• EC2 instances should have IAM profile attached
• Ensure IAM password policy requires a minimum length of 14 or greater
• IAM groups, users, and roles should not have any inline policies
• IAM policy should not have statements with admin access
• IAM root user hardware MFA should be enabled
• IAM root user MFA should be enabled
• IAM root user should not have access keys
• IAM user access keys should be rotated at least every 90 days
• IAM users with console access should have MFA enabled
• 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
• KMS CMK rotation should be enabled
• S3 bucket cross-region replication should be enabled
• S3 bucket default encryption should be enabled
• S3 buckets should enforce SSL
• S3 bucket logging should be enabled
• S3 buckets should prohibit public read access
• S3 buckets should prohibit public write access
• S3 public access should be blocked at account level
• VPC default security group should not allow inbound and outbound traffic
• VPC flow logs should be enabled
• VPC security groups should restrict ingress access on ports 20, 21, 22, 3306, 3389, 4333 from 0.0.0.0/0

Tags