💼 5.4 Ensure routing tables for VPC peering are "least access"

• Contextual name: 💼 5.4 Ensure routing tables for VPC peering are "least access"
• ID: /frameworks/cis-aws-v1.4.0/05/04
• Located in: 💼 5 Networking

Description

Once a VPC peering connection is established, routing tables must be updated to establish any connections between the peered VPCs. These routes can be as specific as desired - even peering a VPC to only a single host on the other side of the connection.

Similar

• Sections
  • /frameworks/cis-aws-v1.5.0/05/05
  • /frameworks/cis-aws-v1.3.0/05/04
• Internal
  • ID: dec-c-785ce442

Similar Sections (Take Policies From)

Section	Sub Sections	Internal Rules	Policies	Flags
💼 CIS AWS v1.3.0 → 💼 5.4 Ensure routing tables for VPC peering are "least access"			1
💼 CIS AWS v1.5.0 → 💼 5.5 Ensure routing tables for VPC peering are "least access" - Level 2 (Manual)			1

Similar Sections (Give Policies To)

Section	Sub Sections	Internal Rules	Policies	Flags
💼 CIS AWS v1.3.0 → 💼 5.4 Ensure routing tables for VPC peering are "least access"			1
💼 CIS AWS v1.5.0 → 💼 5.5 Ensure routing tables for VPC peering are "least access" - Level 2 (Manual)			1

Sub Sections

Section	Sub Sections	Internal Rules	Policies	Flags

Policies (1)

Policy	Logic Count	Flags
📝 AWS VPC Route Table for VPC Peering does not follow the least privilege principle 🟢		🟢 x3