Benchmark: PR.AC-3
Description
Remote access is managed.
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.AC-3.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.nist_csf_pr_ac_3Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.nist_csf_pr_ac_3 --shareControls
- API Gateway stage should be associated with waf
- Auto Scaling launch config public IP should be disabled
- CloudFront distributions should have AWS WAF enabled
- DMS replication instances should not be publicly accessible
- EBS snapshots should not be publicly restorable
- 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
- 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 root user hardware MFA should be enabled
- IAM root user MFA should be enabled
- IAM users with console access should have MFA enabled
- IAM user MFA should be enabled
- Lambda functions should be in a VPC
- Lambda functions should restrict public access
- The default stateless action for Network Firewall policies should be drop or forward for full packets
- Network Firewall policies should have at least one rule group associated
- Stateless network firewall rule group should not be empty
- 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 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 default security group should not allow inbound and outbound traffic
- VPC internet gateways should be attached to authorized vpc
- Network ACLs should not allow ingress from 0.0.0.0/0 to port 22 or port 3389
- 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
- WAF regional rule should have at least one condition
- WAF regional rule group should have at least one rule attached
- WAF global web ACL should have at least one rule or rule group