Security groups do not allow all ingress traffic from the Internet
networking_security_group_allows_all_ingress_from_internet
OpenStack security groups are evaluated to verify that no rule allows all ingress traffic (any protocol, any port) from the Internet (0.0.0.0/0 or ::/0). A rule with no protocol and no port restriction is effectively a "permit any" firewall rule, completely bypassing network-level access controls. This is the most permissive possible configuration and should never be used in production.
Risk
Allowing all inbound traffic from the Internet exposes every service on the instance to unauthorized access. Attackers can exploit any listening service including databases, management interfaces, and internal APIs. This bypasses defense-in-depth and enables initial access, lateral movement, data exfiltration, and infrastructure compromise.
prowler openstack --checks networking_security_group_allows_all_ingress_from_internet
Recommendation
Remove rules that allow all ingress traffic from the Internet. Follow the principle of least privilege by creating specific rules for only the required protocols and ports. Use security group references (remote_group_id) instead of CIDRs where possible to restrict access to known infrastructure components.
Remediation
- Navigate to Network > Security Groups
- Locate the security group with unrestricted ingress
- Click Manage Rules
- Delete rules allowing all traffic from 0.0.0.0/0 or ::/0 with no protocol/port restriction
- Create specific rules for only the protocols and ports required (e.g., TCP 443 for HTTPS)
- Restrict source CIDRs to known IP ranges where possible
- Save changes and verify connectivity
Source Code
Resource Type
OS::Neutron::SecurityGroup
References
Related To
- networking_security_group_allows_ssh_from_internet
- networking_security_group_allows_rdp_from_internet