RNC Voter Data on 198 Million Americans Exposed in the Cloud

RNC Voter Data on 198 Million Americans Exposed in the Cloud

One of the largest known US voter data leaks compromised personal information via an unsecured public-storage cloud account set up on behalf of the Republican National Committee.

Millions of voter records containing personal information and “modeled” voter information like religion and race were leaked from an unsecured public storage cloud account owned by Deep Root Analytics, according to an announcement today by UpGuard, which discovered the leak.

The leaked voter information included voter birth dates, home and mailing addresses, phone numbers, party affiliation, self-reported racial information, and “modeled” voter profile, all of which could be accessed without a password, according to UpGuard. This information was held in an Amazon Web Services S3 bucket storage account owned by Deep Root Analytics, which performed work on behalf of the Republican National Committee.

The leak occurred because Deep Root had set the S3 storage bucket files to public permissions, rather than private, says Chris Vickery, an UpGuard cyber risk analyst, who made voter data leak discovery.

Not only were the voter data files publically viewable, but most had permissions to also allow the records to be downloaded, Vickery says.

“Ultimately, what they did wrong was not having some sort of monitoring going on for their externally facing systems,” Vickery says. If Deep Root had put a monitoring system in place, it would have seen the files were improperly set to public. 

Deep Root Analytics acknowledged the voter data leak and took “full responsibility for this situation,” according to a report in The Hill.

Although Deep Root Analytics in The Hill report said the voter data had been exposed since June 1, Vickery says he would not be surprised if the data had been unsecured and public even prior to that time.

Vickery ran across the Deep Root data on June 12, when he discovered an open cloud repository in an Amazon Web Services S3 bucket. Vickery, at the time of the discovery, was searching for misconfigured data sources for UpGuard. It turned out that anyone pursuing the Internet and traveling to Amazon’s sub-domain “dra-dw” would have come across Deep Root’s data warehouse, according to UpGuard.

Upon this discovery, Vickery said he realized Deep Root may have violated state laws and decided to contact federal authorities before reaching out to the company. Later that same day, the voter data became no longer accessible, Vickery says. He’s not sure if Deep Root fixed it on its own accord, or whether it was fixed because federal authorities contacted the company.

Leaks With Amazon Web Services S3

The situation with Deep Root is not the first time a company has left its data exposed to the public. Government contractor Booz Allen Hamilton recently left 60,000 documents of sensitive US data exposed on AWS S3, which Vickery also discovered.

He says it’s very common to find S3 files that are incorrectly marked to a public setting. Amazon has a shared risk model, which requires its clients to take responsibility for the permission settings they put on their files, Vickery notes.

“The take-away for CISOs is they need to take a hard look at what data you want in the cloud,” Vickery advises. He notes that highly sensitive data may be better housed in a non-cloud environment.

And if a company does opt to use a third-party vendor to store sensitive data, Vickery says, “You have to be real careful and look at the reputation of the company you are dealing with. But sometimes it’s hard to know, so you need to trust but verify if you have the spare bandwidth.”

Paul Fletcher, a security evangelist with Alert Logic, shares a similar sentiment.

“The fact that this exposure was discovered on a public cloud site is irrelevant, in fact, if the AWS suite of security tools and log collection capabilities were properly implemented, this massive data exposure could’ve been avoided,” Fletcher said in a statement.

Amazon S3 comes with an access control list (ACL) that requires its default settings be changed to the appropriate permissions, as well as its settings maintained and audited by the organization using S3. 

Black Hat USA returns to the fabulous Mandalay Bay in Las Vegas, Nevada, July 22-27, 2017. Click for information on the conference schedule and to register.

 

Related Content:

Dawn Kawamoto is an Associate Editor for Dark Reading, where she covers cybersecurity news and trends. She is an award-winning journalist who has written and edited technology, management, leadership, career, finance, and innovation stories for such publications as CNET’s … View Full Bio

More Insights

from Dark Reading – All Stories http://ubm.io/2sjt0by
via IFTTT

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s