CIS Amazon Web Services Foundations Benchmark v1.2.0/Networking/49 of 49
4.4Ensure routing tables for VPC peering are "least access"
Control family: Networking
Control 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.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
A peering connection links two VPCs, but routes decide which parts of each can reach the other. Routing a whole VPC range across a peering when only one subnet or host needs it widens the blast radius of any compromise. Each peering route covers only the destinations that actually have to talk.
Before you start
The same on every cloud, before the steps in the tabs.
- For each peering connection, record which subnets or hosts on each side need to communicate, and why.
Evidence
- The record of approved flows for each peering connection
Not applicable. This benchmark covers AWS only.
On AWS the tasks list the routes that point at each peering connection, then narrow any that cover more than the approved destinations.
Task 1List the routes that use each peering connection
- Sign in to the AWS Management Console at console.aws.amazon.com and open VPC > Peering connections.
- Note each active connection's ID and the address ranges of the two VPCs.
- Choose Route tables and open each route table in the peered VPCs.
- On the Routes tab, note every route whose Target is a peering connection, and the Destination it covers.
- Compare each destination with the record of approved flows.
Task 2Narrow routes that cover more than needed
- In VPC > Route tables, select a route table with a too-broad peering route and choose Edit routes.
- Remove the route that covers the whole peer VPC range.
- Choose Add route, enter the approved subnet or single host range as Destination, and choose the peering connection as Target.
- Choose Save changes, and make the same change on the other side of the peering.
- Check it: from a host outside the approved range, a connection across the peering fails, while approved hosts still connect.
Evidence
- The Routes tab of each route table with peering routes, matching the approved flows
- The record of approved flows for each peering connection
Not applicable. This benchmark covers AWS only.
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.