Join our Newsletter — 33% off our NHI Course

Are assessment-only governance and red teaming enough for agents?

 

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

TL;DR: Assessment-only governance and red teaming show risk at a point in time, but Singul AI says they do not stop agents from acting outside policy in production. Live workflows need controls that can enforce boundaries and prove they held.

Editorial analysis by NHI Mgmt Group, based on content published by Singul AI: “AI Risk Assessment and Red Teaming vs Runtime AI Control: A Score Is Not a Control”.

Key questions

Q: Why do AI agents need runtime control instead of a risk score alone?

A: AI agents act across tools and services, so the key risk is what they can do at the moment of execution.

Q: How do security teams know if AI governance is working?

A: Look for evidence that access decisions are reviewable, permissions are revocable, and exceptions are not becoming permanent.

Q: What breaks when AI red teaming is not part of GenAI governance?

A: Without AI red teaming, organisations usually discover failures only after a model has already exposed data, bypassed a guardrail, or triggered an unsafe API call.

Practitioner guidance

  • Separate assessment from enforcement in your governance model Use risk assessments and red teaming as inputs, but require a distinct runtime layer that can block, allow, or constrain live agent actions.
  • Define agent permissions as task-scoped policy Set access by action, data class, tool, and context so an agent can only do what the current workflow requires.
  • Instrument continuous proof of control effectiveness Capture logs, decisions, and policy outcomes that show the control held after deployment and across changing workflows.

Bottom line: AI risk assessment and red teaming are useful, but they do not stop an agent from acting outside policy in production.

Glossary terms: Assessment-Only Governance, Runtime AI usage control, Agentic AI Identity, Continuous Proof

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
 

Assessment is now the weakest form of AI governance when an agent can act between review cycles. A score can be accurate and still be operationally irrelevant if the system can continue to use tools, reach data, or chain actions after the assessment has been filed. In agentic environments, governance must move from documentation to enforcement or it will lag the actual control plane. Practitioners should stop treating posture reports as evidence of runtime containment.

A few things that frame the scale:

  • Claude Code-assisted commits leaked secrets at a rate of 3.2%, more than double the human-only baseline of 1.5%, with peaks reaching 31 secrets per 1,000 commits in August 2025, according to the State of Secrets Sprawl 2026.
  • 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.

A question worth separating out:

Q: When should organisations treat AI agent authorisation as an identity problem?

A: When the system can invoke tools, move across services, or act with delegated authority, authorisation becomes an identity issue as much as a model-risk issue. At that point, the organisation must govern who or what the agent is, what it can do, and how that authority is revoked or narrowed.

👉 Read our full editorial: Runtime AI control outgrows assessment-only governance for agents


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.