Skip to main content
Back
ExposureAWS
2 min read

Tetrad consumer profiles and retailer data exposed in Amazon S3

Owner
Tetrad
When
Found February 3, 2020 – Feb 10, 2020Disclosed Feb 20, 2020
Entry
A publicly accessible Amazon S3 bucket held market analysis datasets and files associated with Tetrad clients. UpGuard did not identify the policy or access control list that granted access.

A publicly accessible Amazon S3 bucket held market analysis datasets and files associated with Tetrad clients. UpGuard did not identify the policy or access control list that granted access.

What was exposed

Independent discovery
UpGuard
Internet
Amazon S3 storage
Consumer datasets

Tetrad exposure

  1. 1

    Market data stored publicly

    Opening date unknown

    A publicly accessible Amazon S3 bucket held market analysis datasets and files associated with Tetrad clients. UpGuard did not identify the policy or access control list that granted access.

  2. 2

    Consumer profiles readable

    Found February 3, 2020

    An UpGuard analyst downloaded 747 GB. Three files alone held about 130 million rows of household data. That count describes rows and does not establish a count of distinct people.

  3. 3

    Found and closed

    February 10, 2020

    UpGuard notified Tetrad on February 3, 2020. After follow-up calls, Tetrad identified the configuration and removed public access on February 10.

Impact

UpGuard downloaded 747 GB of consumer profiles and client data. Three files contained about 130 million rows of household information. The report did not identify other readers.

Could this have been prevented?

Keep consumer profiles behind authenticated access

If the bucket serves authorized clients, turn on all four S3 Block Public Access settings for it. This blocks public policies and neutralizes public grants in access control lists. A client can use a short-lived link signed by an authorized principal in the bucket owner’s account.

Incident control assessments

1
Prevented
1
Contained
1
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.

Independent discovery
UpGuard
Internet
Amazon S3 storage
Consumer datasets

Tetrad exposure

1 · Market data stored publicly

1 Prevented

2 · Consumer profiles readable

1 Contained

3 · Found and closed

1 Not covered

Key facts

  • UpGuard downloaded the bucket contents, identified sensitive datasets and notified Tetrad.
  • A Tetrad employee confirmed the information and said it would be secured.
  • The analyst’s initial download totaled 747 GB.
  • UpGuard notified Tetrad on February 3, 2020. After follow-up calls, Tetrad identified the configuration and removed public access on February 10.

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. 1.
    Household Names: How Tetrad Exposed Data on 120 Million ConsumersUpGuard · Feb 20, 2020 · ResearchInvestigation, affected environment, data and response.

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.

More cloud attack breakdowns

All breakdowns