Benchmark: 2.2.2 Enable only necessary services, protocols, daemons, etc., as required for the function of the system
Description
As stated in Requirement 1.1.6, there are many protocols that a business may need (or have enabled by default) that are commonly used by malicious individuals to compromise a network. Including this requirement as part of an organization's configuration standards and related processes ensures that only the necessary services and protocols are enabled.
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 2.2.2 Enable only necessary services, protocols, daemons, etc., as required for the function of the system.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.pci_dss_v321_requirement_2_2_2Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.pci_dss_v321_requirement_2_2_2 --shareControls
- 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
- EKS clusters endpoint should restrict public access
- EMR cluster master nodes should not have public IP addresses
- ES domains should be in a VPC
- Lambda functions should be in a VPC
- Lambda functions should restrict public access
- RDS DB instances should prohibit public access
- RDS snapshots should prohibit public access
- Redshift clusters should prohibit public access
- S3 buckets should prohibit public read access
- S3 public access should be blocked at account level
- SageMaker notebook instances should not have direct internet access
- VPC should be configured to use VPC endpoints
- VPC internet gateways should be attached to authorized vpc
- VPC security groups should restrict ingress SSH access from 0.0.0.0/0