TL;DR: AI-related incidents hit a record 233 in 2024 and average breach costs reached $4.88 million, according to Mindgard. Security teams now need inventory, ownership, adversarial testing, and scoped delegation to keep AI systems governable as they scale.
Editorial analysis by NHI Mgmt Group, based on content published by Mindgard: “AI Security Statistics & Benchmarks: The Numbers Behind the AI Security Crisis”.
By the numbers:
- Enterprise AI use rose from 55% of organisations in 2023 to 78% in 2024, according to the Stanford HAI AI Index Report 2025 cited by Mindgard.
- AI-related security incidents reached a record 233 in 2024, according to the Stanford HAI AI Index Report 2025 cited by Mindgard.
- The average cost of an AI-driven breach reached $4.88 million, according to Harvard Business Review research cited by Mindgard.
Key questions
Q: Why do AI-assisted attacks increase application risk so quickly?
A: AI-assisted tooling reduces the effort required to find exposed endpoints, vary payloads, and test credentials at scale.
Q: What are the signs that an AI security programme is failing against autonomous threats?
A: A programme is failing when assurance depends on quarterly assessments, when new tools or prompts appear without retesting, and when findings are only measured as patch backlog.
Q: How should organisations govern AI systems that can make consequential decisions?
A: Organisations should govern consequential AI systems with the same discipline used for high-risk identities: defined ownership, least privilege, logging, approval boundaries, and human override.
Practitioner guidance
- Map every AI system and agent to an owner Build an inventory of models, agents, copilots, and embedded AI features across business units, then assign accountable owners for data access, tool use, and lifecycle decisions.
- Test AI workflows with adversarial scenarios Run red-team scenarios for prompt injection, data leakage, fake account abuse, and unsafe tool invocation before production rollout and after major workflow changes.
- Constrain AI delegation and tool scope Limit what each model or agent can call, read, write, or trigger, and review those boundaries as part of change control when the workflow expands.
Bottom line: The central risk is not AI adoption itself, but the gap between rapid deployment and the controls needed to govern access, data use, and delegated actions.
Glossary terms: Shadow AI, Agentic AI, AI governance debt, AI Red Teaming
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
AI governance debt is now an operational security problem: organisations are accumulating AI capability faster than they are building the controls needed to govern it. That means risk decisions are being deferred into production, where access, data handling, and delegation are already live. The consequence is that the first real governance test often arrives as an incident, not as a design review.
A few things that frame the scale:
- Organisations that describe themselves as confident in their AI deployment actually experience a 72% security incident rate, compared to 33% for those who remain cautious, according to the 2026 Infrastructure Identity Survey.
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What should teams do when an AI system is connected to business workflows?
A: Treat the connection as a governance decision, not a feature toggle. Define what the AI can access, what actions it may trigger, which approvals remain mandatory, and how you will detect misuse. If the workflow touches sensitive data or customer-facing processes, require risk review before expansion.
👉 Read our full editorial: Governance gaps are the main barrier to safer enterprise AI