Benchmark: Annex I (1.3)
Description
Appropriately manage and provide protection within and outside UCB/network, keeping in mind how the data/information is stored, transmitted, processed, accessed and put to use within/outside the UCB’s network, and level of risk they are exposed to depending on the sensitivity of the data/information.
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 Annex I (1.3).
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.rbi_cyber_security_annex_i_1_3Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.rbi_cyber_security_annex_i_1_3 --shareControls
- 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
- Auto Scaling launch config public IP should be disabled
- 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 encryption by default should be enabled
- EBS snapshots should not be publicly restorable
- EBS volume encryption at rest should be enabled
- EC2 instances should be in a VPC
- EC2 instances should not have a public IP address
- EFS file system encryption at rest should be enabled
- Application Load Balancer should be configured to drop invalid http headers
- ELB application load balancers should redirect HTTP requests to HTTPS
- 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 node-to-node encryption should be enabled
- KMS CMK rotation should be enabled
- KMS keys should not be pending deletion
- 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
- 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 with KMS
- S3 bucket default encryption should be enabled
- S3 buckets should enforce SSL
- S3 buckets should prohibit public read access
- S3 buckets should prohibit public write access
- S3 public access should be blocked at account and 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 internet gateways should be attached to authorized vpc
- 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 subnet auto assign public IP should be disabled