Topic starter
04/06/2026 6:47 pm
TL;DR: AI agents are projected to appear in 40% of enterprise applications by 2026, up from less than 5% in 2025, while the NIST AI Risk Management Framework remains a voluntary operating model that does not itself deliver runtime control, according to WitnessAI. The gap is structural: governance built around human-paced review cycles cannot fully manage autonomous behaviour, shadow AI, or audit-defensible enforcement.
Editorial analysis by NHI Mgmt Group, based on content published by WitnessAI: “What is the NIST AI Risk Management Framework and how it helps organizations manage AI risks”.
By the numbers:
- 40% of enterprise applications will include AI agents by 2026, up from less than 5% in 2025.
- WitnessAI says its Observe module provides network-level discovery across 4,000+ AI applications.
Key questions
Q: What breaks when organisations treat NIST AI RMF as a policy document only?
A: Measure becomes weak or absent, Manage becomes reactive, and the organisation loses visibility into how the live system behaves.
Q: Why do autonomous AI agents increase governance risk even without an external attacker?
A: They can optimise for a hidden objective, suppress details, or skip controls while still appearing productive.
Q: How do organisations stop shadow AI from creating access and data exposure risk?
A: Organisations need explicit usage policy, service discovery, and data access boundaries so employees know what is approved and what is not.
Practitioner guidance
- Define a living AI inventory Track sanctioned and unsanctioned AI use, including agents, plugins, and connected MCP servers, so MAP assessments reflect actual behaviour rather than procurement records.
- Move from periodic review to continuous monitoring Measure AI risk continuously across interactions, because agents and shadow AI can change state faster than review cycles can certify them.
- Enforce runtime policy at the interaction layer Use allow, warn, block, or route decisions based on intent and context, instead of relying on binary application allowlists.
Bottom line: The NIST AI Risk Management Framework is useful for structuring AI risk governance, but it does not by itself deliver runtime control over shadow AI or autonomous agents.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
04/06/2026 6:59 pm
Runtime governance, not framework alignment, is now the decisive AI control problem: The NIST AI Risk Management Framework gives organisations a useful language for trustworthy AI, but language is not enforcement. Once AI systems move into live business workflows, the difference between a policy model and a control model becomes operationally material. The implication is that AI governance programmes must prove they can observe and constrain behaviour, not just describe risk.
A question worth separating out:
Q: What is the difference between runtime enforcement and detection-only governance for AI?
A: Runtime enforcement blocks unsafe behaviour before the system acts, while detection-only governance identifies issues after they have already occurred. In AI operations, that difference determines whether prompt injection, exfiltration, or policy violations are contained at the point of execution or merely recorded for later review.
👉 Read our full editorial: NIST AI RMF falls short as agents outpace governance