Benchmark: Your Data-2

Usage

Browse dashboards and select Your Data-2:

steampipe dashboard

Or run the benchmarks in your terminal:

steampipe check aws_compliance.benchmark.cisa_cyber_essentials_your_data_2

Snapshot and share results via Steampipe Cloud:

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

Controls

• ACM certificates should not expire within 30 days
• API Gateway stage should uses SSL certificate
• API Gateway stage cache encryption at rest should be enabled
• API Gateway stage logging should be enabled
• Auto Scaling launch config public IP should be disabled
• Backup recovery points should be encrypted
• At least one multi-region AWS CloudTrail should be present in an account
• All S3 buckets should log S3 data events in CloudTrail
• At least one enabled trail should be present in a region
• CloudTrail trails should be integrated with CloudWatch logs
• CloudTrail trail logs should be encrypted with KMS CMK
• DMS replication instances should not be publicly accessible
• DynamoDB table should be encrypted with AWS KMS
• Attached EBS volumes should have encryption enabled
• EBS snapshots should not be publicly restorable
• EBS default encryption should be enabled
• EC2 instances should be in a VPC
• EC2 instances should not have a public IP address
• EFS file systems should be encrypted with CMK
• ELB application and classic load balancer logging should be enabled
• ELB application load balancers should redirect HTTP requests to HTTPS
• ELB application load balancers should have Web Application Firewall (WAF) enabled
• ELB application and network load balancers should only use SSL or HTTPS listeners
• ELB classic load balancers should use SSL certificates
• ELB classic load balancers should only use SSL or HTTPS listeners
• EMR cluster master nodes should not have public IP addresses
• ES domain encryption at rest should be enabled
• ES domains should be in a VPC
• Elasticsearch domain should send logs to CloudWatch
• Elasticsearch domain node-to-node encryption should be enabled
• Lambda functions should be in a VPC
• Lambda functions should restrict public access
• Log group encryption at rest should be enabled
• RDS DB instance encryption at rest should be enabled
• Database logging should be enabled
• RDS DB instances should prohibit public access
• RDS DB snapshots should be encrypted at rest
• RDS snapshots should prohibit public access
• Redshift cluster encryption in transit should be enabled
• Redshift cluster audit logging and encryption should be enabled
• AWS Redshift clusters should be encrypted with KMS
• Redshift clusters should prohibit public access
• S3 bucket default encryption should be enabled
• S3 bucket default encryption should be enabled with KMS
• 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
• S3 public access should be blocked at bucket levels
• SageMaker endpoint configuration encryption should be enabled
• SageMaker notebook instances should not have direct internet access
• SageMaker notebook instance encryption should be enabled
• SNS topics should be encrypted at rest
• 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
• VPC security groups should restrict ingress SSH access from 0.0.0.0/0
• VPC security groups should restrict ingress TCP and UDP access from 0.0.0.0/0
• VPC subnet auto assign public IP should be disabled
• Logging should be enabled on AWS WAFv2 regional and global web access control list (ACLs)

Tags