Control: 3.4 Ensure routing tables for VPC peering are 'least access'
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.
Remediation
From Console
- Logon to VPC console.
- Open the
routing table. Removeandaddroute table entries to ensure that the least number of subnets or hosts as is required to accomplish the purpose for peering are routable.
Usage
Run the control in your terminal:
powerpipe control run alicloud_compliance.control.cis_v100_3_4Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run alicloud_compliance.control.cis_v100_3_4 --shareSQL
This control uses a named query:
select 'arn:acs:::' || account_id as resource, 'info' as status, 'Manual verification required.' as reason , account_id as account_idfrom alicloud_account;