Join our Newsletter — 33% off our NHI Course

Could April 2026 SR 11-7 shift runtime governance for GenAI?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20217
Topic starter  

TL;DR: GenAI governance now depends on runtime evidence rather than assuming model risk management can absorb agentic systems by extension, Tetrate explains. Runtime controls have to prove inventory, attribution, guardrails and supervision at the point of action, or the programme stays documentary instead of operational.

Editorial analysis by NHI Mgmt Group, based on content published by Tetrate: “SR 11-7 Just Wrote Itself Out of the GenAI Conversation”.

Key questions

Q: Why do AI agents need runtime controls instead of only pre-approved access?

A: Pre-approved access cannot tell you what the agent will do once prompts, tools, memory, and sub-agents start interacting.

Q: How do organisations know whether AI governance is actually working?

A: AI governance is working when teams can prove that data access, identity permissions, and runtime controls line up with policy in practice.

Q: What should security teams do first when GenAI is outside traditional model risk management scope?

A: Start by routing all model and agent traffic through a governed control point that can log, filter and block requests.

Practitioner guidance

  • Implement request-path model governance Force every GenAI and agentic AI request through a controlled gateway that can log, filter and block before the response or tool action occurs.
  • Build an accurate-by-construction inventory Capture model, agent and tool usage automatically from the execution path so the register reflects reality instead of manual updates.
  • Add request-level attribution Record business unit, application and agent context for each model call so examiners can trace usage back to accountable owners.

Bottom line: GenAI governance now depends on runtime evidence, not on assuming model risk management can carry agentic systems by extension.

Glossary terms: Runtime Governance, Request-path control, Usage Attribution, Inventory Accuracy By Construction

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20707
 

SR 11-7 no longer provides a defensible governance wrapper for GenAI. The article is right to treat the rewrite as a scope reset rather than a mere wording update. That matters because many programmes had been using model risk management as the default container for generative and agentic AI. Once that peg is removed, control ownership has to move to the operational layers that actually shape behaviour, including access, telemetry and tool governance.

A few things that frame the scale:

  • Generative AI use specifically increased from 33% in 2023 to 79% in 2025, according to McKinsey’s Global Surveys on the State of AI.

A question worth separating out:

Q: Should banks treat agentic AI as the same risk category as older quantitative models?

A: No. Traditional model risk management fits stable analytical models, but agentic systems combine prompts, retrieval, tools and dynamic execution. That makes them a governance and access problem as much as a modelling problem. Banks need controls that manage runtime authority, data access and supervisory evidence, not only validation of the underlying model.

👉 Read our full editorial: SR 11-7 carve-out shifts GenAI governance to runtime controls


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.