💼 5.6 Ensure routing tables for VPC peering are "least access" (Manual)
- ID:
/frameworks/cis-aws-v5.0.0/05/06
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-v4.0.1/05/06/frameworks/cis-aws-v6.0.0/06/06
Similar Sections (Take Policies From)
| Section | Sub Sections | Internal Rules | Policies | Flags | Compliance |
|---|---|---|---|---|---|
| 💼 CIS AWS v4.0.1 → 💼 5.6 Ensure routing tables for VPC peering are "least access" (Manual) | 1 | no data | |||
| 💼 CIS AWS v6.0.0 → 💼 6.6 Ensure routing tables for VPC peering are "least access" (Manual) | 1 | no data |
Similar Sections (Give Policies To)
| Section | Sub Sections | Internal Rules | Policies | Flags | Compliance |
|---|---|---|---|---|---|
| 💼 CIS AWS v4.0.1 → 💼 5.6 Ensure routing tables for VPC peering are "least access" (Manual) | 1 | no data | |||
| 💼 CIS AWS v6.0.0 → 💼 6.6 Ensure routing tables for VPC peering are "least access" (Manual) | 1 | no data |
Sub Sections
| Section | Sub Sections | Internal Rules | Policies | Flags | Compliance |
|---|
Policies (1)
| Policy | Logic Count | Flags | Compliance |
|---|---|---|---|
| 🛡️ AWS VPC Route Table for VPC Peering does not follow the least privilege principle🟢⚪ | 🟢 x2, ⚪ x1 | no data |