Skip to main content
Back
ExposureAWS
2 min read

Global Tel*Link customer data exposed in an AWS test environment

Owner
Global Tel*Link and Telmate
When
Accessible by August 11, 2020 – Aug 13, 2020Disclosed Sep 4, 2020
Entry
A contractor changed security settings on an AWS test environment containing a copy of customer data. The FTC complaint says the database became accessible without a password.

A contractor’s configuration change exposed an AWS test database containing personal information about approximately 649,500 people. The FTC reported that unauthorized parties took data from the database before Global Tel*Link and its partners closed access in August 2020. The FTC did not establish how many people’s records were taken.

What was exposed

Independent discovery
Security researcher
Internet
AWS test environment
Test database

Global Tel*Link and Telmate exposure

  1. 1

    Test settings changed

    On or about August 11, 2020

    A contractor changed security settings on an AWS test environment containing a copy of customer data. The FTC complaint says the database became accessible without a password.

  2. 2

    Test data accessible

    Accessible by August 11, 2020

    The test environment held personal information about approximately 649,500 people. The FTC alleged that outsiders accessed about 44 billion bytes and that forensic analysis confirmed exfiltration.

  3. 3

    Found and closed

    August 13, 2020

    A researcher notified the companies on August 13, 2020. They confirmed the finding and removed internet access. Copies of exposed records subsequently surfaced outside the company.

Impact

The FTC reported that unauthorized parties exfiltrated personal information from the test environment. It contained records about approximately 649,500 people. The FTC did not establish that every person’s data was taken.

Could this have been prevented?

Keep real customer records out of unprotected test systems

Use synthetic or de-identified records for tests wherever possible, and require authentication before anyone can read sensitive data. The FTC identified an unprotected database but did not identify its AWS service or network design. Its findings do not establish which AWS control could have blocked the public connection.

Incident control assessments

0
Prevented
0
Contained
3
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
Security researcher
Internet
AWS test environment
Test database

Global Tel*Link and Telmate exposure

1 · Test settings changed

1 Not covered

2 · Test data accessible

1 Not covered

3 · Found and closed

1 Not covered

Key facts

  • A contractor changed security settings on or about August 11. The database was open to the internet without a password from at least that date.
  • External access was recorded beginning on or about August 12. The complaint reports exfiltration.
  • The FTC complaint placed approximately 649,500 people’s information in the test environment.
  • A researcher notified the companies on August 13, 2020. They confirmed the finding and removed internet access. Copies of exposed records subsequently surfaced outside the company.

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.
    Complaint against Global Tel*Link, Telmate and TouchPayUS Federal Trade Commission · Nov 16, 2023 · AdvisoryInvestigation, affected environment, data and response.
  2. 2.
  3. 3.
  4. 4.
    Incident ResponseTelmate (GettingOut) · undated · Vendor reportCompany response on August 13, 2020.

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