Skip to content
Post Mortem

Biggest cases ยท March to July 2019

Capital One: 100 million people and a cloud mistake

A former cloud engineer took personal data on about 100 million Americans and 6 million Canadians from Capital One's cloud storage by exploiting a configuration mistake.

HIGHcloudmisconfigurationbankinginsider-knowledge

Details may change as reporting changes. Information comes from the linked sources, and we do not guarantee it is complete or current.

Why it is on the listAround 106 million people, and an $80 million penalty for not assessing the risks of moving its systems to the cloud.

In plain English

Capital One moved much of its computing to a public cloud. A setting on a firewall was misconfigured, which let someone trick one of its servers into handing over keys to its storage.

The person who did it was a former cloud engineer at the cloud provider, who knew how such systems work. She took credit-card application data, including some Social Security and bank account numbers.

Words used here

Misconfiguration
A setting left wrong, so a door that should be closed is open.
Cloud
Computers and storage that you rent over the internet instead of owning them.

What happened

Capital One disclosed in July 2019 that someone had accessed information relating to about 100 million people in the US and about 6 million in Canada. Some Social Security numbers and bank account numbers were included.

A former engineer at the cloud provider, Paige Thompson, was charged with wire fraud and computer data theft. In August 2020 the US banking regulator, the OCC, fined Capital One $80 million for failing to set up effective risk assessment before moving IT operations to the cloud.

How it unfolded

  1. March 2019

    The data is taken.

  2. July 2019

    Capital One announces the breach after a tip-off.

  3. August 2020

    The OCC fines Capital One $80 million.

Who was affected

About 100 million people in the US and about 6 million in Canada who had applied for or held Capital One credit cards.

What the response was

  • Capital One fixed the setting, told customers and offered free credit monitoring.
  • Police arrested a suspect within weeks of a tip-off.

What went wrong

  • One misconfigured firewall gave access to far more data than it should have.
  • The risks of moving to the cloud were not properly assessed first.

What worked

  • A tip-off led to a quick investigation and an arrest.

What organisations should do differently

  • When you move to a new platform, check what each setting does before you go live.
  • Give each system only access to the data it needs, so one slip does not open everything.

What you can do today

  • If you were told your Social Security number was exposed, freeze your credit reports.
  • If you run cloud services, ask someone to review who can reach your storage.

The lesson that still holds

New technology moves fast and fails on small settings. Review the settings, and give every part only the access it needs.

Sources

Finished this one?

Add it to What I learned and earn 40 Trust. You can open your list from the badge at the bottom of the page.