Topic starter
23/06/2026 9:07 pm
TL;DR: AI TRiSM has shifted from a Gartner framework to an operating requirement as enterprises expand AI use, regulators codify obligations, and attackers target GenAI platforms, according to WitnessAI, McKinsey, Gartner, CrowdStrike, and the EU AI Act. Legacy controls cannot reliably interpret conversational data exposure, so governance now needs intent-aware enforcement, audit trails, and accountable ownership.
Editorial analysis by NHI Mgmt Group, based on content published by WitnessAI: “AI TRiSM in 2026: A practical guide for security leaders”.
By the numbers:
- 88% of enterprises now use AI in at least one business function, according to McKinsey’s 2025 State of AI survey.
- 69% of organizations suspect or have evidence that employees are using prohibited public GenAI tools.
- CrowdStrike’s 2026 Threat Report found attackers injecting malicious prompts into legitimate enterprise GenAI platforms to steal credentials across at least 90 organizations.
Key questions
Q: How should organisations enforce AI TRiSM for agentic AI systems?
A: Start with runtime controls, not policy documents.
Q: Why do traditional DLP and CASB tools fall short for AI governance?
A: They were built around predictable data patterns and network flows, while AI interactions are conversational, contextual, and often initiated inside desktop apps or browser sessions.
Q: What breaks when AI agents are not governed at runtime?
A: Without runtime governance, an agent can shift behaviour after provisioning and still execute actions that were never reviewed in context.
Practitioner guidance
- Establish a single accountable AI owner Name one executive owner for AI governance and give that role authority across security, legal, compliance, HR, and business functions.
- Inventory sanctioned and shadow AI use Map where employees, applications, and agents are already interacting with AI, including native apps, browser-based tools, IDEs, and agent connections.
- Move controls to intent-based enforcement Use controls that classify the purpose of an interaction, not just the data pattern inside it.
Bottom line: AI TRiSM is no longer a theoretical framework for future planning. It is becoming the operating model that links AI adoption, enforcement, and regulatory accountability in one programme.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 2:14 am
AI TRiSM is becoming the operating model because AI risk is now behavioural, not just technical. The article shows that enterprise AI governance cannot rely on perimeter controls or static policy alone when the system being governed is conversational, contextual, and increasingly autonomous. That is a category shift for the field, not a tooling tweak. The practitioner conclusion is that AI oversight has to move into runtime decisioning and accountable ownership.
A few things that frame the scale:
- Organisations that rely heavily on static credentials reported a 20-percentage-point increase in security incidents compared with those with low reliance, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should security teams report AI risk to the board?
A: Security teams should report AI risk in terms directors can govern: ownership, data exposure, decision rights, approval boundaries, and incident impact. A useful board report shows who can authorise AI actions, what sensitive data was involved, how policy matches real usage, and how quickly the organisation can detect and contain an AI-related issue.
👉 Read our full editorial: AI TRiSM is becoming the operating model for enterprise AI governance