Skip to content
Breach Index · posture trend

IBM: the firm that prices everyone’s breach, graded on its own house

IBM publishes the industry-standard Cost of a Data Breach Report and runs the X-Force threat team — so it quite literally sets the benchmark the rest of the industry cites for what a breach costs. This is a sourced, dated look at IBM’s own documented exposure, which is concentrated not in a splashy corporate hack but in its role as a data processor. Not a hit piece: every entry is tagged by verification level and linked to its source, and uncertainty is preserved.

The uncomfortable question: if the company that quantifies the cost of a data breach for the whole industry — and runs one of the world’s best-known threat-intelligence practices — still exposed roughly 4.1 million Americans’ Medicaid records because of a file-transfer tool it chose to operate, what does that say about third-party risk for everyone else? The honest answer is that measuring the risk is not the same as being exempt from it. IBM’s own report names third-party involvement, unpatched known-exploited vulnerabilities and sensitive regulated data as cost multipliers — and that is exactly the shape of its strongest documented incident.

How to read the tags

Confirmed

Company-acknowledged, regulator/state-confirmed, or evidenced by official breach notification.

Reported

Credible reporting; scope or a figure is not yet fully confirmed or disclosed.

Unverified claim

An allegation (here, from a whistleblower lawsuit) that IBM disputes and that has not been adjudicated or confirmed by independent evidence.

Incident timeline

May–August 2023Confirmed

IBM’s use of MOVEit exposes ~4.1M Colorado Medicaid records (Cl0p / CVE-2023-34362)

What happened

IBM provides services to the Colorado Department of Health Care Policy & Financing (HCPF), the state’s Medicaid agency, and used Progress Software’s MOVEit Transfer to move HCPF data files. In the mass exploitation of the MOVEit zero-day (CVE-2023-34362) by the Cl0p ransomware gang, files IBM was transferring were accessed by an unauthorized actor on or about May 28, 2023; HCPF identified the access on June 13, 2023. HCPF stated “certain HCPF files on the MOVEit application used by IBM were accessed,” and that no HCPF systems were impacted. IBM told SecurityWeek it worked with the affected agencies and that “there has been no impact to IBM systems.”

Impact

HCPF notified close to 4.1 million individuals (Health First Colorado / Medicaid and Child Health Plan Plus members), beginning August 11, 2023. Reported data fields include names, addresses, dates of birth, Social Security numbers, demographic/income information, clinical and medical data, Medicaid/Medicare IDs and health insurance information — among the most sensitive categories there are. The breach was of client data IBM was processing, not of IBM’s own corporate network — which is precisely the third-party/processor exposure IBM’s own reports warn about.

Source: TechCrunch, 14 Aug 2023; SecurityWeek, Aug 2023
May–August 2023Confirmed

Missouri Medicaid data also exposed via IBM Consulting’s MOVEit use

What happened

Missouri’s Department of Social Services (DSS) disclosed on August 8, 2023 that IBM Consulting, a DSS vendor, had informed it that MOVEit data IBM handled was accessed in the same campaign. DSS said its own systems were not breached, but that data on the MOVEit server was affected. IBM confirmed to SecurityWeek that it worked with DSS as well as with Colorado.

Impact

DSS said it was notifying all Missouri Medicaid recipients as a precaution; a final affected count was not publicly confirmed at disclosure. The MOVEit server reportedly held names, DSS client numbers, dates of birth, benefit eligibility/coverage status and medical-claims information. Two state Medicaid agencies exposed through one vendor’s file-transfer tool is a textbook concentration-of-risk / supply-chain story.

Source: BleepingComputer, Aug 2023; Infosecurity Magazine, Aug 2023
Filed under seal 2020; made public June 2026Unverified claim

Whistleblower lawsuit alleges IBM concealed foreign-state intrusions — IBM disputes it

What happened

A former IBM vice president of threat intelligence, William Barlow, alleges in a complaint (originally filed under seal in 2020, unsealed and reported in June 2026) that IBM and AT&T gave false assurances about the security of cloud systems IBM operated — including for the federal government — and concealed repeated intrusions from regulators and government clients. Barlow ties the matter to the APT10 campaign the U.S. Justice Department described in 2018, alleging an internal investigation found more than 50,000 “potential APT 10 hits” between 2013 and 2016, and that IBM did not retain access logs. IBM says it “is confident that our actions followed the letter of the law.”

Impact

These are untested allegations from civil litigation, not findings. The U.S. Department of Justice declined to intervene, and the case is reported as still pending. IBM denies wrongdoing. The specific intrusion counts and the concealment claim are the plaintiff’s characterizations and should not be read as established fact — they are included here only as a disputed, dated claim, flagged as such.

Source: Fortune / Bloomberg, 4 Jun 2026; Claims Journal, 5 Jun 2026

The posture trend

IBM is a genuinely different case from a classic enterprise breach subject. There is no confirmed, large-scale compromise of IBM’s own corporate network on the public record — which, for a company this size and this exposed, is itself notable. Its documented risk shows up somewhere more interesting: in what IBM holds and processes for other people.

1. Processor / supply-chain exposure (2023)

The MOVEit episode is the clearest signal. IBM was the vendor that chose and operated Progress Software’s MOVEit Transfer to move sensitive state Medicaid data. When the tool’s zero-day (CVE-2023-34362) was mass-exploited by Cl0p, the client data IBM was handling for Colorado and Missouri was exposed — roughly 4.1 million people in Colorado alone. IBM’s true statement that “there has been no impact to IBM systems” is exactly the point: the blast radius was downstream of IBM’s internal network, in the data it processes. For a firm whose business is handling other organizations’ most sensitive information, that is the attack surface.

2. The measurement irony

IBM’s annual Cost of a Data Breach Report names the precise ingredients of its own MOVEit exposure as the expensive ones: third-party involvement, exploitation of a known vulnerability, and highly sensitive regulated (healthcare) data — the costliest sector in IBM’s own 2025 figures at about $7.42 million per breach. The firm that teaches the industry to price these risks met them in the same form. That is not hypocrisy; it is evidence that the risks are structural and spare no one.

3. A disputed, unadjudicated claim (2020 / 2026)

The Barlow whistleblower suit, unsealed in 2026, alleges concealment of earlier foreign-state intrusions. It is unproven, IBM disputes it, and the DOJ declined to intervene — so it does not change the confirmed record. It is included only because transparency about what is claimedversus confirmed is the whole discipline this index is built on.

The trajectory is not “IBM is uniquely insecure.” It is that even the organization that benchmarks breach cost for everyone else carries real risk precisely where its reports say risk lives — in third parties, in tooling, and in the sensitive data it is trusted to hold.

CISO takeaways

Turn the pattern into action. Each links to a free or Pro PlayCISO tool or guide that addresses it directly.

Sources

Dated, primary where possible. The whistleblower suit is cited as an unadjudicated allegation; IBM’s and the states’ own statements are included where made. Reviewed as of October 16, 2026.

  1. 1.Millions of Americans’ health data stolen after MOVEit hackers targeted IBM — TechCrunch (Zack Whittaker), 14 Aug 2023
  2. 2.Colorado Health Agency Says 4 Million Impacted by MOVEit Hack — SecurityWeek, Aug 2023
  3. 3.Health Data of Millions Impacted by MOVEit Exploit at IBM — TechTarget / HealthITSecurity, Aug 2023
  4. 4.Missouri warns that health info was stolen in IBM MOVEit data breach — BleepingComputer, Aug 2023
  5. 5.Breach Connected to MOVEit Flaw Affects Missouri Medicaid Recipients — Infosecurity Magazine, Aug 2023
  6. 6.IBM, AT&T Accused by Whistleblower of Covering Up Foreign Hacks — Fortune / Bloomberg, 4 Jun 2026
  7. 7.IBM, AT&T Accused by Whistleblower of Covering Up Foreign Hacks — Claims Journal, 5 Jun 2026
  8. 8.Cost of a Data Breach Report 2025 — key findings (global avg $4.44M; US $10.22M high) — CyberScoop, Jul–Aug 2025

Frequently asked questions

Has IBM itself been breached?

IBM’s own corporate network has no large, publicly confirmed compromise on the record. Its strongest documented incidents are as a data processor: in 2023, files IBM was transferring with Progress Software’s MOVEit tool were accessed in the Cl0p zero-day campaign, exposing roughly 4.1 million Colorado Medicaid records and Missouri Medicaid data. IBM’s position is that “there has been no impact to IBM systems” — the exposure was of client data IBM handled, not of IBM’s internal environment. Separately, a 2020 whistleblower lawsuit (unsealed in 2026) alleges IBM concealed foreign-state intrusions; IBM disputes it and it is unadjudicated. See the verification tags on the timeline.

Isn’t IBM the company that publishes the Cost of a Data Breach Report?

Yes — which is the whole point of this page. IBM publishes the industry-standard annual Cost of a Data Breach Report (the 2025 edition put the global average at about $4.44 million, the U.S. average at an all-time-high $10.22 million, and healthcare highest at $7.42 million) and runs the X-Force threat-intelligence team. That makes IBM the firm that quantifies everyone else’s breach cost. The irony is instructive, not a gotcha: the structural risks IBM measures — third-party/processor exposure, unpatched known-exploited vulnerabilities, high-value sensitive data — are the same ones that produced its own documented exposure through MOVEit.

Was the MOVEit incident IBM’s fault?

It is shared, and worth stating precisely. The root cause was a zero-day vulnerability in a third-party product (Progress Software’s MOVEit Transfer, CVE-2023-34362), exploited by the Cl0p gang against more than a thousand organizations worldwide. But IBM was the processor that chose and operated MOVEit to move sensitive state Medicaid data, so when the tool was exploited, the client data IBM held was exposed. That is exactly the vendor/supply-chain accountability that breach-cost research — including IBM’s own — flags as a cost multiplier.

Is the Barlow whistleblower lawsuit a confirmed IBM breach?

No. It is an unverified allegation from civil litigation. Former IBM threat-intelligence VP William Barlow alleges IBM concealed repeated foreign-state intrusions (tied to the 2013–2016 APT10 campaign) and gave false assurances to government clients. IBM says it “is confident that our actions followed the letter of the law,” the U.S. Department of Justice declined to intervene, and the case is reported as still pending. Treat the intrusion counts and the concealment claim as the plaintiff’s characterizations, not established fact, until a court says otherwise.

Does selling and measuring cyber risk make a firm immune to it?

No. IBM sets the benchmark the whole industry cites for breach cost and runs a world-class threat-intelligence practice, yet its documented exposure traces to the same fundamentals it measures: third-party tooling, a known-exploited vulnerability, and highly sensitive regulated data. Expertise and measurement sharpen detection and response and lower the odds; they do not exempt an organization from vendor risk, patch discipline and data-minimization. That is the defensible lesson for any security leader — not that IBM is uniquely insecure.

Not affiliated. PlayCISO is independent and has no affiliation with, endorsement from, or sponsorship by IBM Corporation. “IBM”, “X-Force” and “Cost of a Data Breach Report” are used nominatively to refer to the company and its publications. This page is sourced commentary and analysis for security-education purposes; confirmed facts are attributed to dated public sources, and disputed or unproven matters are labelled as claims. Nothing here is a statement that IBM’s own corporate systems were breached beyond what the cited sources support.

Part of the PlayCISO Breach Index — sourced posture trends for the firms that sell cyber defence.

🎉 New here? Use code WELCOME10 for 10% off any plan at checkout
IBM Cyber Breach Index — Posture Trend & Timeline | PlayCISO · PlayCISO