Loading controls...
Benchmark: Your Systems-3
Description
Implement security configurations for all hardware and software assets.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-aws-compliance
Start the Powerpipe server:
steampipe service startpowerpipe server
Open http://localhost:9033 in your browser and select Your Systems-3.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.cisa_cyber_essentials_your_systems_3
Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.cisa_cyber_essentials_your_systems_3 --share
Controls
- API Gateway stage should uses SSL certificate
- API Gateway stage cache encryption at rest should be enabled
- API Gateway stage logging should be enabled
- API Gateway stage should be associated with waf
- Auto Scaling launch config public IP should be disabled
- Backup recovery points should be encrypted
- Backup recovery points manual deletion 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
- At least one enabled trail should be present in a region
- CloudTrail trail logs should be encrypted with KMS CMK
- CloudTrail trail log file validation should be enabled
- CodeBuild project plaintext environment variables should not contain sensitive AWS values
- CodeBuild GitHub or Bitbucket source repository URLs should use OAuth
- DMS replication instances should not be publicly accessible
- DynamoDB table auto scaling should be enabled
- DynamoDB table should be encrypted with AWS KMS
- DynamoDB tables should be in a backup plan
- DynamoDB table point-in-time recovery should be enabled
- DynamoDB table should be protected by backup plan
- Attached EBS volumes should have encryption enabled
- EBS snapshots should not be publicly restorable
- EBS volumes should be in a backup plan
- EBS default encryption should be enabled
- EC2 instance should have EBS optimization enabled
- EC2 instances should be in a VPC
- EC2 instances should not have a public IP address
- EC2 instances should be protected by backup plan
- ECS task definition container definitions should be checked for host mode
- EFS file systems should be encrypted with CMK
- EFS file systems should be protected by backup plan
- ELB application and classic load balancer logging should be enabled
- ELB application load balancer deletion protection 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 have cross-zone load balancing enabled
- 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
- FSx file system should be protected by backup plan
- GuardDuty should be enabled
- IAM password policies for users should have strong configurations
- IAM groups, users, and roles should not have any inline policies
- Ensure inline policies attached to IAM users, roles, and groups should not allow blocked actions on KMS keys
- 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 user MFA should be enabled
- 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
- 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 Aurora clusters should be protected by backup plan
- RDS DB instance and cluster enhanced monitoring should be enabled
- RDS DB instance backup should be enabled
- RDS DB instances should have deletion protection enabled
- RDS DB instance encryption at rest should be enabled
- RDS DB instances should be in a backup plan
- Database logging should be enabled
- RDS DB instance multiple az should be enabled
- RDS DB instances should prohibit public access
- RDS DB snapshots should be encrypted at rest
- RDS snapshots should prohibit public access
- AWS Redshift clusters should have automatic snapshots enabled
- 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 cross-region replication should be enabled
- 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 bucket versioning should be enabled
- 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
- Secrets Manager secrets should have automatic rotation enabled
- Secrets Manager secrets should be rotated within specific number of days
- Secrets Manager secrets should be rotated as per the rotation schedule
- AWS Security Hub should be enabled for an AWS Account
- SNS topics should be encrypted at rest
- 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
- Logging should be enabled on AWS WAFv2 regional and global web access control list (ACLs)