Benchmark: 5 Networking
Overview
This section contains recommendations for configuring security-related aspects of AWS Virtual Private Cloud (VPC).
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 5 Networking.
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.cis_v200_5Snapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.cis_v200_5 --shareControls
- 5.1 Ensure no Network ACLs allow ingress from 0.0.0.0/0 to remote server administration ports
- 5.2 Ensure no security groups allow ingress from 0.0.0.0/0 to remote server administration ports
- 5.3 Ensure no security groups allow ingress from ::/0 to remote server administration ports
- 5.4 Ensure the default security group of every VPC restricts all traffic
- 5.5 Ensure routing tables for VPC peering are "least access"
- 5.6 Ensure that EC2 Metadata Service only allows IMDSv2