TL;DR: AI-related data leaks have already hit 68% of organisations, while only 23% have policies for employee AI use, according to Mindgard. Prompts, agents and APIs now demand tighter access governance than perimeter tools can provide.
Editorial analysis by NHI Mgmt Group, based on content published by Mindgard: “AI Data Security Trends: The New Rules for Protecting Sensitive Data”.
By the numbers:
- 68% of organisations have already faced data leaks related to employee use of AI tools, while only 23% have AI security policies that govern employee use.
- 39.7% of total interactions with AI tools include prompt text, copy-paste functions and file uploads that contain sensitive data.
- In 2025, the FBI IC3 received 22,364 AI-related complaints from victims that cost Americans almost $893 million.
Key questions
Q: Why do AI agents make excessive access more dangerous than human access?
A: AI agents can use inherited permissions continuously, across multiple systems, and at machine speed.
Q: What are the signs that traditional controls are failing to see shadow AI use in the enterprise?
A: A common sign is that AI activity appears in business outcomes but not in security logs.
Q: What breaks when AI data access is not centrally governed?
A: When access is fragmented, teams lose visibility into what data is feeding models, who can change it, and whether outputs can be trusted.
Practitioner guidance
- Map AI data paths and trust boundaries Document every place sensitive information can enter, transform, or leave an AI workflow, including prompts, file uploads, agents, plugins, and API calls.
- Scope AI entitlements to the task Remove standing access that is not required for the current use case, and separate read, write, retrieval, and external sharing permissions.
- Block shadow AI and unsanctioned connectors Detect unmanaged AI tools, browser extensions, and third-party integrations, then revoke or isolate anything that bypasses approved identity, logging, or data controls.
Bottom line: AI is expanding the data security problem into prompts, agents, APIs, model pipelines, and supply chains, which makes visibility and access governance the first control challenge.
Glossary terms: Shadow AI, Prompt-to-exfiltration drift, AI Data Privacy, Non-Human Identity (NHI)
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
AI data security has become an identity governance problem, not just a content filtering problem. Once an AI system can access files, APIs, or SaaS tools, its privilege profile becomes part of the organisation’s attack surface. The article is right to frame prompts, agents, and integrations as separate exposure layers, because each layer changes who or what can move data next. Practitioners should stop treating AI as a passive application and manage it as a governed actor with scoped authority.
A few things that frame the scale:
- 43% of security professionals are concerned about AI systems learning and reproducing sensitive information patterns from codebases, according to the State of Secrets in AppSec.
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: How do organisations balance AI data use with privacy and compliance requirements?
A: Organisations should tie AI data use to explicit governance. That means defining which datasets are allowed for AI, applying native data controls, reviewing third party risk where AI services are involved, and reassessing exposure as models or workflows change. The practical objective is to support innovation without expanding access to personal or regulated data beyond what is necessary.
👉 Read our full editorial: AI data security now fails at prompts, agents and APIs