Impersonate a client after authentication
Verified with Windows Security Options 26H2 — updated on July 25, 2026
Security policy
This is a Security Options policy (Windows Settings > Security Settings), applied by the security engine — not an Administrative Template (ADMX). In GPMC/gpedit it is configured under Local Policies > Security Options.
Microsoft security baseline (Windows 11 v26H2 v2): Administrators, LOCAL SERVICE, NETWORK SERVICE, RESTRICTED SERVICES\PrintSpoolerService, SERVICE GPO “MSFT Windows 11 26H2 - Computer”
Path in the GPO console
Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment Local security policy
SeImpersonatePrivilege This setting has no registry key. It is stored in the local security database (LSA) and is configured through the Group Policy console or secpol.msc.
Description
Assigning this privilege to a user allows programs running on behalf of that user to impersonate a client. Requiring this user right for this kind of impersonation prevents an unauthorized user from convincing a client to connect (for example, by remote procedure call (RPC) or named pipes) to a service that they have created and then impersonating that client, which can elevate the unauthorized user's permissions to administrative or system levels. Caution Assigning this user right can be a security risk. Only assign this user right to trusted users. Default: Administrators Local Service Network Service Service Note: By default, services that are started by the Service Control Manager have the built-in Service group added to their access tokens. Component Object Model (COM) servers that are started by the COM infrastructure and that are configured to run under a specific account also have the Service group added to their access tokens. As a resul