What was exposed
Replaying the campaign August 2018 exposure
- 1
Public campaign files
August to October 2018UpGuard examined publicly readable call lists and campaign materials.
- 2
Access after notification
August to October 2018After the October 1 notification, access still extended to any authenticated AWS user. Public access was removed by October 5.
Impact
UpGuard found call lists with contact information for about 527,000 people, along with campaign materials. After notification, the first change still permitted reads by any authenticated AWS user.
Could this have been prevented?
Treat every AWS account as a public audience
If campaign records should be private, enable all four S3 Block Public Access settings on the bucket. S3 treats the global Authenticated Users group as public. These settings block new public ACLs and disregard existing ones. AWS introduced them in November 2018, after the fund closed access in October.
Incident control assessments
- 2
- Prevented
- 0
- Contained
- 0
- Not covered
How it could have been prevented
The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.
Replaying the campaign August 2018 exposure
1 · Public campaign files
1 Prevented2 · Access after notification
1 PreventedKey facts
- Call-list files contained information on about 527,000 people. The source also described campaign planning and outreach materials.
- The intermediate setting required an AWS identity but did not restrict access to the fund’s own AWS account.
- Gizmodo covered the findings on October 17, 2018. The date displayed by UpGuard precedes the October events described in its report.
- UpGuard downloaded just over two gigabytes of material from the public bucket.
Sources
Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.
- 1.Overboard: How Tea Party Campaign Assets Were Exposed OnlineUpGuard · Sep 17, 2018 · ResearchThe initial public read, material inspected, intermediate grant and closure.
- 2.Tea Party Group Leaks Call Lists, Guides for Staging Pro-Gun ‘Student-Led’ High School ProtestsGizmodo · Oct 17, 2018 · NewsDated public coverage on October 17 after closure.
- 3.Blocking public access to your Amazon S3 storageAmazon Web Services · undated · Vendor reportThe four S3 Block Public Access settings and treatment of public ACLs and bucket policies.
- 4.Introducing Amazon S3 Block Public Access – another layer of protection for your accounts and bucketsAmazon Web Services · Nov 15, 2018 · Vendor reportLaunch of the bucket and account settings after these exposures.
The estate in the replay is illustrative and drawn at the level of the exposure; the owner's real environment is not public. Verdicts describe what a control does when it is in place before the data is exposed. They are not an assessment of the owner's security program.