Project Description
Determine what VPCs are peered, which accounts are associated, and identify accounts that aren’t controlled by the enterprise.
Summary:
VPC peering connects two virtual networks within AWS. These VPCs do not need to be in the same AWS account, and can even span AWS regions. It isn’t uncommon to find VPCs peered that shouldn’t be; often leftover from previous projects. This creates operational sprawl and potential security risks by expanding the potential blast radius. This op assesses peered VPCs and can be used to identify stale connections, connections from other AWS accounts, and new connections that may not have been expected. It can optionally isolate the connected VPC by implementing a network ACL, or even dissolve the connection.
Supported Issue Types:
- A peered VPC within the same account was found
- A peered VPC from another known/registered account was found
- A peered VPC from another account also owned by your organization was identified
- A peered VPC from an unknown, external account was found
- A peered VPC from the external account with the id was identified
Supported Actions:
- Quarantine the peered network with a new ACL
- Disconnect the peered VPC
Platform:
Related Articles
Sending Events (Like GuardDuty) from CloudWatch to Lambda
Sending Events (Like GuardDuty) from CloudWatch to Lambda Someone pointed me to a Reddit post asking how to send and access the JSON from a GuardDuty finding into Lambda. This is easy if you [...]
Has the Cloud changed Software Development for Good?
Has the Cloud changed Software Development for Good? One of two concepts might have popped into your head when reading the title of this blog. Has software development improved? – OR – Has software [...]
