Join our Newsletter — 33% off our NHI Course

What would it take for state sprawl to stay governable in AI?

 

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

TL;DR: Enterprise AI governance now reaches into AI-built code, agent permissions, embedded services and model-data controls as adoption grows, according to Pluto Security. Governance has to account for delegated access and shifting behavior across identities, runtime activity and policy paths.

Editorial analysis by NHI Mgmt Group, based on content published by Pluto Security: “Enterprise AI Security”.

By the numbers:

  • Pluto Security is out of stealth with $42 million in total funding.

Key questions

Q: Why do AI model changes create governance risk even when approvals are still current?

A: Because approval often attaches to a declared model, not to the live service that users actually hit.

Q: What are the signs that shadow AI agents are escaping discovery controls?

A: Common signs include identity traces without formal registration, endpoint-level activity from local agents or MCP servers, and broad permissions with no clear owner.

Q: How should security teams govern AI-enabled workflows that can act on their own?

A: Treat them as identity-governed execution paths, not just software features.

Practitioner guidance

  • Build a central AI asset inventory Catalog AI-built applications, agents, model integrations, prompt repositories, and embedding stores so governance starts from known assets, not assumptions.
  • Separate agent identities from human identities Assign dedicated service identities to each agent, scope their tokens tightly, and prevent inheritance of broad user credentials.
  • Insert mandatory review gates for AI-generated code Require security review for generated logic, dependency scanning for generated artefacts, and secure baselines before deployment.

Bottom line: Enterprise AI governance now reaches beyond model review into code, prompts, agents, and embedded services.

Glossary terms: Enterprise AI security, Shadow AI, AI Agent Identity, State Sprawl

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
 

Enterprise AI security is becoming an identity governance problem before it becomes an AI governance problem. Once agents can call systems, trigger workflows, and act on behalf of users, the core question is who or what is authorized to do the work. That shifts the centre of gravity from model quality to identity, privilege, and accountability. Practitioners should treat AI systems as governed actors, not just analytical tools.

A few things that frame the scale:

A question worth separating out:

Q: How can organisations balance AI productivity with identity security?

A: Organisations can balance AI productivity with identity security by making secure access the easiest path, not the exception path. That means using governed access workflows, limiting credential visibility, and designing controls that work at machine speed. If the process is too manual, users bypass it; if it is too open, secrets proliferate.

👉 Read our full editorial: AI governance now has to track agents, code and hidden access


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.