Firewall rules should prohibit ingress from 0.0.0.0/0 to port 10255
Firewall rules provide stateful filtering of ingress/egress network traffic to GCP resources. The powerpipe check is titled "Ensure no open firewall rules allow ingress from 0.0.0.0/0 to port 10255". No rule should allow unrestricted ingress access to port 10255.
Firewall rules provide stateful filtering of ingress/egress network traffic to GCP resources. It is recommended that no security group allows unrestricted ingress access to port 10255.
What this control checks
Firewall rules must not allow ingress from 0.0.0.0/0 to port 10255
Audit evidence
Evidence that deployed resources meet this control: PowerPipe control gcp_compliance.control.compute_firewall_rule_ingress_access_restricted_to_postgresql_port_10255.
Framework-specific interpretation
NIST Cybersecurity Framework v2.0: Mapped to PR.IR-01 (Networks and environments are protected from unauthorized logical access and usage.).
Framework mappings
The clauses this control is mapped to in each framework.
Related controls
- Firewall rules should prohibit ingress from 0.0.0.0/0 to port 10250
- Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP port 6379
- Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP ports 7000 or 7001
- Firewall rules should prohibit ingress from 0.0.0.0/0 to TCP or UDP ports 2483-2484
- GKE clusters should have a Network Policy installed
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
compute_firewall_rule_ingress_access_restricted_to_postgresql_port_10255 - Powerpipe Control:
gcp_compliance.control.compute_firewall_rule_ingress_access_restricted_to_postgresql_port_10255
Last reviewed: 2026-10-09