Skip to main content
Back
ExposureAWS
2 min read

Patient billing records exposed in Medico’s cloud storage

Owner
Medico and patients represented in its billing records
When
Initial exposure date unreportedDisclosed Jul 17, 2019
Entry
Patient billing documents were reachable from public Amazon S3 storage.

Independent researchers found two Medico storage buckets containing patient records. One reporter confirmed that a collection of more than 300,000 files was readable without signing in. UpGuard analyzed about 14,000 documents in a separate bucket.

What was exposed

Outside Medico
Researcher
Internet
Medico storage
Billing documents

Medico storage

  1. 1

    A public index identifies billing files

    June 15

    The DataBreaches reporter found a Medico storage bucket through a publicly searchable index on June 15. The reporter identified patient billing documents in the collection.

  2. 2

    The larger bucket serves records without a login

    At discovery

    That S3 bucket served files without requiring a login. The reporter counted 307,139 files and distinguished the collection from the one UpGuard examined.

  3. 3

    Researchers notify Medico and access is restricted

    June 2019

    DataBreaches contacted Medico about the larger collection. UpGuard separately reported that its bucket was closed within hours of notification. Medico later described restricting a storage server.

Impact

The larger bucket held more than 300,000 files. The number of files is distinct from the number of patients, which the sources do not establish.

Could this have been prevented?

Restrict reads of billing records at the bucket

An S3 bucket policy that denies anonymous reads can protect the billing documents even if an external index retains a reference to them. Review each storage collection separately so the fix covers both the bucket that drew the first report and other locations holding patient information.

Incident control assessments

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

Outside Medico
Researcher
Internet
Medico storage
Billing documents

Medico storage

1 · A public index identifies billing files

1 Not covered

2 · The larger bucket serves records without a login

1 Prevented

3 · Researchers notify Medico and access is restricted

1 Not covered

Key facts

  • The DataBreaches reporter found the larger bucket on June 15.
  • The larger bucket held 307,139 files and did not require a login.
  • UpGuard separately analyzed about 14,000 documents in another bucket.
  • Medico’s public notice says it restricted access and reconfigured a storage server.

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.
    HIPAA nightmare: An IT vendor’s error left more than 300,000 files with protected health information exposedDataBreaches.net · Jul 17, 2019 · ResearchFirst-person discovery and anonymous read of a second S3 bucket, explicitly distinguished from UpGuard’s bucket.
  2. 2.
    Medical Procedure: How a Misconfigured Storage Bucket Exposed Medical DataUpGuard · Jul 17, 2019 · ResearchSeparate finding of roughly 14,000 billing and other documents and restriction following notification.
  3. 3.
    Medico Security Incident NotificationMedico · Dec 11, 2019 · Vendor reportCompany account of reconfiguring a storage server and restricting public access.
  4. 4.
    Bucket policies for Amazon S3Amazon Web Services · undated · Vendor reportResource policies can control which principals may read or write specified objects.
  5. 5.
    Policy evaluation logicAmazon Web Services · undated · Vendor reportAn applicable explicit denial takes precedence over an allow.

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