Topic starter
09/07/2026 12:34 pm
TL;DR: AI security strategy is moving toward purpose-based access, retrieval-aware classification, and runtime observability across prompts, retrievals, tool calls, and outputs, according to Knostic. The governance gap is no longer just who can access data, but what an AI system can use, combine, and reveal at runtime.
Editorial analysis by NHI Mgmt Group, based on content published by Knostic: “Building an AI Data Security Strategy From Scratch”.
Key questions
Q: How should security teams implement purpose-based access for AI systems?
A: Start with the highest-risk assistant or search workflow, then define who can use which data for what purpose.
Q: Why do AI assistants need retrieval-aware data classification?
A: Because the main risk is not just whether data is stored securely, but whether it can be retrieved and recombined into an output that exceeds the user’s intended purpose.
Q: What are the signs that AI security controls are not working in government agencies?
A: Warning signs include limited visibility into who can access sensitive data, weak or inconsistent monitoring, and delayed response to suspicious activity.
Practitioner guidance
- Define purpose-bound access rules Map high-value AI use cases to personas and business objectives, then enforce who can use which data for what purpose at prompt and retrieval time.
- Standardise retrieval-aware classification Apply consistent labels for PII, PHI, secrets, and provenance across data lakes, search indexes, and vector stores so the AI layer can enforce source-specific handling.
- Instrument end-to-end AI tracing Log prompts, retrieved sources, policy decisions, tool calls, and outputs together so investigators can reconstruct oversharing and policy bypass paths.
Bottom line: AI security strategy is shifting from coarse role assignment to purpose-bound control at the point where prompts, retrievals, tool calls, and outputs actually happen.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
09/07/2026 12:39 pm
Purpose-based control is the right abstraction for enterprise AI governance. Role-centric entitlement models were built for static access requests, not for systems that infer answers across multiple sources in a single interaction. Once the control point moves to prompt, retrieval, tool call, and output, the governing question becomes why the data is being used, not only who can see it. That is the correct mental model for AI security programmes.
A few things that frame the scale:
- Business leaders plan to spend $124 million on average on AI in 2026, and 91% say data security and risk will shape their AI strategy.
A question worth separating out:
Q: When should organisations prioritise an AI gateway over better observability?
A: They should prioritise the gateway whenever model calls involve internal data, regulated workflows, agents, or external tools. Observability is valuable, but it cannot replace request authorization, least privilege, or runtime policy enforcement. If a system can act, spend, or reach tools, the preventive control has to sit in front of the call.
👉 Read our full editorial: AI security strategy is shifting from roles to purpose-based controls