Security News

AWS Bucket Leaks Viacom Critical Data
2017-09-20 14:18

An Amazon Web Services S3 cloud storage bucket containing a great deal of Viacom internal access credentials and other critical data was left publicly accessible, UpGuard security researchers have...

Four Million Time Warner Cable Records Left on Misconfigured AWS S3 (Threatpost)
2017-09-05 18:06

600 gigabytes of information, including SQL database dumps, code, access logs, and customer information, belonging to BroadSoft and its client, TWC, was left online, accessible to anyone.

Military Contractor’s Vendor Leaks Resumes in Misconfigured AWS S3 (Threatpost)
2017-09-05 16:16

Thousands of resumes and job applications from U.S. military veterans, law enforcement, and others were leaked by a recruiting vendor in an unsecured AWS S3 bucket.

Vendor Exposes Backup of Chicago Voter Roll via AWS Bucket (Threatpost)
2017-08-18 17:55

Voter registration data belonging to the entirety of Chicago’s electoral roll—1.8 million records—was found a week ago in an Amazon Web Services bucket.

Amazon Launches AWS Data Protection Service (Security Week)
2017-08-16 09:57

Amazon announced this week the launch of Macie, a new security service that helps Amazon Web Services (AWS) users discover, classify and protect sensitive data. read more

Experts Warn Too Often AWS S3 Buckets Are Misconfigured, Leak Data (Threatpost)
2017-07-13 13:00

An analysis of Amazon Web Services storage containers reveals troubling trend of misconfigured S3 buckets that leak data.

Over 14 Million Verizon Customers' Data Exposed On Unprotected AWS Server (The Hackers News)
2017-07-12 10:12

Verizon, the major telecommunications provider, has suffered a data security breach with over 14 million US customers' personal details exposed on the Internet after NICE Systems, a third-party...

WWE Exposes Details of 3 Million Customers on AWS (Security Week)
2017-07-07 16:35

In what is likely to be an operator or technician error, WWE left unencrypted personal details of more than 3 million customers exposed on AWS in at least two separate databases. The issue was...