Administrators · Privileged access (PAM)
Privileged access (PAM): overview and where to start
Privileged access keeps administration credentials (servers, databases) in a vault, hands them only to people who asked and were approved, for the time requested, and records the sessions. Sessions go through an Edge appliance in your network.
Main pieces
| Piece | Where | Purpose |
|---|---|---|
| Edge appliance | «Operate» › «Edge appliances» | Connects people to targets and records sessions |
| Targets and accounts | «PAM» › «Targets» | The servers and their privileged accounts |
| Vault | Automatic | Keeps credentials encrypted, never showing them again |
| Access profiles | «PAM» › «Access profiles» | Who approves, for how long, what is allowed |
| Rotation | «PAM» › «Rotation» | Changes passwords automatically |
| Sessions | «PAM» › «Sessions» | Live sessions and recordings |
Where do I start?
- Install and confirm an Edge appliance and turn on the «Privileged access» module. See Install the appliance.
- Review «PAM settings» (recording retention). See PAM settings.
- Create the approver groups under «Manage» › «Groups».
- Create an access profile. See Access profiles.
- Register a target and its accounts, set the credential and assign the profile. See Targets and accounts.
- Publish a policy rule that allows
pam.session,pam.checkoutorpam.jit. - Ask someone to make a test request under «Access» › «My access».
Recommended protections
- «Dual control» for sensitive changes.
- A break-glass group with at least two members.
- An offline escrow key for the vault.
Limits
By default each organization can have up to 10 gateways and 500 GiB of recordings; your provider adjusts them. Only SSH sessions are supported today. In development, and not available yet: recorded remote desktop sessions (RDP), recorded database sessions (PostgreSQL) and application secrets for applications and CI pipelines.
Error codes in this article
Was this page helpful?
Thank you. Your answer stays in this browser; nothing is sent.
Sorry about that. Try:
- searching for the exact text of the message or the error code
- the error code index
- asking your organization's administrator