Topic starter
12/06/2026 9:23 pm
TL;DR: C1.ai says NIST IR 8596, the Cyber AI Profile, treats AI security as a problem of inventories, ownership, permissions, and continuous risk review because AI systems are now embedded in business and security workflows. Identity governance becomes the control plane when AI systems start acting, not just advising.
Editorial analysis by NHI Mgmt Group, based on content published by C1.ai: “NIST’s New Cyber AI Profile Signals a Shift: AI Security Starts With Identity”.
Key questions
Q: How should security teams govern AI systems that can act without human approval?
A: Security teams should govern autonomous AI the same way they govern other high-risk identities, but with runtime enforcement instead of periodic review.
Q: Why do periodic access reviews struggle in AI-heavy environments?
A: Because risk changes faster than the review cycle.
Q: What breaks when AI agents are given broad inherited permissions?
A: Broad inherited permissions break the assumption that access is tied to a narrow business need.
Practitioner guidance
- Map AI systems to accountable identities Assign each model, agent, API integration, and automation path an owner, an approved permission scope, and a revocation path before production use.
- Separate advisory AI from acting AI Classify where AI only recommends versus where it can execute actions, then require stronger controls and human approval wherever execution is possible.
- Apply least privilege dynamically Replace broad standing access with task-scoped permissions that expire when the AI action, workflow, or business context ends.
Bottom line: AI security is moving into identity territory because the main control question is now who or what can act inside enterprise workflows.
What's in the full article
C1.ai's full blog post covers the operational detail this post intentionally leaves for the source:
- How NIST IR 8596 maps AI security into CSF 2.0 and the AI RMF
- The article’s full breakdown of inventories, ownership, permissions, and continuous risk review
- Practical guidance on applying human-in-the-loop approvals to AI-assisted actions
- The broader framing of AI as a control-plane issue for identity and security teams
👉 Read C1.ai's analysis of NIST's Cyber AI Profile and identity-led AI security →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 5 days ago by NHI Mgmt Group
12/06/2026 11:25 pm
AI security has become an identity governance problem before it becomes a model governance problem. The Cyber AI Profile repeatedly returns to ownership, permissions, and revocation because those are the controls that determine whether AI can act safely inside enterprise workflows. Security teams that treat AI as a standalone model risk missing the real control plane. The practitioner conclusion is simple: if identity is not defined for the system, AI security is not operational.
A few things that frame the scale:
- Only 23% of IT leaders were very confident in their organisation's ability to manage security and governance for GenAI deployments, according to a 2025 Gartner survey of 360 IT leaders.
A question worth separating out:
Q: What does Zero Trust mean for AI agent identity governance?
A: For AI agents, Zero Trust means every request is authenticated and authorised in context, with access granted only for the specific task and duration required. Long-lived trust, broad entitlements, and reusable tokens all undermine that model. Teams should use Zero Trust to reduce standing privilege and make agent access auditable and disposable.
👉 Read our full editorial: NIST’s Cyber AI Profile puts identity at the center of AI security
This post was modified 5 days ago by NHI Mgmt Group