TL;DR: Identity security platforms need shared services, cloud-native delivery, and practical AI to keep pace with modern attack and operational demands, according to Delinea. It notes it can patch 28 clusters worldwide in an hour and support over 40 engineering teams delivering independently, while stitching tools together may look complete but leaves governance, integration, and response speed fragmented.
NHIMG editorial — based on content published by Delinea: Platform truths: What others stitch, we build
By the numbers:
- The next morning, we deployed over the course of an hour an upgrade to 28 clusters worldwide.
- We have over 40 engineering teams delivering to production independently.
Questions worth separating out
Q: How should security teams evaluate stitched identity platforms versus unified ones?
A: Security teams should test whether policy, audit, secrets handling, and access decisions share the same state.
Q: Why do cloud-native identity platforms matter for IAM and PAM operations?
A: Cloud-native platforms matter because they can absorb urgent security updates, scale across environments, and preserve control continuity without forcing disruptive migrations.
Q: What do security teams get wrong about practical AI in identity governance?
A: Teams often treat AI as a separate intelligence layer when it should be evaluated as part of the identity control plane.
Practitioner guidance
- Audit control-plane fragmentation Map where vaulting, session recording, secrets access, authorization, and analytics live today.
- Test remediation speed under real failure conditions Ask vendors how they deploy security fixes across clustered environments, what happens during urgent patching, and how they preserve service continuity while changing shared components.
- Validate AI features against existing governance data Require AI-driven auditing or authorization to use the same session, ticket, location, and risk inputs already relied on by your identity programme.
What's in the full article
Delinea's full blog post covers the operational detail this post intentionally leaves for the source:
- How the platform’s shared services are used across vaulting, analytics, remote access, and AI capabilities.
- The 28-cluster remediation example and why Delinea says cloud-native architecture changed the deployment outcome.
- How the AI-based authorization agent evaluates ticket, location, and risk context in real time.
- Why the vendor frames platform consolidation as a long-term operating choice rather than a feature bundle.
👉 Read Delinea's analysis of cloud-native identity platforms and practical AI →
Cloud-native identity platforms and AI governance: what changes for teams?
Explore further
Platform stitching is a governance problem before it is a product problem. When vaulting, analytics, remote access, and authorization are assembled from separate systems, the organisation inherits multiple states of truth and multiple audit paths. That fragments policy enforcement across human, NHI, and emerging AI-driven workflows. The implication is that identity leaders should evaluate whether the platform shares control primitives, not just whether it claims broad coverage.
A few things that frame the scale:
- 71% of NHIs are not rotated within recommended time frames, increasing the risk of compromise over time, according to Ultimate Guide to NHIs.
- Only 5.7% of organisations have full visibility into their service accounts, which means most identity programmes are still operating with partial control awareness.
A question worth separating out:
Q: How do identity buyers judge whether a platform can support long-term governance?
A: Buyers should ask whether the platform can evolve continuously, respond quickly to threats, and avoid annual migration cycles. Long-term governance depends on stability under change, not just feature breadth. If the architecture cannot keep shared state intact while services change, the organisation will pay for that with more manual oversight and weaker assurance.
👉 Read our full editorial: Cloud-native identity platforms and AI governance: why stitching fails