Notifications
Clear all
Topic starter
09/07/2026 12:34 pm
TL;DR: AI usage control governs prompts, retrieval, tool calls, and outputs in real time through policy decision points and enforcement points, while McKinsey says around 78% of organisations now use AI in at least one business function. The control gap is no longer access to AI, but purpose-aware governance of how AI is actually used.
NHIMG editorial — based on content published by Knostic: Fast Facts on AI Usage Control
By the numbers:
- Around 78% of organisations report using AI in at least one business function, up from 55% a year earlier.
- Only 18% of MCP server deployments implement any form of access scoping for tool permissions.
Questions worth separating out
Q: How should security teams implement AI usage control in enterprise AI workflows?
A: Start by identifying every AI touchpoint, including prompts, retrieval sources, tool calls, and outputs.
Q: Why does AI usage control matter more than access control for AI systems?
A: Access control only decides who can reach the system.
Q: What breaks when AI controls stop at the login boundary?
A: A login-only model misses the places where AI risk is created.
Practitioner guidance
- Map AI control points across the full interaction path Inventory where prompts originate, which retrieval sources are used, which tools can be called, and where outputs are consumed.
- Define machine-readable purpose and sensitivity rules Translate acceptable-use policy into context fields that a PDP can evaluate, including persona, data class, device trust, location, and jurisdiction.
- Require audit logs that explain every AI decision Log the request context, policy rationale, enforcement action, and final outcome for each governed interaction.
What's in the full article
Knostic's full blog covers the operational detail this post intentionally leaves for the source:
- Step-by-step implementation of policy decision points and enforcement points across AI workflows.
- Concrete examples of prompt, retrieval, tool, and output controls with allow, deny, and obligation outcomes.
- Guidance on audit logging, policy feedback loops, and operational tuning for AI usage decisions.
- The source article's practical examples for mapping context attributes such as persona, device trust, and jurisdiction.
👉 Read Knostic's full guide on AI usage control and governance →
AI usage control for enterprise AI systems: what changes now?
Explore further
09/07/2026 12:39 pm
AI usage control exposes the real governance gap in enterprise AI: access control answers who may enter the system, but AI usage control answers what the system may do with data once it is inside the workflow. That distinction becomes decisive when prompts, retrieval, tools, and outputs each create separate leakage and misuse opportunities. For identity teams, this is the point where entitlement management stops being sufficient and policy enforcement becomes interaction-aware.
A few things that frame the scale:
- 53% of MCP servers expose credentials through hard-coded values in configuration files, according to The State of MCP Server Security 2025.
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, according to The State of MCP Server Security 2025.
A question worth separating out:
Q: How do organisations prove that AI governance is actually working?
A: They need audit-ready logs that capture the request context, policy decision, enforcement action, and result for each interaction. Those records let teams show that controls were applied consistently, detect drift or workarounds, and refine policies based on real usage rather than assumptions.
👉 Read our full editorial: AI usage control reframes governance for prompts, tools, and outputs
