The Cost of a Data Breach

Kathrin Gardhouse
Mar 8, 2023
Share this post
Sharing to FacebookSharing to LinkedInSharing to XSharing to Email

The latest data breaches are a regular topic in the news. Raising awareness about the prevalence and severity of the issue, as well as how the financial impact on the business can be limited is what we contribute with this article. We thereby focus on the tangible immediate and long-term costs and the aggravating and mitigating factors that are most influential in determining that cost. We set out the average overall cost, the cost in relevant regions and industries, and the cost per record. In terms of cost factors, we focus on compliance failure, risk quantification, and how AI systems can help.

Average Cost of a Data Breach

According to the 2022 Cost of a Data Breach Report conducted by Ponemon Institute and sponsored by IBM Security, the average cost of a data breach in 2022 was $4.35 million USD. This report covered breaches from a total of 17 countries and regions, spanning 17 industries, and 550 affected organizations. The United States leads the 17 geographic regions with an average cost of $9.44M per breach, followed by the Middle East with $7.46M, and Canada coming in third at $5.64M.

Source: https://www.ibm.com/account/reg/us-en/signup?formid=urx-51643The cost was highest in the healthcare and financial industry, followed by pharmaceuticals and technology.

Source: https://www.ibm.com/account/reg/us-en/signup?formid=urx-51643

Cost Per Record

The report also sets out the cost of a data breach per record. In 2022, it hit a seven-year high at $164 per record, a massive financial burden on businesses considering breaches affected between 2,200 and 102,000 records.

Source: https://www.ibm.com/account/reg/us-en/signup?formid=urx-51643

A record is defined for purposes of the report as “information that identifies the natural person or individual whose information has been lost or stolen in a data breach. Examples include a database with an individual’s name, credit card information and other personally identifiable information (PII) or a health record with the policyholder’s name and payment information.” Mega data breaches, such as that of Equifax or Facebook, are excluded from this calculation due to their atypical nature.

The 2020 Cost of a Data Breach Report differentiated between records containing personally identifiable information (PII) and those that don’t. Breaches of records containing PII were the most frequent breaches, and they cost businesses an average of $150 per record (compared to the 2020 average of $146 per record not containing PII). When the breach was caused by a malicious actor, that cost rose to $175 per record. In comparison, anonymized data that was involved in a breach (which occurred 24 percent of the times) the average cost was $143 per record, and $171 in a malicious attack. The 2022 report does not draw these distinctions.

Cost Factor: Compliance Failure

The healthcare and financial industry are the most highly regulated industries, given the particular sensitivity of the data that is entrusted to organizations in these sectors, for example personal health information (PHI) protected under HIPAA, and financial information that must be protected under the Payment Card Industry Data Security Standards (PCI DSS). Especially in these industries, the cost associated with compliance failure contributes notably to the cost of a data breach.In the following section we first provide general information on administrative fines imposed for a failure to report data breaches under different data protection laws, followed by further details on the average compliance failure costs as detailed in the report.

What You Need to Know

Most data protection laws require organizations to report data breaches to a supervisory authority, imposing hefty fines in case of a failure to do so. For example, Art. 83(4)(a) of the European General Data Protection Regulation (GDPR) provides for administrative penalties up to as high as 10 million EUR or two percent of the total worldwide annual turnover of the preceding financial year for infringing Art. 33 or 34, the obligation to notify the supervisory authority and the individual concerned, respectively, of a breach involving personal data.Similarly, § 164.404 and § 164.408 HIPAA require the notification of the individual concerned and the Secretary. Fines for a violation are regulated in § 1320d-5(a)(3) of the Health Information Technology for Economic and Clinical Health (HITECH) Act and can range, depending on the culpability of the person, between $100 USD per violation capped at $25,000, and $50,000 per violation, capped at $1,500,000.

Compliance Failure Cost

In the healthcare and financial industries 24 percent of the costs of a data breach accrue more than two years after the breach, compared to only 8 percent in industries with low regulation. This “longtail” cost is most likely attributable to regulatory and legal costs that take some time to show up on the balance sheet.

Source: https://www.ibm.com/account/reg/us-en/signup?formid=urx-51643In addition, when comparing organizations with a high impact of the cost factor ‘compliance failure’ and a low impact of that factor, the breach cost for the former is $5.57M, compared to a cost of $2.26M for the latter, a difference of 50.9 percent.Overall, compliance failure is the third most expensive factor contributing to the cost of data breaches, topped only by security system complexity and cloud migration.

Mitigating Cost Factor: Risk Quantification

Turning to another impactful, yet mitigating, cost factor, the report suggests that an average of $2.1M was saved by companies that employed risk quantification techniques versus organizations that didn’t.Risk quantification is a method that determines, first, the potential financial impacts of each cyber threat, and second, the probabilities of their occurrence. A popular, international standard for this purpose is the Factor Analysis of Information Risk (FAIR).As part of risk quantification efforts, it is key to know what an organization is trying to protect. If it is unknown what kind of data is under the control of the organization, its value cannot be determined. Knowing the value of the information will factor into the probability of a threat, and the financial impact of a threat, too, will differ with the kind of information the organization is trying to protect.It is therefore paramount to identify and classify the information in the possession of the organization, and to determine the data risk as well as the degree of protections required throughout the information lifecycle. The determination of the required protection is informed by the classification of the types of information, the sensitivity, and the risk to the organization. Some information organizations are legally required to protect, such as personally identifiable information (PII), PHI, and PCI data.

How We Can Help

The most effective mitigating factors, measured by cost savings, are the formation of an incidence response team, implementation of an AI security platform, and DevSecOps, a development practice that bakes security initiatives right into every stage of the software development lifecycle.Private AI can help mitigate the cost of a data breach by facilitating key measures that the report surfaced as impactful cost factors if not undertaken properly.

Breach Reporting

Private AI has the ability to produce a precise report indicating the location and type of PII in the affected data, which can save a considerable amount of time. This is particularly important in cases where there are tight deadlines for reporting data breaches. The GDPR requires reporting “without undue delay and, where feasible, not later than 72 hours after having become aware of it.” Under HIPAA, reporting of breaches affecting 500 or more individuals must occur “without unreasonable delay and in no case later than 60 days following a breach.” Given that it takes between 61 and 84 days, on average, to contain a data breach resulting from stolen or compromised credentials, to take an example from the report, even a 60-day reporting period can seem short, given the competing demands on everyone’s time during data breach incidents. Having tools to aid with the issuing of the report can be instrumental in avoiding significant fines.

Risk Quantification

As we have seen, being prepared for a data breach – and it will come – saves a good deal of money. Risk quantification is one measure to take pre-emptively. Private AI’s reporting abilities will come in handy here as well. The solution can identify and classify the data in the organization’s system, enabling the responsible person to properly assess the risk the business is exposed to. Furthermore, the cheapest data, from a risk perspective, is data the organization does not have in the first place. Private AI can redact and replace personally identifiable information, making it much less valuable to malicious actors while maintaining its value for the organization, in certain circumstances.

Conclusion

There is no sugar-coating it, (1) data breaches are steadily increasing in frequency (up by 2.6 percent compared to 2021). They are likely to occur; it is a question of when, not if, and (2) data breaches are expensive, but less so if the organization is not caught off guard and has implemented appropriate safeguards in advance. If that seems like an expensive undertaking, you are not wrong. But weighed against the cost of not doing it, these precautions are worth it. And we can help. Try our web demo to see for yourself, or talk to an expert today.Download the infographic:

Data Left Behind: AI Scribes’ Promises in Healthcare

Data Left Behind: Healthcare’s Untapped Goldmine

The Future of Health Data: How New Tech is Changing the Game

Why is linguistics essential when dealing with healthcare data?

Why Health Data Strategies Fail Before They Start

Private AI to Redefine Enterprise Data Privacy and Compliance with NVIDIA

EDPB’s Pseudonymization Guideline and the Challenge of Unstructured Data

HHS’ proposed HIPAA Amendment to Strengthen Cybersecurity in Healthcare and how Private AI can Support Compliance

Japan's Health Data Anonymization Act: Enabling Large-Scale Health Research

What the International AI Safety Report 2025 has to say about Privacy Risks from General Purpose AI

Private AI 4.0: Your Data’s Potential, Protected and Unlocked

How Private AI Facilitates GDPR Compliance for AI Models: Insights from the EDPB's Latest Opinion

Navigating the New Frontier of Data Privacy: Protecting Confidential Company Information in the Age of AI

Belgium’s Data Protection Authority on the Interplay of the EU AI Act and the GDPR

Enhancing Compliance with US Privacy Regulations for the Insurance Industry Using Private AI

Navigating Compliance with Quebec’s Act Respecting Health and Social Services Information Through Private AI’s De-identification Technology

Unlocking New Levels of Accuracy in Privacy-Preserving AI with Co-Reference Resolution

Strengthened Data Protection Enforcement on the Horizon in Japan

How Private AI Can Help to Comply with Thailand's PDPA

How Private AI Can Help Financial Institutions Comply with OSFI Guidelines

The American Privacy Rights Act – The Next Generation of Privacy Laws

How Private AI Can Help with Compliance under China’s Personal Information Protection Law (PIPL)

PII Redaction for Reviews Data: Ensuring Privacy Compliance when Using Review APIs

Independent Review Certifies Private AI’s PII Identification Model as Secure and Reliable

To Use or Not to Use AI: A Delicate Balance Between Productivity and Privacy

To Use or Not to Use AI: A Delicate Balance Between Productivity and Privacy

News from NIST: Dioptra, AI Risk Management Framework (AI RMF) Generative AI Profile, and How PII Identification and Redaction can Support Suggested Best Practices

Handling Personal Information by Financial Institutions in Japan – The Strict Requirements of the FSA Guidelines

日本における金融機関の個人情報の取り扱い - 金融庁ガイドラインの要件

Leveraging Private AI to Meet the EDPB’s AI Audit Checklist for GDPR-Compliant AI Systems

Who is Responsible for Protecting PII?

How Private AI can help the Public Sector to Comply with the Strengthening Cyber Security and Building Trust in the Public Sector Act, 2024

A Comparison of the Approaches to Generative AI in Japan and China

Updated OECD AI Principles to keep up with novel and increased risks from general purpose and generative AI

Is Consent Required for Processing Personal Data via LLMs?

The evolving landscape of data privacy legislation in healthcare in Germany

The CIO’s and CISO’s Guide for Proactive Reporting and DLP with Private AI and Elastic

The Evolving Landscape of Health Data Protection Laws in the United States

Comparing Privacy and Safety Concerns Around Llama 2, GPT4, and Gemini

How to Safely Redact PII from Segment Events using Destination Insert Functions and Private AI API

WHO’s AI Ethics and Governance Guidance for Large Multi-Modal Models operating in the Health Sector – Data Protection Considerations

How to Protect Confidential Corporate Information in the ChatGPT Era

Unlocking the Power of Retrieval Augmented Generation with Added Privacy: A Comprehensive Guide

Leveraging ChatGPT and other AI Tools for Legal Services

Leveraging ChatGPT and other AI tools for HR

Leveraging ChatGPT in the Banking Industry

Law 25 and Data Transfers Outside of Quebec

The Colorado and Connecticut Data Privacy Acts

Unlocking Compliance with the Japanese Data Privacy Act (APPI) using Private AI

Tokenization and Its Benefits for Data Protection

Private AI Launches Cloud API to Streamline Data Privacy

Processing of Special Categories of Data in Germany

End-to-end Privacy Management

Privacy Breach Reporting Requirements under Law25

Migrating Your Privacy Workflows from Amazon Comprehend to Private AI

A Comparison of the Approaches to Generative AI in the US and EU

Benefits of AI in Healthcare and Data Sources (Part 1)

Privacy Attacks against Data and AI Models (Part 3)

Risks of Noncompliance and Challenges around Privacy-Preserving Techniques (Part 2)

Enhancing Data Lake Security: A Guide to PII Scanning in S3 buckets

The Costs of a Data Breach in the Healthcare Sector and its Privacy Compliance Implications

Navigating GDPR Compliance in the Life Cycle of LLM-Based Solutions

What’s New in Version 3.8

How to Protect Your Business from Data Leaks: Lessons from Toyota and the Department of Home Affairs

New York's Acceptable Use of AI Policy: A Focus on Privacy Obligations

Safeguarding Personal Data in Sentiment Analysis: A Guide to PII Anonymization

Changes to South Korea’s Personal Information Protection Act to Take Effect on March 15, 2024

Australia’s Plan to Regulate High-Risk AI

How Private AI can help comply with the EU AI Act

Comment la Loi 25 Impacte l'Utilisation de ChatGPT et de l'IA en Général

Endgültiger Entwurf des Gesetzes über Künstliche Intelligenz – Datenschutzpflichten der KI-Modelle mit Allgemeinem Verwendungszweck

How Law25 Impacts the Use of ChatGPT and AI in General

Is Salesforce Law25 Compliant?

Creating De-Identified Embeddings

Exciting Updates in 3.7

EU AI Act Final Draft – Obligations of General-Purpose AI Systems relating to Data Privacy

FTC Privacy Enforcement Actions Against AI Companies

The CCPA, CPRA, and California's Evolving Data Protection Landscape

HIPAA Compliance – Expert Determination Aided by Private AI

Private AI Software As a Service Agreement

EU's Review of Canada's Data Protection Adequacy: Implications for Ongoing Privacy Reform

Acceptable Use Policy

ISO/IEC 42001: A New Standard for Ethical and Responsible AI Management

Reviewing OpenAI's 31st Jan 2024 Privacy and Business Terms Updates

Comparing OpenAI vs. Azure OpenAI Services

Quebec’s Draft Regulation Respecting the Anonymization of Personal Information

Version 3.6 Release: Enhanced Streaming, Auto Model Selection, and More in Our Data Privacy Platform

Brazil's LGPD: Anonymization, Pseudonymization, and Access Requests

LGPD do Brasil: Anonimização, Pseudonimização e Solicitações de Acesso à Informação

Canada’s Principles for Responsible, Trustworthy and Privacy-Protective Generative AI Technologies and How to Comply Using Private AI

Private AI Named One of The Most Innovative RegTech Companies by RegTech100

Data Integrity, Data Security, and the New NIST Cybersecurity Framework

Safeguarding Privacy with Commercial LLMs

Cybersecurity in the Public Sector: Protecting Vital Services

Privacy Impact Assessment (PIA) Requirements under Law25

Elevate Your Experience with Version 3.5

Fine-Tuning LLMs with a Focus on Privacy

GDPR in Germany: Challenges of German Data Privacy (Part 2)

Comply with US Executive Order on Safe, Secure, and Trustworthy Artificial Intelligence using Private AI

How to Comply with EU AI Act using PrivateGPT