Skip to main content

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

  • Contextual name: 💼 4.4 Ensure routing tables for VPC peering are "least access"
  • ID: /frameworks/cis-aws-v1.2.0/04/04
  • Located in: 💼 4 Networking

Description​

Once a VPC peering connection is estalished, 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.3.0/05/04
  • Internal
    • ID: dec-c-bd20937e

Similar Sections (Take Policies From)​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS AWS v1.3.0 → 💼 5.4 Ensure routing tables for VPC peering are "least access"1

Similar Sections (Give Policies To)​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS AWS v1.3.0 → 💼 5.4 Ensure routing tables for VPC peering are "least access"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