Endpoint privilege management (EPM) and privileged access management (PAM) both claim to remove standing privilege, yet they stop different attacks on different systems, and buying one in place of the other leaves a predictable gap. EPM takes local administrator rights away from the people who use workstations and replaces them with rule-based elevation of single tasks. PAM controls the accounts that administer servers, directories, cloud consoles and network devices: it vaults their credentials, grants them just in time and records what is done with them. This guide compares them as architectures, maps where each breaks the attack chain, and covers approval fatigue, servers vs workstations and sequencing, for architects deciding what to fund first.
Key takeaways
- EPM governs what a user's session may do on one device; PAM governs who may act as a privileged account anywhere. One shrinks the blast radius of a phished laptop, the other shrinks the blast radius of a stolen admin credential.
- They break different steps of the same intrusion. EPM denies the attacker local admin on the first host, which blocks most credential dumping there; PAM makes the credentials the attacker would harvest next short-lived, approved and recorded.
- Fatigue is the shared failure mode. Elevation prompts and PAM approvals both decay into reflex clicks unless frequent requests become rules and approval effort matches the risk of the action.
- Workstations and servers need different tools. Task elevation suits user devices with predictable software; servers need role-scoped administration, brokered sessions and vaulted local accounts, with task-scoped delegation such as Just Enough Administration where it fits.
- Most estates need both, in sequence. Protect tier 0 accounts with PAM first, remove local admin from the workforce with EPM second, then join them so IT staff elevate through the same request, approval and evidence trail.
The short answer
If your problem is that ordinary users are local administrators, buy or switch on EPM. If your problem is that administrators hold standing, shared or unrecorded privileged accounts on servers, directories, databases, network devices and cloud platforms, you need PAM. With both problems, the question is order. The Endpoint Privilege Management Guide covers rule design and rollout in depth, and the Privileged Access Management Guide covers vaulting and session controls.
What each control actually governs
Endpoint privilege management
EPM is an agent or operating system feature on the endpoint. The user's account is a standard user; when a task needs administrative rights, the agent checks the file against a rule and, if allowed, starts that one process with elevated rights. Microsoft's Intune implementation is a documented example: it states that users "run as a standard user (without administrator rights) and complete tasks that require elevated privileges", and for most elevation types the process runs under a virtual account isolated from the user, with neither account added to the local Administrators group. Its elevation types are Automatic, User confirmed (optionally with Windows authentication and a business justification), Support approved, Elevate as current user and Deny. Microsoft warns that Elevate as current user gives the process the user's full context and "introduces a broader attack surface", so it recommends the virtual account wherever compatibility allows.
The unit of control is the process: one task gets more power and no reusable admin credential is issued.
Privileged access management
PAM is a central service in front of administrative interfaces. The NCSC describes its two core ideas as just in time administration, where an administrator uses a normal credential to request a temporary privileged one, and just enough administration, where they choose a predefined role that carries only the permissions the task needs. Products add vaulting, rotation, brokered sessions and recording. The unit of control is the privileged account or role: who may become a Domain Admin, database owner, cloud owner or root, for how long and through which path. See the IAM vs PAM for how this sits beside the wider identity programme.
Side-by-side comparison
| Dimension | Endpoint privilege management | Privileged access management |
|---|---|---|
| Primary question | May this process run with admin rights on this device? | May this person or workload act as this privileged account, now, and how? |
| Where enforcement happens | Agent or OS component on each endpoint | Central vault, broker, proxy or cloud role service in front of targets |
| Typical targets | Windows and macOS workstations, some Linux desktops | Directories, servers, databases, hypervisors, network devices, cloud control planes, SaaS admin consoles |
| Credential handling | None issued to the user; elevation is local and process-scoped | Vaults, rotates and checks out credentials, or brokers sessions without revealing them |
| Evidence produced | Managed and unmanaged elevation events, file, hash, justification | Request, approver, reason, check-out window, session recording, commands |
| Main attack it disrupts | Privilege escalation and credential theft on the first compromised host | Reuse and abuse of high-value admin credentials across the estate |
| Main new risk | Over-broad elevation rules; agent tampering by anyone still admin | The PAM platform itself, its admins and its connector accounts |
Threat model, architecture and failure modes: EPM
Threat model: the attacker lands on a workstation through phishing, a malicious download or a browser exploit and runs code as the user. If the user is a local administrator, the attacker can bypass User Account Control (ATT&CK T1548.002), read LSASS memory (T1003.001), create local accounts and switch off defences. Removing admin does not stop the initial code; it stops the escalation to credentials for the next system.
Architecture in words: a policy service sends rules and a default response to an agent, which matches files by hash, publisher or path and reports managed elevations and unmanaged ones (someone still holds admin). Unmanaged elevations are the best signal the programme is incomplete.
Failure modes:
- Admin by rule: automatic rules for shells, script hosts or installers that can launch children turn one approved file into a general admin console. Microsoft warns that broad automatic rules can have a widespread security impact.
- Exceptions that never close: teams keep local admin "for now" and can tamper with the agent.
- Current-user elevation by default: the elevated process inherits the user's full context.
Controls: hash or pinned publisher rules for automatic elevation, child processes required to match their own rule, a default response of support approval or deny for unknown files, application control alongside, and alerting on any addition to the local Administrators group. See Securing the endpoint privilege management (EPM) itself.
Threat model, architecture and failure modes: PAM
Threat model: the attacker already has some foothold and wants accounts that control many systems: domain administrators, server local administrators reused across hosts (T1078.003), domain service accounts with broad rights (T1078.002), or cloud owners. They move laterally with harvested hashes and admin shares (T1550.002, T1021.002). PAM makes privileged credentials rare, short-lived, approved and observed, so there is less to steal and use is visible.
Architecture in words: administrators authenticate with phishing-resistant MFA from a trusted device, request a role with a reason, are approved by rule or person, then check out a rotated credential or open a recorded brokered session. Connectors rotate passwords and keys. The NCSC is explicit that "the PAM system is itself an attack surface": it holds or can change every privileged credential it manages, so it needs architectural isolation, patching, monitoring and a tested break-glass path for outages.
Failure modes:
- Vault as a password store: credentials are vaulted but checked out for days, never rotated on check-in, and pasted into scripts.
- Bypass paths: administrators keep direct RDP or SSH to targets, so the broker records only the people who choose to use it.
- Admin workstations left out: a strong PAM workflow launched from a daily-driver laptop where the administrator is still local admin; the session can be hijacked on the endpoint.
Controls: zero standing membership in tier 0 groups, rotation on check-in, network rules that only allow administrative protocols from the broker or privileged access workstations, separate review of PAM administrators and connector accounts, and session evidence for high-impact roles. See Securing the PAM Vault Itself and the Privileged Access Workstations Guide.
Where each control stops an attack
One intrusion, phished user to domain compromise, mapped against both controls:
| Attack step | ATT&CK | EPM effect | PAM effect |
|---|---|---|---|
| Escalate on the phished workstation | T1548.002 Bypass User Account Control | Blocks it: the user token has no admin to elevate | None: the workstation user is outside PAM scope |
| Dump cached credentials on that host | T1003.001 LSASS Memory | Blocks most of it: reading LSASS needs admin or SYSTEM | Reduces value: vaulted admin passwords have rotated since last use |
| Reuse a local admin password on other hosts | T1078.003 Local Accounts | Indirect, only with unique local passwords | Blocks it where server local accounts are vaulted and rotated |
| Pass the hash over admin shares | T1550.002, T1021.002 | Limited: less to harvest on user devices | Limits it: no standing admin hashes; admin protocols only from the broker |
| Use a domain admin or privileged service account | T1078.002 Domain Accounts | None | Primary control: JIT membership, approval, recording, rotation |
| Abuse an administrator's own workstation | Several | Primary control: admins are standard users on their daily device | Partial: PAM sessions launched from privileged access workstations only |
The last row is where the two meet: an administrator who is local admin on their email laptop undermines the PAM workflow that starts there, so EPM or a privileged access workstation is what makes PAM sessions trustworthy. Microsoft's enterprise access model states the same principle at architecture level: prevent control of higher planes from lower planes.
Elevation request fatigue and approval fatigue
Both controls fail the same way: too many prompts for users, too many check-out requests for approvers, so people approve without reading. The fixes are parallel.
- Measure the volume first. Run EPM in reporting mode and PAM in request-logging mode for several weeks. Rank requests by file or by target and role.
- Turn the top of the list into rules. The 20 files that make up most elevations become hash or publisher rules; the routine PAM requests for low-impact roles become rule-based auto-approval with a ticket reference. The NCSC lists rule-based auto-approval alongside multi-party approval and says approval should reflect the impact of compromise.
- Reserve human approval for real decisions. Support approval for unknown files on sensitive personas; named approvers for tier 0 roles; dual control where one action can harm the whole estate. See the Dual control and four-eyes approval for privileged and agent actions.
- Set a service-level target. Slow approvals drive requests for permanent exceptions.
Servers vs workstations
Workstations suit EPM because their software sets are broadly predictable and the user is a single person doing personal tasks. Servers are different: changes are administrative, many people and services act on the same host, and evidence matters more than convenience.
| Concern | Workstations | Servers |
|---|---|---|
| Who needs elevation | The device's user, for installs, drivers and settings | Administrators and automation, for configuration and maintenance |
| Best-fit control | EPM rules, standard users, LAPS-managed local account for support | PAM: JIT group membership, brokered sessions, vaulted local and service accounts |
| Task-scoped delegation | EPM elevation of single files | Just Enough Administration on Windows, sudo command rules on Linux |
| Evidence needed | Elevation events and justification | Who approved, session recording or command transcript |
Server EPM helps application owners who need a few admin tasks without a full admin role, but it does not replace brokered, recorded sessions for high-impact systems. Microsoft's Just Enough Administration shows the server-side version of task elevation: it "enables you to remove users from widely privileged local/domain administrator roles", restricts sessions to specified cmdlets and commands, can run them under virtual accounts or group managed service accounts, and keeps transcripts of what each user ran. Microsoft's example is a DNS administrator who needs no Domain Admin rights. On Linux the equivalent is narrow sudo rules; see the sudo and sudoers Security Guide. For local administrator passwords on servers specifically, the Local Administrator Password Solution vs PAM Vaulting comparison covers when LAPS is enough and when a vault is needed.
Decision guidance
| Situation | Start with | Why |
|---|---|---|
| Most users are local admins; few servers; cloud-first | EPM (or plain standard users with a software catalogue) | The workforce endpoint is the biggest privilege surface |
| Domain admins and shared server passwords in daily use | PAM for tier 0 and servers | One stolen tier 0 credential outweighs any single laptop |
| Regulator or auditor asks for evidence of admin activity | PAM with session evidence | EPM records elevations, not administrative sessions |
| Developers need frequent installs and tooling changes | EPM with persona rules | PAM approvals per install would be unworkable |
| Small organisation, one or two IT staff | Standard users, LAPS, separate admin accounts, cloud-native JIT roles | Both full products may be more than the risk needs; CIS Safeguard 5.4 is met with dedicated admin accounts |
| Large, regulated, hybrid estate | Both, with one request and evidence trail | Different attack steps, shared fatigue and reporting problems |
Sequencing roadmap
- Inventory privilege in both places. Count local Administrators members per device (users, IT, service accounts, unknown SIDs) and, separately, members of tier 0 groups, cloud owner roles and server admin groups. The Privileged Account Discovery and Onboarding Guide covers sources.
- Protect tier 0 with PAM first. Remove standing membership from domain and cloud control-plane roles, vault and rotate their credentials, and require privileged access workstations.
- Remove local admin from IT staff's daily accounts. Administrators become standard users on their email and browsing device, using EPM or a separate admin account for local tasks. This closes the bridge between the two controls.
- Run EPM in reporting mode for the workforce. Use managed and unmanaged elevation data to build persona rules; pilot with a willing department; expand in rings.
- Extend PAM to servers and databases. Vault server local accounts, broker sessions for production, add JEA or sudo rules for routine tasks.
- Join and tighten. One request portal and evidence store for EPM support approvals and PAM check-outs; move EPM default responses towards deny, shorten check-out windows and retire unused rules.
Testing and rollback: every phase starts in audit or reporting mode on a pilot group. For EPM, keep local group membership centrally managed so a ring can be restored by removing it from the policy assignment. For PAM, keep the previous access path open for the pilot group until brokered access is proven, and test break-glass before removing standing access. See the Break-Glass Account Guide.
Worked scenario
A manufacturer has 4,000 Windows laptops where 60 percent of users are local admins, 600 Windows and Linux servers, a single shared server local admin password, eight permanent Domain Admins and a PAM licence bought two years ago that holds only firewall passwords.
- Month 1 to 2: the eight Domain Admins lose standing membership and request it through PAM from privileged access workstations, with approval from a second administrator outside change windows. The shared server password is replaced by vaulted, per-server credentials rotated on check-in.
- Month 2 to 3: 120 IT staff become standard users on their laptops. EPM rules cover their admin tools; anything else goes to support approval. PAM sessions now start from devices without standing admin.
- Month 3 to 8: EPM reporting for the workforce shows 35 files account for most elevations. They become hash or publisher rules; engineering gets a persona with CAD and driver tools; local admin is removed ring by ring.
- Month 6 to 10: brokered server sessions; JEA for DNS and print teams; command-specific sudo on Linux.
- Result: a phished laptop yields a standard user, and the admin credentials an attacker would hunt for next exist only inside short PAM check-out windows.
Where identity fits
Both controls have non-human identities at their core. EPM agents, PAM connectors and reconciliation accounts often hold administrator rights on every device or target they manage, and services installed to run as local administrator escape EPM entirely because no person ever elevates. Treat them as privileged NHIs with owners, scoped rights and reviews. See the Service Account Security Guide and, for the machine credential side of PAM, the PAM vs Secrets Manager.
Detection and measurement
| Signal | Source | What it tells you |
|---|---|---|
| Unmanaged elevations | EPM reporting | Someone still holds local admin outside the programme |
| Event 4732, member added to a security-enabled local group | Windows Security log | Local Administrators changed outside managed policy |
| Event 4672, special privileges assigned to new logon | Windows Security log on servers and DCs | Privileged logon that did not come through PAM |
| Admin protocol sessions not from the broker | Network flow logs | PAM bypass paths still open |
| Check-outs without rotation on check-in | PAM audit | Vault used as a password store |
| Approval decision time and rejection rate | EPM and PAM workflow | Fatigue: near-zero rejections with fast approvals means rubber-stamping |
Metrics that show both controls working together:
- Standing admin coverage: share of devices with no standard user in local Administrators, and number of accounts with permanent tier 0 membership (target zero outside break-glass).
- Brokered share: percentage of privileged server and directory sessions that went through PAM.
- Rule conversion rate: share of elevations handled by rules rather than prompts or approvals, trending up.
- Admin device hygiene: percentage of PAM sessions launched from privileged access workstations or devices where the administrator is a standard user.
- Median approval time against a published target.
Common failure patterns
- Buying PAM to fix local admin. Making thousands of users check out passwords for installs adds friction and leaves them admin between sessions.
- Buying EPM to fix domain admins. Task elevation on endpoints does nothing for a standing Domain Admin whose credentials are cached on a file server.
- Administrators exempted from EPM. The people with the most valuable credentials keep local admin on the device where they read email, which is the device an attacker targets.
- Two approval queues. EPM and PAM approvals run by different teams with no shared evidence, so neither is reviewed.
- No offline plan. A PAM outage during an incident leads to standing access being restored and never removed.
Framework mapping
| Framework | Reference | EPM | PAM |
|---|---|---|---|
| NIST SP 800-53 Rev. 5 | AC-6 Least Privilege; AC-6(2) Non-privileged Access for Nonsecurity Functions; AC-6(10) Prohibit Non-privileged Users from Executing Privileged Functions; CM-11 User-installed Software | Primary | Supporting |
| NIST SP 800-53 Rev. 5 | AC-2(7) Privileged User Accounts; AC-6(5) Privileged Accounts; AC-6(7) Review of User Privileges; AC-6(9) Log Use of Privileged Functions | Supporting | Primary |
| NIST CSF 2.0 | PR.AA-05 access permissions managed with least privilege and separation of duties | Yes | Yes |
| CIS Controls v8.1 | 5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts; 5.5 Inventory of Service Accounts | 5.4 | 5.4, 5.5 |
| ISO/IEC 27001:2022 Annex A | A.8.2 Privileged access rights; A.8.18 Use of privileged utility programs; A.8.19 Installation of software on operational systems | A.8.18, A.8.19 | A.8.2 |
Practitioner checklist
- Count local Administrators members per device and permanent tier 0 members, and report both to the same owner.
- Put tier 0 and cloud control-plane roles behind PAM with zero standing membership before the workforce EPM rollout.
- Make administrators standard users on their daily devices, or move privileged work to privileged access workstations.
- Run EPM in reporting mode, convert the most frequent elevations to hash or publisher rules, and prefer virtual-account elevation over current-user elevation.
- Restrict administrative protocols on servers to the PAM broker and privileged access workstations.
- Use JEA or command-specific sudo rules for routine server tasks instead of full admin roles.
- Match approval effort to impact: rules for routine low-risk requests, named approvers and dual control for tier 0.
- Treat EPM management roles, PAM administrators and connector accounts as privileged identities.
- Test break-glass for both platforms before removing standing access.
Standards and references
- NIST: SP 800-53 Rev. 5 Security and Privacy Controls
- NCSC: Secure system administration, use privileged access management
- NCSC: Secure system administration
- CIS: Controls v8.1, Control 5 Account Management
- CISA and NSA: Top Ten Cybersecurity Misconfigurations (AA23-278A)
- Microsoft: Enterprise access model
- Microsoft: Intune Endpoint Privilege Management overview
- Microsoft: Just Enough Administration overview
Related NHI Mgmt Group resources: Endpoint Privilege Management Buyer's Guide, PAM Buyer's Guide, Tiered Administration and Enterprise Access Model Guide, JIT Access Guide.