Topic starter
30/03/2026 3:48 pm
TL;DR: The core issue is not whether AI can talk, but whether identity and access controls can safely govern autonomous execution, according to Palo Alto Networks, which says Prisma AIRS 3.0 adds discovery, risk assessment, and runtime protection across the agentic AI lifecycle, including agent inventory, architectural scanning, AI red teaming, and a control plane for authorization and observability.
Editorial analysis by NHI Mgmt Group, based on content published by Palo Alto Networks: “Palo Alto Networks Secures Agentic AI with Prisma AIRS 3.0”.
Key questions
Q: What breaks when AI systems are governed like static applications?
A: Lifecycle drift breaks the model.
Q: Why do autonomous MCP agents need NHI-style identity controls?
A: Autonomous MCP agents need NHI-style controls because they operate as their own principals once deployed.
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.
Practitioner guidance
- Define an agent inventory standard Catalog every agent, model connection, tool integration and execution location across cloud, SaaS and endpoint estates so unmanaged agentic identities do not sit outside governance scope.
- Separate design-time and runtime review Use architectural scanning and red teaming before deployment, then apply separate runtime authorization controls once the agent starts executing tasks independently.
- Bind agent authority to task scope Limit access to the minimum tool set and data paths needed for the current task, and revoke that authority as soon as the task completes or changes context.
Bottom line: Agentic AI changes the governance problem because systems that act independently need runtime authorization, not just monitoring and approval at setup.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 4 days ago by NHI Mgmt Group
08/10/2026 6:51 pm
Agentic identity governance is now a runtime problem, not an inventory problem. Palo Alto Networks is describing a class of systems that can act independently across discovery, assessment and execution. That shifts the control question from whether an AI exists to whether its authority is bounded while it runs. Practitioners should read this as a governance pivot: identity controls must follow the agent into runtime, not stop at provisioning.
A few things that frame the scale:
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, according to the 2026 Infrastructure Identity Survey.
- 53% of security leaders expect AI to run major portions of their infrastructure autonomously within the next three years, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How should security teams govern human, NHI, and agentic access in one programme?
A: Security teams should use one control plane for policy, logging, and lifecycle visibility, then apply actor-specific rules for authentication, credentials, and runtime behaviour. Humans, service accounts, and agentic systems should not share identical enforcement assumptions. The goal is consistent governance with differentiated controls, not separate identity programmes that drift apart.
👉 Read our full editorial: Prisma AIRS 3.0 puts agentic identity governance at the center