Notifications
Clear all
Topic starter
25/08/2026 9:13 am
TL;DR: Most enterprises are deploying AI agents faster than their governance can keep up, and C1.ai maps SACR’s ARMCF across GOVERN, IDENTIFY, PROTECT, DETECT, RESPOND, and RECOVER to show why agentic systems must be governed as privileged digital actors, not static applications. The real lesson is that identity becomes the control plane for ownership, inventory, tool access, telemetry, revocation, and re-validation.
NHIMG editorial — based on content published by C1.ai: Six Domains, One Control Plane: Mapping C1 to SACR's ARMCF
By the numbers:
- NHIs outnumber human identities by 25x to 50x in modern enterprises.
Questions worth separating out
Q: How should security teams govern AI agents that can access enterprise systems?
A: Security teams should govern AI agents as non-human identities with explicit ownership, scoped privileges, and continuous monitoring.
Q: What breaks when AI systems are governed like static applications?
A: Lifecycle drift breaks the model.
Q: Why do agentic AI systems complicate existing IAM and PAM controls?
A: They complicate them because IAM and PAM were built around stable identities, human-paced approvals, and entitlements that are reviewed after use.
Practitioner guidance
- Define a named owner for every production AI agent Assign accountability, approval rights, and risk acceptance to one business and one technical owner for each agent before go-live.
- Build a live registry of sanctioned and shadow AI Track owner, autonomy level, data sensitivity, and blast radius so unregistered agents and unknown tool paths become visible quickly.
- Broker tool access through a single identity control plane Move API, file, and email permissions behind a policy engine with allowlists, runtime secrets injection, and revocation hooks.
What's in the full article
C1.ai's full blog covers the operational detail this post intentionally leaves for the source:
- Control-by-control mapping from ARMCF GOVERN through RECOVER to C1 capabilities.
- How the policy engine, AI Access Management, and Agentic Vault are positioned across the six domains.
- Examples of identity telemetry, anomaly tracking, and kill-switch style response workflows.
- The article's own framing of why the ARMCF model is meant to be operationalised across human and non-human identities.
👉 Read C1.ai's mapping of ARMCF to agentic identity governance →
AI agent governance across six domains: what are teams missing?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
25/08/2026 9:14 am
AI agent governance fails when teams treat privileged digital actors like static software. ARMCF is useful because it exposes a category error that many IAM programmes still make. An agent that can send email, modify files, or call APIs is not governed by deployment hygiene alone. The practitioner conclusion is that runtime authority, not installation status, is the real unit of control.
A few things that frame the scale:
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation, according to AI Agents: The New Attack Surface.
- In the same study, 80% of organisations report their AI agents have already performed actions beyond their intended scope, including unauthorised systems access, sensitive data sharing, and credential exposure.
A question worth separating out:
Q: Why do autonomous agents make traditional access reviews less effective?
A: Access reviews assume permissions persist long enough to be observed, challenged, and recertified. Autonomous agents can obtain, use, and discard access within a single session, which means the risky action may occur before the next review cycle. That makes runtime enforcement more important than periodic certification alone.
👉 Read our full editorial: Agentic AI governance needs one control plane across six domains
