Notifications
Clear all
Topic starter
28/05/2026 11:36 am
TL;DR: Delinea’s partner webinar centers on StrongDM positioning, product roadmap updates, and how identity security, cloud infrastructure access, and AI-driven environments are changing customer priorities, according to Delinea. The practical issue is not the demo itself but how partners translate infrastructure access control into NHI governance and agentic AI access decisions.
NHIMG editorial — here’s why we think this discussion matters
By the numbers:
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools.
- Only 5.7% of organisations have full visibility into their service accounts.
- NHIs outnumber human identities by 25x to 50x in modern enterprises.
Questions worth separating out
Q: How should security teams govern AI-driven infrastructure access?
A: Security teams should govern AI-driven infrastructure access with session-based mediation, short-lived credentials, and action-level policy checks.
Q: What is the difference between access convenience and access governance for NHIs?
A: Access convenience focuses on making connections easy, while access governance focuses on constraining what a non-human identity can do, for how long, and under which conditions.
Q: When should organisations replace standing access with just-in-time controls?
A: Organisations should replace standing access with just-in-time controls when the identity can perform privileged or repeated infrastructure actions, or when the access path is shared across teams and environments.
Practitioner guidance
- Classify every infrastructure access path Separate human-admin access, service account access, and AI-mediated access paths so each can be governed with the right policy, session length, and revocation process.
- Require session mediation for elevated operations Prefer access patterns that broker the session rather than distributing long-lived credentials directly to operators or automation.
- Build partner-facing runbooks for AI-driven access Document how access requests are approved, constrained, logged, and revoked when an AI system interacts with infrastructure tools.
For teams modernising infrastructure access, the real test is whether the programme can reduce standing privilege without creating operational dead ends?
👉 Register for Delinea's Technical Partner Exchange EMEA on StrongDM and AI access →
Explore further
28/05/2026 11:40 am
Partner education is becoming a control plane for NHI governance. When a webinar focuses on roadmap alignment, technical deep dives, and field success stories, it is really shaping how the channel explains access control to customers. That matters because partners often translate vendor capability into operational policy, especially in cloud infrastructure access and AI-driven environments. The practitioner takeaway is to treat partner guidance as part of the governance model, not just as sales support.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools.
A question worth separating out:
Q: Why do AI-driven environments make identity governance harder?
A: AI-driven environments make identity governance harder because software can request, chain, and reuse access dynamically across systems. That creates a wider trust surface than a human-only workflow. Teams need runtime policy, strong logging, and short-lived access so the agent’s effective authority stays bounded.
👉 Read our full editorial: Delinea partner exchange frames StrongDM amid AI access shifts
