Don't Panic — Privileged Access Management

Privileged access management, usually called PAM, is the arrangement that puts controls around the route from a named requester to an action powerful enough to change a system. Before that arrangement, an administrator might keep a broad role active, use a shared account, or handle a reusable password. Those methods can get the job done. They are also rather poor at answering who used the power, why, and whether it still exists afterwards.

The useful picture is a controlled path. First, find the accounts, roles, keys, and targets that matter. Then identify the requester, check a policy, grant narrowly bounded privilege, connect through a broker where possible, collect evidence, end the access, and compare the intended state with the target's actual state. A vault is one station on this route, not the entire railway. A direct login around it is a direct login around the control.

The surprise is that just-in-time access is not a magic expiry sticker. A temporary role can end while a target session or token still works. A checked-out password can be copied before it rotates. The end condition therefore has several pieces: the session, role, account, token, and any exposed credential need their own route to an end state. Otherwise the permission has left the office but neglected to tell the building.

People are only part of the picture. Non-human identities include service accounts and automation workloads, and they can hold the same consequential access. They cannot request approval before every scheduled job, so their safety depends on ownership, narrow scope, managed authentication material, known dependencies, and retirement. Rotating a credential without knowing what uses it is an unusually efficient way to discover a service you had forgotten existed.

PAM also has limits and dependencies. An approved administrator can still make a harmful change. A failed broker, vault, identity provider, or recording system can block or weaken the normal route. Emergency access exists for that reason, but it must be protected outside the dependency it recovers and reviewed every time it is used.

Read the Intro for the full control plane and its design choices. Use the Slides to keep the route and its failure points in view. Keep the Cheatsheet nearby when comparing grant mechanisms, evidence, and operational signals. The Quiz tests the distinctions that tend to blur together when everything is labelled “admin access.”

Don't Panic — Privileged Access Management

Relevant careers