Skip to main content

💼 5.6 Ensure routing tables for VPC peering are "least access" (Manual)

  • Contextual name: 💼 5.6 Ensure routing tables for VPC peering are "least access" (Manual)
  • ID: /frameworks/cis-aws-v4.0.1/05/06
  • Located in: 💼 5 Networking

Description​

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

Similar​

  • Sections
    • /frameworks/cis-aws-v5.0.0/05/06
    • /frameworks/cis-aws-v4.0.0/05/06

Similar Sections (Take Policies From)​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS AWS v4.0.0 → 💼 5.6 Ensure routing tables for VPC peering are "least access" (Manual)1
💼 CIS AWS v5.0.0 → 💼 5.6 Ensure routing tables for VPC peering are "least access" (Manual)1

Similar Sections (Give Policies To)​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS AWS v4.0.0 → 💼 5.6 Ensure routing tables for VPC peering are "least access" (Manual)1
💼 CIS AWS v5.0.0 → 💼 5.6 Ensure routing tables for VPC peering are "least access" (Manual)1

Sub Sections​

SectionSub SectionsInternal RulesPoliciesFlags

Policies (1)​

PolicyLogic CountFlags
📝 AWS VPC Route Table for VPC Peering does not follow the least privilege principle 🟢🟢 x3