Notifications
Clear all
Topic starter
12/06/2026 9:46 pm
TL;DR: AI data leakage now happens through prompts, memorization, third-party AI providers, and overpermissioned agents, with shadow AI adding $670,000 in breach costs on average according to IBM’s 2025 Cost of a Data Breach Report. The central problem is that conventional IAM assumes access is stable enough to review, but autonomous and semi-autonomous AI systems can access, reuse, and expose data within a single workflow.
NHIMG editorial — based on content published by Aembit: AI data leakage, agent identity, and access controls
Questions worth separating out
Q: How should security teams prevent AI data leakage in production environments?
A: Start by treating every AI prompt, tool call, and agent action as a governed data flow.
Q: Why do AI agents create more leakage risk than standard automation?
A: AI agents can decide which data to request, when to call tools, and how much information to return, so their behaviour can expand inside a session.
Q: What breaks when employees use unsanctioned AI tools with company data?
A: Security teams lose visibility into where the data went, who processed it, and whether the provider retained it.
Practitioner guidance
- Inventory every AI tool and agent path Map sanctioned and shadow AI usage, including prompt tools, coding assistants, MCP-connected agents, and any workflow that can reach internal data.
- Remove standing secrets from agent workflows Replace static API keys and passwords with short-lived credentials that expire after the task completes.
- Scope agent access to the minimum data slice Give agents only the records, systems, and actions needed for one task, not full database or tenant-level access.
What's in the full article
Aembit's full article covers the operational detail this post intentionally leaves for the source:
- A step-by-step breakdown of leakage vectors across prompts, training pipelines, logs, and agent tool calls.
- Specific controls for secretless just-in-time access and per-agent policy enforcement in real environments.
- Practical guidance for monitoring agent behaviour and building audit trails that support incident response.
- Examples of how blended human and agent identity changes access decisions in production workflows.
👉 Read Aembit's analysis of AI data leakage, agents, and access controls →
AI data leakage and agent identity: where current controls fail?
Explore further
13/06/2026 12:05 am
AI data leakage is now an identity problem, not just a content problem. The article shows that the highest-risk exposures come from systems that can access, retain, and re-emit data under machine speed. That shifts control priority from user warnings to governed access paths, because the leakage vector is often a non-human identity acting inside an approved workflow. Practitioners should treat AI tool access as an identity and entitlement issue first.
A few things that frame the scale:
- 1 in 4 organisations are already investing in dedicated NHI security capabilities, with an additional 60% planning to do so within the next twelve months, according to The State of Non-Human Identity Security.
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation, according to AI Agents: The New Attack Surface.
A question worth separating out:
Q: Who is accountable when an AI agent exposes sensitive data?
A: Accountability should follow the identity chain, not just the model vendor. The business owner of the agent, the team that granted access, and the operator who approved the workflow all share responsibility for the exposure path and the control failure.
👉 Read our full editorial: AI data leakage exposes why identity controls must shift to agents
