Writing

Identity comes before privileged access management

Why centralizing Linux identity is the foundation that makes privileged access, audit and offboarding manageable.

Identity & access, Linux, Security

Privileged access management tools promise session recording, approvals and just-in-time elevation. All of that assumes something more basic is already true: every person has exactly one identity, and every system trusts it.

Local accounts do not scale

With local users and copied SSH keys, the question “who can access this server?” has no single answer. Offboarding becomes a search. Audit logs record usernames that may be shared.

Centralize first

A central identity provider for Linux (FreeIPA is one option) gives you users, groups, host enrollment, host-based access control and sudo rules in one place. Access follows group membership, so changing someone’s role changes their access everywhere.

Then layer privileged access on top

Once identity is central, elevation rules, approvals and session audit have something reliable to attach to. Done in the other order, PAM tooling ends up wrapping the same unmanaged accounts it was meant to replace.