Topic starter
06/11/2026 6:40 pm
TL;DR: PlainID’s analysis of the Conference of State Bank Supervisors’ AI Supervisory Framework finds that banks will be judged on whether AI controls operate inside live transactions, not just in policy documents. For practitioners, the burden shifts to proving authorization, filtering and audit evidence at the moment an agent acts.
Editorial analysis by NHI Mgmt Group, based on content published by PlainID: “The CSBS AI Supervisory Framework: Turning AI Governance Into Controls Examiners Can Test”.
Key questions
Q: What is the difference between AI governance and AI runtime security?
A: AI governance focuses on policies, documentation, approvals, fairness checks, and regulatory evidence.
Q: How should banks apply least privilege to AI agents?
A: Banks should treat AI agents as delegated identities with tightly scoped runtime permissions, not as broad application users.
Q: Why do MCP-based AI workflows need runtime authorization checks?
A: They need runtime checks because the right to call a tool can change as the session evolves, the task expands, or the risk of an action rises.
Practitioner guidance
- Map every AI use case to a live transaction path Inventory where AI requests data, invokes tools, calls APIs or produces output, then tie each step to the controlling policy and enforcement point.
- Separate policy intent from runtime decisioning Keep governance documents, approvals and risk tiering in one layer, but require the production control plane to enforce permit, deny, mask, constrain or step-up decisions in the workflow itself.
- Treat the identity chain as a single decision surface Evaluate the human requester, the acting agent, delegated authority, target resource and environmental context together so privilege does not inherit beyond the approved task.
Bottom line: The CSBS framework turns AI governance into a test of whether controls change live system behaviour, not just whether policy exists.
What's in the full article
PlainID's full blog post covers the operational detail this post intentionally leaves for the source:
- Step-by-step mapping of CSBS supervisory objectives to enforcement points in a live agentic workflow
- Concrete examples of policy versioning, immutable audit logs and step-up approval decisions
- Detailed breakdown of runtime controls for retrieval, tool selection, parameter limits and output filtering
- The vendor's walk-through of how a billing-dispute agent is controlled across seven execution steps
👉 Read PlainID's analysis of CSBS AI supervision and runtime authorization →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:42 pm
Runtime enforcement, not policy drafting, is now the differentiator. CSBS is effectively asking whether organisations can prove that AI controls changed live system behaviour, not just governance language. That is a material shift for banks because it moves AI oversight from advisory risk framing into operational control evidence. The practitioners who win here will be the ones who can show transaction-level decisions, not policy promises.
A few things that frame the scale:
- 52% of respondents see AI security decision-making power shifting toward platform and infrastructure teams rather than the executive suite, according to the 2026 Infrastructure Identity Survey.
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What evidence do auditors need for AI access decisions?
A: Auditors need a clear record of who approved each AI access decision, what policy or risk rule was applied, which identity or agent received access, and when it was granted or revoked. They also need logs showing authentication, entitlement changes, and any step-up approval or exception used. Evidence must tie the access decision to a human owner and an auditable control.
👉 Read our full editorial: CSBS turns runtime authorization into the test of AI governance