Check ID:
Provider: AWS
Service:
Severity: HIGH
Categories:
Resource type:
ec2_securitygroup_allow_wide_open_public_ipv4Provider: AWS
Service:
ec2Severity: HIGH
Categories:
internet-exposedResource type:
AwsEc2SecurityGroupWhat this check verifies
EC2 security groups with rules that permit non-RFC1918 IPv4 ranges wider than/24 are identified across both ingress and egress.
The focus is on public CIDRs (/1-/23) that broadly expose sources or destinations, not on private networks.
Risk
Over-broad public CIDRs expand exposure and enable:- Confidentiality loss via unauthorized access and exfiltration
- Integrity compromise by exploiting exposed services
- Availability impact from scanning and abuse
Recommendation
Apply least privilege on security groups:- Allow only known IPs (prefer
/32or tight CIDRs) - Use private connectivity (VPN, Direct Connect, private endpoints)
- Restrict and log egress; deny by default
- Segment with security group references and network ACLs for defense-in-depth
Remediation
- Terraform
- Native IaC
- Dashboard steps
References
- https://support.icompaas.com/support/solutions/articles/62000229600-ensure-vpc-security-groups-not-wide-open-public-ipv4-cidr-ranges-non-rfc1918-
- https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = ec2_securitygroup_allow_wide_open_public_ipv4. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks