Find public facing S3 buckets.
The accidental or deliberate exposure of private data stored in Amazon S3 is a persistent issue. S3 buckets can become public through multiple mechanisms, and keeping track of all of them can be difficult. This Op checks bucket policies and Access Control Lists for the most common inadvertent exposures.
DisruptOps users can choose to lock down the Bucket policy to pre-approved IP addresses, or tagged the instance as approved for Internet access.
Supported Issue Types:
The bucket has an ACL with Public access
- The bucket has an ACL with public permissions
The bucket’s policy allows 0.0.0.0/0 access
- A statement in the bucket policy allows open access from 0.0.0.0/0
- Restrict access to approved IP address
- Tag bucket as public
We spend a lot of time talking to cloud security professionals, basically trying to figure out the best ways to get their jobs done in largely uncharted territory. Cloud technology is evolving at an unprecedented [...]
In Quick and Dirty: Building an S3 guardrail with Config we highlighted one of the big problems with Config: you need to set it up in each region of each account. Your best bet to make [...]