Every company has a handful of accounts that can do almost anything: the domain administrator who can reset any password, the database account that can read every customer record, the cloud root user that can delete a whole environment. Attackers know this, which is why these accounts are the first thing they look for once they get inside. Privileged access management is how you keep them under control.
Privileged access management (PAM) is the set of policies, processes and tools an organization uses to control, monitor and audit accounts that have more power than a normal user. It covers who gets privileged access, how they get it, how long they keep it and what they do with it. NIST describes a privileged user as one who is authorized, and therefore trusted, to perform security-relevant functions that ordinary users cannot.
In one sentence: PAM makes sure the most powerful accounts in your company are used only by the right people, only for as long as needed, and with every action recorded.
Key takeaways
- Privileged accounts include admin, root, service, database and cloud owner accounts, plus powerful business-application users.
- Stolen credentials are one of the main ways attackers get in: credential abuse was the top initial access vector in Verizon’s 2025 breach report at 22%.
- Core PAM controls are an inventory, separate admin accounts, a password vault, strong MFA, just-in-time access, session recording and regular reviews.
- The modern goal is “zero standing privileges”: nobody holds admin rights permanently, and access is granted only for a task.
- Machine and service accounts need the same discipline as people.
What counts as a privileged account?
Any account that can change systems, security settings, other people’s access or large amounts of sensitive data. Common examples:
- Administrator and root accounts on servers, laptops and network devices.
- Directory admins, such as Active Directory or Entra ID domain and global administrators.
- Cloud owner accounts that control whole AWS, Azure or Google Cloud environments.
- Database and application admins, including powerful users in ERP systems such as SAP.
- Service and machine accounts that applications, scripts and integrations use to talk to each other. These often have broad rights and passwords nobody has changed in years.
- Emergency or break-glass accounts kept for when normal access fails.
Privilege is about what an account can do, not the person’s job title. A junior contractor with a database admin login is a privileged user.
Why does privileged access matter so much?
Because one compromised admin account can undo every other control. With the right privileges an attacker can create new accounts, switch off logging, push ransomware to every machine or quietly copy data.
Credentials are a favorite way in. Verizon’s 2025 Data Breach Investigations Report, which analyzed more than 12,000 confirmed breaches, found credential abuse was the leading initial access vector at 22%. In the 2026 edition, exploitation of vulnerabilities moved to the top at 31% and credential abuse fell to 13%, but stolen logins remain a major path, and once attackers are inside, they still hunt for privileged accounts to move further.
Privileged users can also make honest mistakes with outsized effects, or misuse their access. PAM reduces both risks by limiting how much power sits in any one account at any one time.
How does PAM work?
Most PAM programs combine a few building blocks:
- Discovery and inventory. Find every privileged account, including the forgotten service accounts and local admin passwords.
- Separate admin accounts. Administrators use a normal account for email and browsing and a separate, named admin account only for admin work. Government guidance, including from Australia’s Cyber Security Centre and the US NSA, recommends this separation.
- A credential vault. Passwords and keys for privileged accounts are stored in a vault, rotated automatically and checked out when needed, so people do not know or reuse them.
- Strong authentication. Multi-factor authentication on every privileged login, ideally phishing-resistant (security keys or passkeys).
- Just-in-time (JIT) access. Instead of permanent admin rights, a user requests elevated access for a task and it expires automatically afterward.
- Session monitoring and recording. Privileged sessions are logged, and often recorded, so you can see exactly what happened.
- Reviews and alerts. Owners regularly confirm who still needs privileged access, and unusual activity raises an alert.
What are “zero standing privileges”?
Traditional PAM focused on vaulting passwords for permanent admin accounts. The newer approach, often called zero standing privileges, aims for a default state where no identity, human or machine, holds admin rights at all. People are eligible for elevated access, and they receive it just in time, for a specific task and a limited period, after which it disappears.
Fully reaching zero is hard, so many teams treat it as a direction: fewer permanent admins every quarter, and short-lived access for everything else. It fits naturally with zero trust, which assumes no account should be trusted just because it is already inside the network.
How is PAM different from IAM?
Identity and access management (IAM) covers every user: creating accounts, signing in, joining and leaving. PAM is a specialized part of that picture for the small number of accounts that can do the most damage, with extra controls such as vaulting, approval workflows and session recording.
What does PAM look like in SAP?
SAP systems have their own powerful users, such as accounts with SAP_ALL or broad Basis rights. Many companies handle them with emergency access management, often called firefighter access, where people borrow elevated access for a limited time and every action is logged and reviewed. Our guide to SAP firefighter access explains how that works, and SAP GRC covers the wider governance tooling.
A worked example: the weekend database fix
Imagine a database administrator who needs to fix a failed overnight job on a Saturday. Without PAM, they log in with a permanent admin account whose password lives in a spreadsheet. With PAM:
- They sign in with their own account and MFA, then request admin access to that one database, citing the incident ticket.
- The request is approved automatically for on-call staff, and the vault opens a session without revealing the password.
- The session is recorded, and access ends after two hours.
- On Monday, the team lead reviews the session log against the ticket.
The fix happens just as quickly, but there is no permanent admin account to steal and a full record of what changed.
How do you get started with PAM?
- Build an inventory of privileged accounts, starting with domain admins, cloud owners and database admins.
- Turn on MFA for every privileged login.
- Split admin work into separate named accounts and stop sharing admin passwords.
- Put the most powerful credentials in a vault and rotate them.
- Pick one system and pilot just-in-time access, then expand.
- Review privileged access at least quarterly and remove what is no longer needed.
Frequently asked questions
What does PAM stand for?
PAM usually stands for privileged access management. You may also see privileged account management or privileged identity management, which refer to closely related ideas.
Is PAM only for large companies?
No. Smaller organizations have fewer admins but the same risk. Separate admin accounts, MFA and a password vault are affordable starting points for any size of business.
What is just-in-time access?
Just-in-time access gives a user elevated permissions only when they need them for a specific task and removes them automatically afterward, so no permanent admin rights are left for attackers to steal.
Do service accounts need PAM?
Yes. Service and machine accounts often have broad rights and old passwords. They should be inventoried, given only the access they need, and have their credentials stored and rotated in a vault.
Go deeper
Our plain-language PDF books cover this in detail, each with a free sample: Privileged Access Management, Identity and Access Management Basics and Identity Threat Detection and Response.
The bottom line
Privileged accounts are the keys to the kingdom, and attackers know it. PAM keeps those keys in as few hands as possible, for as little time as possible, with a record of every use. Start with an inventory, MFA and separate admin accounts, then work toward just-in-time access and zero standing privileges.
Sources: NIST CSRC Glossary: privileged user; Verizon: 2025 Data Breach Investigations Report; Infosecurity Magazine: Verizon DBIR, vulnerability exploits overtake credentials; Australian Cyber Security Centre: Restricting administrative privileges; Canadian Centre for Cyber Security: Managing and controlling administrative privileges; GSA: Privileged Identity Playbook; NSA: Defend Privileges and Accounts; Palo Alto Networks: What is just-in-time access.