Notifications
Clear all
Topic starter
02/08/2026 11:23 am
TL;DR: AI inference risk occurs when AI systems combine individually harmless inputs into sensitive outputs that traditional file-centric DLP cannot detect, according to Cyberhaven's analysis of AI data exposure. The control gap is no longer classification at rest or in transit, but governance over recombination, lineage, and derivative outputs that AI creates from context.
NHIMG editorial — based on content published by Cyberhaven: AI Inference Risk: The Data Exposure Your DLP Can't See
By the numbers:
- 39.7% of all human interactions with AI tools involve sensitive data.
- 78% of organizations now use AI in at least one business function, up from 55% the year prior.
- 48% of cybersecurity professionals rank agentic AI as the leading attack vector.
Questions worth separating out
Q: What breaks when AI systems recombine harmless inputs into sensitive outputs?
A: What breaks is the assumption that sensitivity is visible at the file or prompt level.
Q: Why do AI tools complicate traditional data loss prevention?
A: They complicate DLP because the sensitive event often happens inside the model, not at the boundary.
Q: How do security teams know if AI inference risk is actually being controlled?
A: They know it is controlled when they can trace source data into AI sessions, identify which identities and workflows can supply sensitive context, and show that outputs are classified and reviewed where needed.
Practitioner guidance
- Instrument AI data flows for lineage Track what enters AI tools, how it is combined across prompts and sessions, and what leaves as a derivative output.
- Scope access to AI inputs by identity and purpose Limit which users and systems can feed sensitive context into generative tools, and separate casual experimentation from approved business workflows.
- Govern shadow AI through access policy and discovery Discover unsanctioned AI usage, then apply policy controls at the identity and endpoint layer so unmanaged tools cannot receive regulated or confidential content.
What's in the full article
Cyberhaven's full blog covers the operational detail this post intentionally leaves for the source:
- How Cyberhaven distinguishes AI prompt submission from normal data processing in enterprise workflows.
- The specific data lineage and enforcement mechanics used to trace AI inputs into derivative outputs.
- Operational examples of how sensitive context can recombine across sessions without triggering file-based DLP.
- The control architecture Cyberhaven describes for blocking confidential information before it reaches external models.
👉 Read Cyberhaven's analysis of AI inference risk and DLP blind spots →
AI inference risk and the governance gap DLP misses?
Explore further
02/08/2026 12:41 pm
Inference risk is a control-plane failure, not a classification failure. The article shows why sensitive exposure can occur even when labels, policy rules, and file scanning are all functioning as designed. That shifts the problem from content inspection to governance of how AI systems recombine context. For practitioners, the lesson is that DLP alone cannot be the last line of defence.
A question worth separating out:
Q: What should organisations do when employees use shadow AI with sensitive context?
A: They should treat it as an access and governance problem, not just a policy violation. That means discovering unsanctioned tools, limiting the identities that can submit sensitive material, and controlling the endpoints and browsers where those tools are used. The objective is to reduce invisible recombination, not simply to forbid AI use.
👉 Read our full editorial: AI inference risk exposes data DLP cannot see
