Loading controls...
Benchmark: Baseline Configuration (CM-2)
Description
The organization develops, documents, and maintains under configuration control, a current baseline configuration of the information system.
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 Baseline Configuration (CM-2).
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.fedramp_low_rev_4_cm_2Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.fedramp_low_rev_4_cm_2 --shareControls
- API Gateway stage should be associated with waf
- Auto Scaling launch config public IP should be disabled
- DMS replication instances should not be publicly accessible
- EBS snapshots should not be publicly restorable
- EBS volumes should be attached to EC2 instances
- EC2 instances should be in a VPC
- EC2 instances should not have a public IP address
- EC2 instances should be managed by AWS Systems Manager
- EC2 stopped instances should be removed in 30 days
- ELB application load balancer deletion protection should be enabled
- EMR cluster master nodes should not have public IP addresses
- ES domains should be in a VPC
- 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
- SSM managed instance associations should be compliant
- VPC default security group should not allow inbound and outbound traffic
- VPC route table should restrict public access to IGW
- 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