Topic starter
24/06/2026 6:56 pm
TL;DR: Palo Alto Networks says its acquisition of Portkey folds an AI gateway into Prisma AIRS to centralise governance for autonomous AI agents and related access decisions, according to Protect AI research. The deeper issue is that agentic systems force identity control to shift from static policy to runtime authorisation, where assumptions about stable intent and reviewable access no longer hold.
Editorial analysis by NHI Mgmt Group, based on content published by Protect AI: “Network Security”.
Key questions
Q: How should security teams govern AI agents that can choose tools at runtime?
A: Security teams should govern runtime agent choice as an access event, not as a simple application action.
Q: Why do autonomous AI agents change the authorization model?
A: Autonomous agents can alter their tool use, scope and sequencing after access has been granted, so the original authorization decision may no longer match the action being taken.
Q: What breaks when AI agents are governed like ordinary service principals?
A: The main failure is that ordinary service-principal governance assumes a stable workload with predictable lifecycle and entitlement patterns.
Practitioner guidance
- Define agent authority boundaries Map each AI agent to the minimum tools, data sources, and actions it can use, then separate read, write, and execution permissions so scope changes are visible and reviewable.
- Centralise runtime enforcement at the gateway Use an AI gateway or equivalent control point to mediate requests, record decisions, and keep policy enforcement separate from application logic.
- Instrument agent activity for auditability Capture prompt, tool-call, and downstream action evidence in a form that supports reconstruction of delegated access and incident review.
Bottom line: AI agent governance is maturing into a delegated identity problem, where tool use, runtime context, and revocation matter more than static role assignment.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 3:58 am
AI agent governance is becoming delegated identity governance, not a model-management problem. Once an agent can choose tools and execute tasks, the security question becomes who granted that authority, how it is constrained, and how it is revoked. That shifts the centre of gravity from prompt safety to control over runtime privileges. Practitioners should treat agent governance as an identity lifecycle issue with audit and revocation requirements.
A few things that frame the scale:
- 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.
- 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: What should teams evaluate before adopting a unified AI gateway?
A: Teams should evaluate where identity authority, policy enforcement, and audit logging actually sit, and whether those functions are preserved outside the application layer. A gateway only helps if it becomes the enforceable choke point for delegated access. Without that, the organisation gains another integration layer but not stronger governance.
👉 Read our full editorial: Palo Alto Networks acquires Portkey for AI agent governance