KBIdentity Bytes Knowledge Base — plain-English explainers behind every lab track.HomeLabs
HomeKnowledge Base › Privileged Access
?
Track 05 · Article

Privileged Access: questions, answered

The Privileged Access track is deliberately vendor-neutral — you learn the tradecraft, not one product's console. These answers explain the PAM concepts the labs put into practice with Vault and SSH.

privileged access managementPAMjust-in-time accessHashiCorp VaultSSH certificatessecrets managementsecrets rotationbreak-glass accountprivileged identity managementleast privilege
?What is privileged access management (PAM)?+

PAM is the set of controls for accounts and credentials that can cause the most damage — domain admins, root, cloud owners, service accounts and API keys. It covers vaulting secrets, brokering and recording privileged sessions, enforcing approval and just-in-time elevation, and rotating credentials. The goal is to eliminate standing privilege and make every privileged action accountable.

?What is just-in-time (JIT) privileged access?+

JIT access grants elevated permissions only when needed, for a short window, and revokes them automatically. Instead of a permanent admin account an attacker can target year-round, privilege exists for minutes and is tied to an approved request. Lab 01 and the Vault labs issue short-lived, just-in-time credentials for both humans and workloads.

?What is HashiCorp Vault and how is it used for PAM?+

Vault is a secrets-management platform that stores, generates and rotates credentials behind identity-based policy. Its dynamic secrets engines mint short-lived database, cloud and SSH credentials on demand, so nothing long-lived sits in config files. The Vault labs build policies, auth methods like AppRole and Kubernetes auth, and dynamic secrets with a full audit trail.

?What is the difference between SSH keys and SSH certificates?+

Plain SSH keys are static: public keys pile up in authorized_keys files with no expiry and no central revocation, which becomes unmanageable at scale. SSH certificates are signed by a trusted certificate authority, carry an expiry and principals, and need no per-host key distribution — you revoke by letting them expire or rotating the CA. Labs 04 and the SSH mastery lab move you from keys to certificate-based access.

?Why does secrets rotation matter for machine identities?+

Service accounts, API keys and database credentials often outlive the people who created them and get copied into pipelines and images. Regular, automated rotation limits how long a leaked secret is useful and forces systems to fetch credentials dynamically rather than hard-code them. Vault's dynamic secrets and lease model make rotation the default rather than a manual chore.

?What is a break-glass account and how should it be protected?+

A break-glass (emergency access) account is a highly controlled account used only when normal admin access fails — for example, if Conditional Access or the IdP locks everyone out. It is typically cloud-only, excluded from the very policies that could cause the lockout, protected with the strongest possible authentication, and closely monitored so any use raises an alert. Every hardening programme needs at least two.

?How does PIM differ from a traditional password vault?+

A password vault stores and checks out static credentials; privileged identity management (PIM) grants time-boxed role activation with approval and justification, so no standing privilege exists to check out in the first place. They are complementary — vaults protect the secrets that must exist, while PIM removes the need for permanent elevated roles. Lab 18 covers the PIM activation and review model.

Practise these concepts

Reading is a start — the skill sticks when you do the work. Open the Privileged Access track and run the labs behind these answers.