Security group CIDR is formatted unexpectedly

What this check finds

A rule in this security group uses a range that starts at 0.0.0.0 but is not /0, such as 0.0.0.0/8. That is rarely what was meant: it is usually a mistyped 0.0.0.0/0 or a mistyped private range.

Passing looks like: No unexpected security group CIDRs.

How to fix it

Review and correct the oddly-formatted CIDR. Ensure it uses standard CIDR notation (e.g. 10.0.0.0/8).

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs

More Security groups checks

• CriticalSecurity group has critical port open to the internet
• HighDefault VPC security group allows unrestricted traffic
• LowSecurity group has overlapping CIDR rules
• InfoSecurity Group CIDR contains large IP range
• InfoSecurity group contains a redundant CIDR rule

All Security groups checks