Critical severity
Storage bucket open to the internet
Object storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.
Updated
What it looks like in each cloud
An S3 bucket without Block Public Access, or with a bucket policy or ACL granting access to Everyone / AllUsers.
A Cloud Storage bucket with an IAM binding for allUsers or allAuthenticatedUsers, or without public access prevention enforced.
A storage account that allows anonymous blob access, with a container whose public access level is Blob or Container.
Why it matters
Public buckets are the most common source of large data leaks. Scanners enumerate bucket names continuously, so an exposed bucket is usually found within hours, not months.
How it happens
A bucket is made public for a one-off share or a static website and never locked down again, or an application role is given broad storage permissions that leak into a policy. Account-level public access blocks are off because they were never part of the account setup.
How to check
Review the account-level public access setting first, then every bucket's policy, ACL and IAM bindings for Everyone, AllUsers or allAuthenticatedUsers principals.
How to fix it
Turn on the account-wide block (Block Public Access, public access prevention, or disallow anonymous access), remove the public grants, and serve genuinely public content through a CDN with an origin access policy instead.
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.1.4 (Block Public Access); Google Cloud Foundations 5.1 (no anonymous or public access); Azure Foundations 3.x (public access on blob containers disallowed).
SOC 2
CC6.1 (logical access to data) and CC6.6 (boundaries against external threats).
ISO/IEC 27001
A.5.15 Access control, A.8.3 Information access restriction, A.5.23 Cloud services.
DORA
Art. 9(3) data protection and Art. 9(4)(c) logical access.
NIS2
Art. 21(2)(i) access control and asset management.
PCI DSS v4
Req. 1.3 and 1.4 (no direct access from untrusted networks), Req. 7.2 (need to know).
NIST CSF 2.0
PR.AA-05 (least-privilege access), PR.DS-01 (data at rest protected).
BSI C5
IDM (access to data restricted), AM (asset classification).
DNB Good Practice Information Security
Logical access management; data classification.
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
Root or owner account without MFA
CriticalThe most privileged identity in the account protected by a password alone.
Read moreDatabase reachable from the internet
CriticalA managed database with a public address and a firewall that lets the world in.
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.
