🛡️ Google GCE Network allows unrestricted traffic to PostgreSQL🟢
- Contextual name: 🛡️ Google GCE Network allows unrestricted traffic to PostgreSQL🟢
- ID:
/ce/ca/google/vpc/network-postgresql-access - Tags:
- Policy Type:
COMPLIANCE_POLICY - Policy Categories:
SECURITY
Logic
Description
Description
This policy identifies Google GCE Networks that have Firewall Rules allowing unrestricted incoming traffic (
0.0.0.0/0) from the internet to the PostgreSQL database portTCP/UDP 5432.In GCP, Firewall Rules are defined at the VPC Network level. Each rule either allows or denies traffic based on its configuration. These configurations specify the type of traffic (e.g., protocols and ports) and the source or destination (e.g., IP addresses, subnets, and instances).
Rationale
Exposing a PostgreSQL database directly to the public internet introduces a critical security vulnerability. Publicly accessible databases are common targets for attackers who attempt brute-force login attempts, exploit unpatched vulnerabilities, or launch denial-of-service (DoS) attacks. To maintain strong security posture, PostgreSQL instances should reside in private network segments and be accessible only to trusted application servers and authorized administrative hosts through secure channels.
Impact
All PostgreSQL connections from outside of the network to the concerned VPC(s) can be blocked. If there is a legitimate business requirement for external access, specific trusted source IP addresses should be defined in the firewall rules to whitelist access to the PostgreSQL port for the relevant VPC(s).
... see more
Remediation
Remediation
From Google Cloud Console
- Go to
VPC Network.- Go to the
Firewall Rules.- Click the
Firewall Ruleto be modified.- Click
Edit.- Modify
Source IP rangesto specificIP.- Click
Save.From Google Cloud CLI
Identify Firewall Rules Allowing Public Access
gcloud compute networks get-effective-firewalls default \
--format="table(NAME, DIRECTION, IP_RANGES)" \
--filter="IP_RANGES:0.0.0.0/0 AND DIRECTION:INGRESS"Restrict the Source Range
Once you have identified the firewall rules, update each one to restrict access to trusted CIDR ranges:
gcloud compute firewall-rules update {{firewall-rule-name}} \
--source-ranges={{cidr-range1}},{{cidr-range2}}