30 Days Gen AI Risk Trial -Start Now
Skip to main content
10 source-linked findings

AI Security Statistics 2026: What the Sources Show

Selected findings from IBM/Ponemon's 2025 breach study and OWASP's 2025 LLM risk list. IBM studied 600 organisations that had already experienced a data breach, so its percentages are not prevalence estimates for every enterprise.

13%
AI-model breach in IBM's sample
97%
of that subset lacked AI access controls
1 in 5
shadow-AI breach in IBM's sample
US$670K
higher average breach cost with high shadow AI use

Breaches involving AI models and applications

13%

of the 600 already-breached organisations in IBM's study reported a breach of AI models or applications.

IBM/Ponemon, 2025
97%

of IBM's AI-model or application-breach subset reported that they had no AI access controls in place.

IBM/Ponemon, 2025

Shadow AI and exposed data

1 in 5

of the 600 already-breached organisations reported a breach due to shadow AI.

IBM/Ponemon, 2025
US$670K

higher average breach cost among organisations with high shadow AI use than among those with low or no shadow AI use in IBM's study.

IBM/Ponemon, 2025
65%

of incidents involving shadow AI compromised personally identifiable information, versus 53% of breaches overall in IBM's study.

IBM/Ponemon, 2025
40%

of incidents involving shadow AI compromised intellectual property, versus 33% of breaches overall in IBM's study.

IBM/Ponemon, 2025

Governance in the breach sample

63%

of IBM's breached organisations had no AI governance policy or were still developing one.

IBM/Ponemon, 2025
34%

of organisations in IBM's study with an AI governance policy regularly audited unsanctioned AI use.

IBM/Ponemon, 2025

Broader breach and LLM risk context

US$4.44M

global average cost across all breach types in IBM's 2025 study. This is not an AI-specific breach average.

IBM/Ponemon, 2025
LLM01

OWASP places prompt injection first in its 2025 Top 10 for LLM applications. List position is not an incident rate.

OWASP LLM Top 10, 2025

How to read these findings

IBM's 13% figure describes AI-model or application breaches within a sample of organisations that had already experienced a breach. The 97% access-control finding applies only to that AI-breach subset. Neither figure estimates AI-breach prevalence across all enterprises.

The US$670,000 shadow AI cost difference is an observed association, not a predicted saving from a policy or product. OWASP's LLM01 placement identifies an application risk priority, not the frequency of employee AI incidents or a control Aona claims to provide.

Methodology and primary sources

The 2025 Cost of a Data Breach study was conducted by Ponemon Institute, sponsored and analysed by IBM. It examined breaches at 600 organisations globally from March 2024 to February 2025. OWASP's 2025 Top 10 is a risk list, not an incident survey. This page reports selected publisher findings and no new Aona measurement.

Sources reviewed 26 September 2026.

FAQ

Questions about these statistics

How common were AI-model or application breaches in IBM's study?
IBM reported 13% among 600 organisations that had already experienced a data breach between March 2024 and February 2025. This is not an estimate for all enterprises.
What did IBM report about shadow AI breaches?
One in five organisations in IBM's already-breached sample reported a breach due to shadow AI. Organisations with high shadow AI use had US$670,000 higher average breach costs than those with low or no use. The cost difference is an association, not a predicted saving.
Is US$4.44 million the average cost of an AI breach?
No. IBM's US$4.44 million figure is the 2025 global average across all breach types in its study, not an AI-specific or 2026 average.
Does OWASP say prompt injection is the most common AI incident?
No. OWASP lists prompt injection as LLM01 in its 2025 Top 10 for LLM applications. That is a risk-list position, not a measured incident frequency.
How can Aona help a team assess employee AI exposure?
Aona helps security teams review AI use on managed browser or native endpoint paths, apply configured policies, and inspect sensitive prompts or files where supported. Confirm the intended AI tool, client and action in the coverage guide, then test the policy response in a focused demo.
Review your employee AI exposure

Test the AI use your team needs to secure

Bring one employee AI tool and action. See the observed activity, configured policy response and sensitive-data protection on a supported path, then agree what needs validation in your environment.