Topic starter
14/09/2026 10:10 am
TL;DR: AI data classification inspects prompts, uploads, responses, retrieved context, and agent tool calls in flight so organisations can stop sensitive information reaching external models, according to WitnessAI. That matters because effective AI governance now depends on context-aware controls, audit evidence, and enforceable policies rather than keyword filters that miss meaning and generate noise.
Editorial analysis by NHI Mgmt Group, based on content published by WitnessAI: “AI data classification: how it works”.
By the numbers:
- DLP accuracy research for unstructured content ranges from 5 to 25%, with false positive rates above 40%.
- Gartner says 17% of organisations have deployed AI agents, and 60% expect to within two years.
Key questions
Q: How should organisations classify sensitive data in AI prompts and outputs?
A: Organisations should classify AI traffic at runtime, before prompts or files reach external models, and apply policy based on the data category and the interaction’s intent.
Q: Why do keyword and regex controls fail for conversational AI?
A: They fail because conversational AI often carries sensitive meaning in plain language rather than in fixed patterns.
Q: What are the signs that AI classification is too weak for production use?
A: Common signs include high false positives, routine work being blocked or routed incorrectly, and sensitive prompts still reaching external models without a control decision.
Practitioner guidance
- Define AI-specific data classes Create categories for prompts, retrieved context, outputs, source code, regulated data, and agent tool calls so policy can target the actual AI interaction surface.
- Enforce pre-execution policy checks Require classification before external model submission, then use allow, warn, block, route, or tokenize responses based on the data class and interaction intent.
- Extend monitoring to agent and MCP paths Discover AI agents and MCP connections at the network layer, then attribute tool activity to a human identity and log governed calls end to end.
Bottom line: AI data classification closes a governance gap that appears when prompts, outputs, retrieved context, and tool calls move faster than static data controls can inspect them.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/09/2026 10:11 am
AI data classification is becoming the missing control plane for AI governance. Keyword filters and static DLP controls were designed for files and forms, not for conversational workflows where meaning emerges in context. The governance problem is no longer whether data is stored securely, but whether it is recognised fast enough while it is moving through prompts, outputs, and tool calls. Practitioners should treat runtime classification as part of AI policy enforcement, not as a reporting add-on.
A few things that frame the scale:
- Internal repositories are 6x more likely to contain secrets than public ones (32.2% vs 5.6%), contradicting the assumption that private repos are safe, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: How should teams govern AI agents that use MCP?
A: Treat each connected agent as a non-human identity with an owner, a scope, and a review cycle. The practical control set is familiar: least privilege, secret rotation, access expiration, and auditability across the systems the agent can reach.
👉 Read our full editorial: AI data classification is closing the governance gap in model use