Misconfigured Storage Bucket
Also called Open bucket, Exposed object store.
An object-storage container whose permissions expose data more broadly than intended.
What it is
A storage container whose access policy or access-control settings allow unintended parties, often the entire internet, to list or read its contents. The exposure usually comes from a permissive policy rather than a software flaw.
Why it matters
Open buckets are among the most common and most damaging cloud data leaks, so checking object-store exposure is a standard part of both proactive review and post-incident scoping.
In practice
A responder confirms a customer-data leak originated from a backup bucket left publicly listable after a hurried migration.
What to look for
- Buckets with public read or list permissions.
- Policies granting access to all authenticated users of the provider.
- Anonymous access in storage access logs.
Common mistake
Checking only the bucket policy. Object ACLs and account level settings can also open access.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Amazon GuardDuty Cloud service
AWS threat detection that analyzes CloudTrail, VPC flow logs and DNS logs.
-
Microsoft Defender for Cloud Commercial
Posture and threat protection for Azure, AWS and Google Cloud.
-
Wiz Commercial
Maps cloud resources, identities and exposures into one graph of risk.
-
Prowler Open source
An open source tool that checks cloud accounts against benchmarks such as CIS.
Read next
- Cloud Misconfiguration: A security-weakening setting left in an insecure or default state.
- Security Groups and NACLs: Virtual firewall rules that filter traffic to cloud workloads and subnets.