Critical severity
Database reachable from the internet
A managed database with a public address and a firewall that lets the world in.
Updated
What it looks like in each cloud
An RDS instance or cluster with Publicly Accessible set to yes and a security group allowing its port from 0.0.0.0/0.
A Cloud SQL instance with a public IP and an authorised network of 0.0.0.0/0, or SSL not required.
An Azure SQL, PostgreSQL or MySQL server with public network access enabled and a firewall rule spanning 0.0.0.0 to 255.255.255.255.
Why it matters
Databases hold the data every attack path is heading for. A public endpoint removes every network hop between an attacker and a credential-guessing attempt.
How it happens
Public access is enabled so a developer can connect from a laptop, or because a managed service defaulted to it years ago. Authorised networks are widened to any during an outage and never narrowed.
How to check
For every managed database, confirm whether it has a public address, what the firewall or authorised networks allow, and whether encrypted connections are required.
How to fix it
Disable public access and connect over private networking, VPN or a proxy. If a public endpoint is unavoidable, restrict it to specific addresses and require TLS.
Frameworks that require this
The controls this issue falls under. AKRIBOS reports the finding once and maps it to each framework you have in scope.
CIS Benchmarks
AWS Foundations 2.3.3 (RDS instances not publicly accessible); Google Cloud Foundations 6.x (Cloud SQL not open to the world, SSL required); Azure Foundations 4.x (public network access disabled).
SOC 2
CC6.1 (access to data) and CC6.6 (network boundaries).
ISO/IEC 27001
A.8.3 Information access restriction, A.8.20 Networks security.
DORA
Art. 9(4)(b) network segregation, Art. 9(3) data protection.
NIS2
Art. 21(2)(e) and 21(2)(i).
PCI DSS v4
Req. 1.4.4 (systems storing account data not directly accessible from untrusted networks).
NIST CSF 2.0
PR.IR-01 (segmentation), PR.DS-01 (data at rest).
BSI C5
COS (segmentation), IDM (access to data).
DNB Good Practice Information Security
Network security; logical access management.
How AKRIBOS handles it
AKRIBOS finds this during a read-only review of every connected account, project and subscription, shows the exact resource and setting behind the finding, and ranks it by the attack path it enables rather than in isolation. The fix is proposed as CLI commands or Terraform for you to review and approve, and the approval is recorded in the audit trail together with the compliance controls it satisfies.
Related issues
Storage bucket open to the internet
CriticalObject storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.
Read moreRoot or owner account without MFA
CriticalThe most privileged identity in the account protected by a password alone.
Read moreSnapshots or machine images shared publicly
CriticalDisk snapshots, database snapshots or machine images that anyone with a cloud account can copy.
Read moreAttackers don't wait for your next audit. Neither does AKRIBOS.
Connect AWS, Google Cloud or Azure and get your first review today.
