Skip to content
Cloud Security Breaches

Capital One breach: what the company and the OCC state

Capital One stated that on 19 July 2019 it determined an outside individual had gained access, and that the incident affected about 100 million people in the United States and 6 million in Canada. The OCC consent order, signed 5 August 2020 and announced 6 August 2020, imposed an $80 million penalty over cloud risk management. Read 16 Nov 2026.

Open the ledger ยท All guides

Capital One stated an outside individual obtained data from March 2019

Capital One's incident page says that on July 19, 2019 the company determined an outside individual gained unauthorized access and obtained personal information about credit card customers and people who had applied for its credit card products. The page says the access occurred on March 22 and 23, 2019 (Capital One, read 16 Nov 2026).

The company wrote that the incident affected approximately 100 million individuals in the United States and approximately 6 million in Canada. It also wrote that no credit card account numbers or log-in credentials were compromised, and that less than one percent of Social Security numbers were compromised.

On discovery, the page says, the company fixed the issue and began working with federal law enforcement, and that the individual was captured by the FBI. It also reports the government's statement that it believes the data has been recovered and that there is no evidence it was used for fraud or shared.

The company says a researcher reported a configuration vulnerability on July 17, 2019

In its FAQ the company says an external security researcher reported a "configuration vulnerability" through its program for security researchers to report vulnerabilities on July 17, 2019, and that its own investigation led to the July 19 determination. That is the only statement about the method of access in the company pages read. The page does not name the cloud provider, the service, the role or the request path involved. The method of access is therefore not public in the sources this ledger accepts, and this page does not describe it further.

What Capital One said was exposed

The company's page groups the data by category. The counts below are as the company stated them.

DataAs Capital One stated it
Credit card applications, 2005 through early 2019Names, addresses, zip or postal codes, phone numbers, email addresses, dates of birth and self-reported income; the largest category
Customer status dataCredit scores, credit limits, balances, payment history and contact information
Transaction dataFragments from a total of 23 days during 2016, 2017 and 2018
U.S. Social Security numbersAbout 140,000 of credit card customers; on January 27, 2021 the company found about 4,700 more among data accessed, not previously known
Linked bank account numbersAbout 80,000, of secured credit card customers
Canadian Social Insurance numbersApproximately 1 million

The OCC assessed an $80 million penalty on August 6, 2020

The Office of the Comptroller of the Currency announced the penalty in news release 2020-101 on August 6, 2020. The agency said it acted on the bank's failure to establish effective risk assessment processes before migrating significant information technology operations to the public cloud environment, and its failure to correct the deficiencies in a timely manner (OCC, read 16 Nov 2026).

The consent order (docket AA-EC-20-49) records the Comptroller's findings, which the bank neither admitted nor denied. In or around 2015 the bank failed to establish effective risk assessment processes before the move, and failed to establish appropriate risk management for the cloud operating environment, including the design and implementation of certain network security controls, adequate data loss prevention controls and effective dispositioning of alerts. The order also finds that internal audit failed to identify numerous control weaknesses and gaps, and that the board failed to take effective action to hold management accountable.

The order does not describe the 2019 incident itself in the pages read. It covers the bank's practices around the cloud move.

Later steps and what remains not public

The company's page records a class action settlement that a federal court preliminarily approved on February 7, 2022. A justice.gov page on the related criminal case returned no readable text on 16 Nov 2026, and no court record was read. For that reason the ledger does not assign this incident an access path from the documents above; the access path field reads not public until a company statement, filing or court document read by the ledger states the mechanism.

Sources

  1. Capital One, Information on the Capital One cyber incident, read 16 Nov 2026
  2. Capital One, 2019 cyber incident FAQ, read 16 Nov 2026
  3. OCC news release 2020-101, read 16 Nov 2026
  4. OCC consent order, AA-EC-20-49, read 16 Nov 2026

Last reviewed 16 Nov 2026.