Benchmark: 164.308(a)(1)(ii)(B) Risk management
Description
Implement security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level to comply with Section 164.306(a).
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 164.308(a)(1)(ii)(B) Risk management.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.hipaa_security_rule_2003_164_308_a_1_ii_bSnapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.hipaa_security_rule_2003_164_308_a_1_ii_b --shareControls
- API Gateway stage cache encryption at rest should be enabled
- Auto Scaling groups with a load balancer should use health checks
- 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 point-in-time recovery should be enabled
- Attached EBS volumes should have encryption enabled
- EBS snapshots should not be publicly restorable
- EBS encryption by default should be enabled
- 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
- EFS file system encryption at rest should be enabled
- ElastiCache Redis cluster automatic backup should be enabled with retention period of 15 days or greater
- ELB application load balancer deletion protection should be enabled
- ELB application load balancers should redirect HTTP requests to HTTPS
- ELB classic load balancers should use SSL certificates
- 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
- IAM policy should not have statements with admin access
- IAM root user should not have access keys
- 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
- OpenSearch domains should have encryption at rest enabled
- OpenSearch domains should be in a VPC
- RDS DB instance backup should be 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
- RDS snapshots should prohibit public access
- Redshift cluster encryption in transit should be enabled
- Redshift cluster audit logging and encryption should be enabled
- Redshift clusters should prohibit public access
- S3 bucket cross-region replication should be enabled
- S3 bucket default encryption should be enabled
- S3 buckets should enforce SSL
- S3 bucket object lock should be enabled
- S3 bucket policy should prohibit public access
- 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
- 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
- SSM managed instance associations should be compliant
- SSM managed instance patching should be compliant
- VPC internet gateways should be attached to authorized vpc
- 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
- Both VPN tunnels provided by AWS Site-to-Site VPN should be in UP status