Notifications
Clear all
Topic starter
06/09/2026 6:20 pm
TL;DR: Access governance for AI agents and non-human identities is moving into environments where identity teams want policy enforcement without surrendering control of the runtime, as Paladin now runs in self-hosted, on-prem deployments where it can evaluate access requests, run review cycles, and recommend revoke-or-keep decisions while using customer-controlled inference paths, according to Opal Security.
NHIMG editorial — what this means for NHI practitioners
By the numbers:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials.
Questions worth separating out
Q: How should security teams use AI in access decisions without losing governance?
A: Use AI for recommendation, triage, and pattern detection first, then keep human approval for privileged, exception-heavy, or business-sensitive access.
Q: Why do headless identity models matter for NHI and AI agent governance?
A: Headless models matter because non-human actors do not wait for screens, tickets, or helpdesk workflows.
Q: What breaks if access review automation is allowed to approve everything?
A: If automation is allowed to approve everything, reviewers lose the chance to challenge bad evidence, exception handling weakens, and policy drift can become invisible.
Practitioner guidance
- Define the inference boundary for identity data Document which entitlement records, review notes, and usage signals may be processed inside the self-hosted environment and which remain off limits.
- Separate human approval from automated recommendation Allow the agent to draft keep, revoke, or flag outcomes, but make the final approval rule explicit for high-risk access, privileged roles, and NHI accounts with broad blast radius.
- Calibrate review logic to entitlement evidence Require the agent to attach role, peer-group, and last-use signals to every recommendation so reviewers can validate why the outcome was proposed before action is taken.
What's in the full announcement
Opal Security's full product post covers the operational detail this post intentionally leaves for the source:
- Self-hosted deployment setup for customers running Opal in their own AWS infrastructure.
- Configuration choices between KOTS and Helm, including the trade-offs in admin control and operational complexity.
- How the agent is configured to use a customer-owned Anthropic key or Bedrock in the customer's AWS account.
- The exact setup flow for connecting entitlement data and usage signals into review recommendations.
👉 Read Opal Security's post on self-hosted Paladin access governance →
Paladin in self-hosted deployments: what changes for IAM teams?
Explore further
View Full Forum → | NHI Foundation Course → | Our Services →
06/09/2026 6:21 pm
Self-hosted governance is becoming the default trust answer for AI-mediated identity workflows. The technical issue is not whether access governance can be automated. The issue is where the evidence, policy logic, and decision engine live when entitlements are being evaluated for both humans and non-human identities. Teams that need to keep identity context inside their own infrastructure are signalling that hosted review assistance is no longer enough for sensitive access programmes.
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 report.
- Only 44% of companies say governing AI agents is critical, yet 92% agree it matters to enterprise security, showing that policy intent still outpaces implementation.
A question worth separating out:
Q: How should organisations decide whether AI agent access belongs in IAM or separate governance?
A: If an AI agent can choose actions, call tools, or move between systems during runtime, it should be governed as a distinct identity class with explicit policy and audit coverage. If it is just a scripted workflow, ordinary machine identity controls may be enough. The decision should follow behaviour, not the label attached to the system.
👉 Read our full editorial: Self-hosted AI access governance shifts the control boundary
