global average breach cost
IBM reported this global average in its 2026 Cost of a Data Breach research.
IBM 2026 Cost of a Data Breach · 2026 ↗Updated 2026-10-04 · Application security
A source-first view of change quality, recovery speed and whether the running system meets its objectives. Published findings provide context; the measurement framework shows what to calculate inside your own environment.
01 / Published evidence
Each figure links directly to the organization that published it. Vendor telemetry and community surveys are labelled rather than blended into one invented industry average.
IBM reported this global average in its 2026 Cost of a Data Breach research.
IBM 2026 Cost of a Data Breach · 2026 ↗GitHub reported monthly merged pull requests increased 23% year over year.
GitHub Octoverse 2025 · 2025 ↗Verizon derived this median from SSO provider logs across the dataset it analyzed.
Verizon 2025 DBIR credential research · 2025 ↗02 / Your baseline
Use these formulas consistently for at least one complete operating cycle. Keep scope, exclusions and collection dates beside the result.
Changes causing rollback, hotfix or incident ÷ all changes × 100
Median time from impact detection to service restoration
Measurement windows meeting the agreed SLO ÷ all windows × 100
03 / Interpretation
Segment results by environment, workload owner and business criticality. A falling average can hide one critical service getting worse; a rising count can simply reflect better discovery.
Related benchmarks
Gritt can map the data sources, calculate a defensible baseline and implement the changes behind it.
Build the baseline →