Skip to main content
Version: 4.2.0

How to Find AWS VPCs with Default Security Groups Allowing All Inbound Traffic

Even having a perimeter firewall, having security groups open allows any user or malware with vpc access to scan for well known and sensitive ports and gain access to instance.

info

This security check is part of the CIS Amazon Web Services Benchmarks and is rated severity high.

Prerequisites​

This guide assumes that you have already installed and configured Fix Inventory to collect your AWS resources.

Directions​

  1. Execute the following search command in Fix Inventory Shell:

    > search is(aws_ec2_security_group) and name="default" and group_ip_permissions[*].{ip_protocol="-1" and (ip_ranges[*].cidr_ip="0.0.0.0/0" or ipv6_ranges[*].cidr_ipv6="::/0")} <-- is(aws_vpc)
    ​kind=aws_vpc, ..., region=fixinventory-poweruser
    ​kind=aws_vpc, ..., account=poweruser-team

  2. Pipe the search command into the dump command:

    > search is(aws_ec2_security_group) and name="default" and group_ip_permissions[*].{ip_protocol="-1" and (ip_ranges[*].cidr_ip="0.0.0.0/0" or ipv6_ranges[*].cidr_ipv6="::/0")} <-- is(aws_vpc) | dump
    ​reported:
    ​  id: /aws/ec2/123
    ​  name: some-name
    ​  ctime: '2022-12-05T22:53:14Z'
    ​  kind: aws_vpc
    ​  age: 2mo28d

    The command output will list the details of all non-compliant aws_vpc resources.

Remediation​

  • Apply Zero Trust approach.
  • Implement a process to scan and remediate unrestricted or overly permissive network ACLs.
  • Recommended best practices is to narrow the definition for the minimum ports required.
note

Please refer to the AWS EC2 documentation for details.

Further Reading​