Delinea’s acquisition of StrongDM expands the vendor’s privileged access footprint from vaulting and session brokering into the infrastructure access layer: databases, servers, Kubernetes clusters and cloud consoles reached through a single brokered gateway. The strategic logic is straightforward. Privileged access management grew up protecting interactive administrator logins to on-premises systems. The estate it now needs to protect is largely ephemeral, API-driven and distributed, and the controls built for permanent servers map poorly onto it.

The problem: cloud infrastructure broke the PAM perimeter

In a traditional data centre, privileged access has a shape. There are servers, there are administrators, and there is a jump host. Vault the credentials, broker the session, record the activity, and the control model holds. Cloud infrastructure dissolves each of those assumptions. Workloads are created and destroyed by pipelines. Engineers reach production through multiple consoles and CLI tools. Access paths run from CI systems to clusters to managed databases without a human authenticating at any point.

The consequence is a visibility and enforcement gap. Standing cloud roles accumulate because removing them risks breaking a pipeline nobody fully understands. Direct database access bypasses the brokered session entirely. Kubernetes service accounts multiply with no owner. Security teams can enumerate these entitlements in a cloud posture tool, but posture tools report; they do not broker access or produce session-level evidence of privileged account use.

What infrastructure access brokerage adds

Three capabilities matter when a PAM platform extends into this layer.

Protocol-aware brokering without network changes. Access to a database or a cluster should be mediated by policy rather than by network position. That means authenticating the human or workload, evaluating the request against role and context, then proxying the connection so the underlying credential is never exposed to the requester. Done well, it removes the need for bastion hosts and for distributing database passwords to application teams.

Just-in-time entitlements across cloud roles. Rather than permanent IAM roles, access is granted for a bounded window against a ticket or approval, then automatically revoked. The audit value is significant: the organisation can demonstrate that no engineer held standing production access during a given period, which is precisely the evidence that privileged account security frameworks and cyber insurers now request.

Uniform session management evidence. Recording is routine for SSH and RDP. It is not routine for database queries or kubectl sessions. Extending session management to those protocols closes a gap that attackers have learned to exploit, because a query executed directly against a production database is both high impact and, in many estates, entirely unlogged at the privileged access layer.

Consolidation and its trade-offs

The acquisition also reflects a broader market pattern. CyberArk’s absorption into Palo Alto Networks, Delinea’s expansion, and the growth of cloud-native challengers such as Britive and Teleport all point the same way: buyers want privileged controls to follow the workload, not the data centre. Consolidating vaulting, endpoint privilege and infrastructure access under one policy engine reduces the number of places an administrator must be defined and audited.

The trade-off is integration depth. Acquired infrastructure access technology must be reconciled with existing vaults, approval workflows and SIEM pipelines rather than sitting alongside them as a second control plane. Practitioners evaluating any consolidated platform should test the same access path end to end: a pipeline deploys, an engineer debugs, a contractor requests temporary database read access, and the auditor asks for the evidence. If that path crosses two policy engines, the consolidation has not been completed.