This "Curious Dev" was trying to play around with AWS S3 bucket policy.
*Statutory warning: Curiosity kills. Never try this stunt while at work. Organizations as big as U.S. Pentagon have faced the music because of this.
The ‘Principal’ element in the policy code specifies the user, account, service, or other entity that is allowed or denied access to a resource residing in AWS S3 bucket. There have been several cases reported across the world about how S3 buckets lead to data leakage. In most cases, that ‘star’ is the culprit.
For more information, visit AWS’ Principal page in the IAM User Guide. To know more about how to restrict Amazon S3 Bucket access to a specific IAM role, click here.
Share your experiences with us.
Do check out TotalCloud Inc.'s new flagship feature Security Group View that will provide visual cues to security loopholes in real-time and in 3D space. Sign-up to try. Want to know how the visual cues to security renders, read this post.
Check out this video that gives a gist of AWS Security Group View:
Want a quick demo? Click here.
Related Reading:
5 Not-to-Ignore Best Practices for AWS NACLs (Network Access Control Lists)
5 Not-to-Ignore Best Practices for AWS Security Groups
Note: Originally published at blog.totalcloud.io on March 20, 2018.
Oldest comments (0)