Ping Identity has introduced a just-in-time privileged access capability intended to cover the full identity lifecycle, joining a growing group of vendors that treat standing privilege as a defect rather than an administrative convenience. The announcement lands in a space where two disciplines, privileged access management and identity governance, have spent years describing the same risk from different seats in the room.

The problem is easy to state. Most organisations still grant permanent administrative rights because the alternative was historically too slow, and a change freeze is easier to defend than a blocked incident response. The result is a large population of accounts holding rights they need for a few minutes a month, protected by a password and, if the programme is mature, a vault. Governance systems then perform access reviews over entitlements that were never really decisions, and the review produces approvals rather than removals.

Just-in-time only works as a governance control

Elevation on demand is only an improvement if each elevation is a governed event with a requestor, a reason, an approver and an expiry. Where that exists, standing privilege falls sharply and the audit trail becomes a record of intent rather than a record of entitlement. Where it does not, just-in-time becomes a faster way to hand out the same access with less oversight, and the review problem is simply hidden behind a ticket queue.

Lifecycle integration is the differentiator

The capability is described as spanning the full identity lifecycle, which is the right framing. Privileged access is not a separate population: a departing engineer’s break-glass account is an offboarding failure, a contractor’s admin right is a third-party risk question, and a service account with standing rights is an inventory problem. Governance platforms have the ownership and review machinery; PAM platforms have the session control and credential custody. Buyers should test whether the join between them is real, or a CSV export.

Ephemeral credentials change the review model

Where credentials are issued for the duration of a task and then destroyed, the review question shifts from “does this person still need this role” to “was this elevation justified and appropriately approved”. That is a better question, and it needs different reporting. Identity teams should check that the platform can aggregate elevations by person, by target system and by approver, because volume analysis is how excessive approval patterns get found.

Operational trade-offs to plan for

Just-in-time access introduces dependency on the approval path. If the broker is unavailable during an incident, recovery slows at the worst moment, so break-glass design and offline procedures still matter. Approval fatigue is the other risk: a queue that asks for confirmation dozens of times a day trains approvers to click through, which defeats the control. Thresholds and risk-based auto-approval need to be tuned deliberately rather than left at defaults.