S3 is a well-known and popular service, but it can be tricky to configure securely. Between ACLS, IAM permissions, and resource policies, it can be easy for an administrator to make a mistake. Attackers reportedly start accessing the data within a few hours when a bucket name is publicly exposed.
A public S3 bucket can expose a range of sensitive data, including personally identifying information (PII), proprietary technology, and – worst of all – credentials. The consequences can be severe. Not only could you face significant fines, but attackers could also carry out more sophisticated attacks using the data they uncover.
Data breaches due to misconfigured S3 buckets are a common news headline, and big-name companies such as Twilio, Accenture, and Verizon have all been victims.
Try this lab to equip yourself and prevent your organization from becoming the next name in the headlines.