Benchmark: PR.PT-3
Description
The principle of least functionality is incorporated by configuring systems to provide only essential capabilities.
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 PR.PT-3.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.nist_csf_pr_pt_3Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.nist_csf_pr_pt_3 --shareControls
- Auto Scaling launch config public IP should be disabled
- CodeBuild project environments should not have privileged mode enabled
- DMS replication instances should not be publicly accessible
- EBS snapshots should not be publicly restorable
- EC2 instances should have IAM profile attached
- EC2 instances should be in a VPC
- EC2 instances should not have a public IP address
- EC2 transit gateways should have auto accept shared attachments disabled
- ECS task definition container definitions should be checked for host mode
- EKS clusters endpoint should restrict public access
- EMR cluster master nodes should not have public IP addresses
- ES domains should be in a VPC
- IAM policy should not have statements with admin access
- IAM root user should not have access keys
- IAM user should not have any inline or attached policies
- Lambda functions should be in a VPC
- Lambda functions should restrict public access
- OpenSearch domains should have fine-grained access control enabled
- OpenSearch domains should be in a VPC
- RDS DB instances should prohibit public access
- RDS snapshots should prohibit public access
- AWS Redshift enhanced VPC routing should be enabled
- Redshift clusters should prohibit public access
- S3 buckets access control lists (ACLs) should not be used to manage user access to buckets
- S3 bucket policy 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 documents should not be public
- VPC should be configured to use VPC endpoints
- VPC internet gateways should be attached to authorized vpc
- VPC subnet auto assign public IP should be disabled