{
  "Provider": "aws",
  "CheckID": "vpc_peering_routing_tables_with_least_privilege",
  "CheckTitle": "Ensure routing tables for VPC peering are least access.",
  "CheckType": [
    "Infrastructure Security"
  ],
  "ServiceName": "vpc",
  "SubServiceName": "route_table",
  "ResourceIdTemplate": "arn:partition:service:region:account-id:resource-id",
  "Severity": "medium",
  "ResourceType": "AwsEc2VpcPeeringConnection",
  "Description": "Ensure routing tables for VPC peering are least access.",
  "Risk": "Being highly selective in peering routing tables is a very effective way of minimizing the impact of breach as resources outside of these routes are inaccessible to the peered VPC.",
  "RelatedUrl": "",
  "Remediation": {
    "Code": {
      "CLI": "https://docs.bridgecrew.io/docs/networking_5#cli-command",
      "NativeIaC": "",
      "Other": "https://www.trendmicro.com/cloudoneconformity-staging/knowledge-base/aws/VPC/vpc-peering-access.html#",
      "Terraform": ""
    },
    "Recommendation": {
      "Text": "Review routing tables of peered VPCs for whether they route all subnets of each VPC and whether that is necessary to accomplish the intended purposes for peering the VPCs.",
      "Url": "https://docs.aws.amazon.com/vpc/latest/peering/peering-configurations-partial-access.html"
    }
  },
  "Categories": [],
  "DependsOn": [],
  "RelatedTo": [],
  "Notes": ""
}
