DOC_TYPE: RESEARCH_LOG

PAM from Fundamentals to Advanced Practice: From Concepts to a Real Deployment

#PAM#JumpServer#Privileged Access Management#Access Control#Zero Trust

PAM is often introduced as a password vault. That is only part of the story. Privileged Access Management is the discipline of controlling who can use high-impact access to servers, databases, network devices, cloud consoles, and service accounts—and under which conditions.

This article starts with the concepts, then connects them to a real JumpServer deployment. The goal is not to promote a product. It is to make the purpose of the features in any PAM product easier to understand.

Why PAM Exists

An employee mailbox and a production-database administrator account do not carry the same level of risk. When a privileged account is compromised, an attacker may gain access far beyond a single user’s data.

The usual attack path is familiar: initial access through phishing, a vulnerability, or leaked credentials; lateral movement in search of higher privilege; then persistence, log removal, access to other systems, or data exfiltration. PAM aims to disrupt that second stage by centralizing control over privileged accounts, hiding the real credential from the user, limiting access, and recording activity.

The Four Jobs of PAM

The 4A model is a useful way to understand PAM:

ComponentQuestionExamples
AuthenticationIs this person really this user?MFA, SSO, hardware keys
AuthorizationMay this user access this system or action?RBAC, policy, JIT approval
AccountingWho accessed what, and when?Connection and access logs
AuditIs there evidence to review later?Session video, command logs, reports

Every PAM feature maps to one or more of these jobs. MFA is authentication; an approval workflow is authorization; an SSH recording supports accounting and audit.

Bastion Hosts and Credential Vaulting

Most PAM platforms use a bastion-host model:

User → PAM/Bastion → authentication, authorization, recording → target system

The user does not connect directly to the target. The bastion brokers the connection, allowing SSH or RDP services to be reachable only from that controlled point. It reduces the attack surface and centralizes oversight.

Credential vaulting is equally important. Target passwords and SSH keys are stored in an encrypted vault. A user reaches the system without seeing the real password. If someone leaves the team, disabling PAM access is enough; they never knew the credential that would otherwise need to be changed everywhere.

Least Privilege, JIT, and Recorded Access

Least privilege means giving a person only the access required for the job. JIT (Just-In-Time) access adds time to that decision: access is requested, approved, opened for a defined period, then removed automatically.

The opposite is standing privilege—administrator access that remains available for months or years even when it is rarely used. That gives an attacker a usable path at any moment. JIT reduces the exposure window.

Session recording is both an operational and a deterrent control. SSH commands, RDP screens, and database activity can be recorded. More advanced policies can block dangerous commands, generate immediate alerts, or terminate a session. Recording alone is not enough, of course; the review process and incident response need to be defined as well.

Problems PAM Helps Address

Common issuePAM approach
Shared administrator account and passwordAuthenticate the person individually and broker a controlled target account without exposing the password
Vendor or external-support accessApproved, time-bound, recorded remote access
Excessive or forgotten privilegeLeast privilege through role, target, and time constraints
Insufficient logs during an investigationSession, command, and connection records for traceability
Legacy and forgotten service accountsAccount discovery, ownership, and lifecycle control

Service accounts deserve special attention. A CI/CD pipeline account that reaches a database is privileged too, yet it is often less visible than a human account. A mature PAM program discovers these accounts, assigns ownership, and includes them in credential-rotation processes.

Secrets management and PAM are related but different. Secrets management focuses on API keys and machine-to-machine application credentials. PAM focuses on interactive human access, session control, and recording. In modern environments, the two commonly work together.

Rotation, Approval, and Emergency Access

A credential is created, used, rotated on a schedule or after a session, and revoked immediately when needed. Rotation may run every 30, 60, or 90 days; the more mature model uses temporary credentials for each session.

For critical access, the requester and approver should not be the same person. This separation of duties matters especially for production databases and infrastructure. At the same time, a well-logged break-glass route must exist for emergencies when the normal approval path is unavailable. Without it, PAM can become a new outage point.

Compliance and Maturity

PAM is not merely a preference of security teams. Frameworks such as ISO 27001, PCI DSS, SOC 2, and privacy obligations expect privileged access to be managed and auditable.

Maturity usually develops in stages: centralized vaulting; then RBAC and session recording; then JIT, automated rotation, and SIEM integration; finally, Zero Standing Privilege, where persistent privilege is removed. Not every organization needs to start at the final stage. The first requirement is knowing which accounts are critical, who genuinely needs access, and where access currently remains open.

In cloud environments, the conversation extends to CIEM. With AWS IAM roles, Kubernetes RBAC, and ephemeral containers, the issue is often an overly broad role rather than a static root password. PAM has more value when it works alongside IAM/IGA and SIEM.

Where the Theory Appeared in JumpServer

JumpServer implements the bastion model through components such as Core, Koko, Lion, Luna, and Chen. My first practical issue was an account-discovery task that failed because the Ansible executor Docker image was unavailable. The issue was more than a missing image: the tasks were intentionally isolated from the main platform in containers.

Pulling the image to the worker preserved isolation; in a disconnected network, it could be transferred offline. Disabling isolation was faster, but weakened a security boundary. Those are the moments when it is worth understanding why a control exists before bypassing it.

The separate Asset, Account, and Permission objects in the interface are another direct expression of PAM theory. The asset is the target system; the account is the real target credential; the permission determines who may use which account on which target. This separation supports different access scenarios and makes troubleshooting clearer.

Credential rotation also revealed an edition boundary: some automated capabilities may not be available in the Community Edition. Before spending time searching menus, confirm in the official documentation that the feature exists in the edition you operate.

A Sensible Starting Point

Do not start by trying to onboard everything at once. List critical systems and privileged human and service accounts. Begin with a small pilot asset; make the Asset/Account/Permission distinction clear; enable MFA and RBAC. Then introduce JIT, rotation, SIEM integration, and high availability in stages.

PAM is not software you deploy and forget. It is a living system of access decisions, policy updates, and audit cycles. Once the concepts are clear, the product interface becomes much easier to operate.