Benchmark: 500.02(a)
Description
Cybersecurity Program. Each Covered Entity shall maintain a cybersecurity program designed to protect the confidentiality, integrity and availability of the Covered Entity’s Information Systems.
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 500.02(a).
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.nydfs_23_500_02_aSnapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.nydfs_23_500_02_a --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 groups with a load balancer should use health checks
- Auto Scaling launch config public IP should be disabled
- Backup recovery points should be encrypted
- CloudTrail trail logs should be encrypted with KMS CMK
- CloudTrail trail log file validation should be enabled
- CodeBuild project artifact encryption should be enabled
- DynamoDB table auto scaling should be enabled
- DynamoDB table should be encrypted with AWS KMS
- Attached EBS volumes should have encryption enabled
- EBS encryption by default should be enabled
- EC2 instance detailed monitoring should be enabled
- EFS file system encryption at rest should be enabled
- Elastic Beanstalk enhanced health reporting should be enabled
- ELB application load balancer deletion protection should be enabled
- ELB application load balancers should be drop 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 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
- ES domain encryption at rest should be enabled
- Elasticsearch domain node-to-node encryption should be enabled
- Kinesis streams should have server side encryption enabled
- Log group encryption at rest should be enabled
- OpenSearch domains should have encryption at rest enabled
- OpenSearch domains node-to-node encryption should be enabled
- RDS DB instances should have deletion protection enabled
- RDS DB instance encryption at rest should be enabled
- RDS DB instance multiple az should be enabled
- RDS DB snapshots should be encrypted at rest
- Redshift cluster encryption in transit should be enabled
- Redshift cluster audit logging and encryption should be enabled
- S3 bucket default encryption should be enabled with KMS
- S3 bucket default encryption should be enabled
- S3 buckets should enforce SSL
- S3 bucket object lock should be enabled
- S3 public access should be blocked at account level
- SageMaker endpoint configuration encryption should be enabled
- SageMaker notebook instance encryption should be enabled
- SNS topics should be encrypted at rest
- SSM documents should not be public
- Both VPN tunnels provided by AWS Site-to-Site VPN should be in UP status