Detections
Analytics

2.2.25 Configure 'Impersonate a client after authentication'

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

The policy setting allows programs that run on behalf of a user to impersonate that user (or another specified account) so that they can act on behalf of the user. If this user right is required for this kind of impersonation, an unauthorized user will not be able to convince a client to connect--for example, by remote procedure call (RPC) or named pipes--to a service that they have created to impersonate that client, which could elevate the unauthorized user's permissions to administrative or system levels.

Services that are started by the Service Control Manager have the built-in Service group added by default to their access tokens. COM servers that are started by the COM infrastructure and configured to run under a specific account also have the Service group added to their access tokens. As a result, these processes are assigned this user right when they are started.

Also, a user can impersonate an access token if any of the following conditions exist:
- The access token that is being impersonated is for this user.
- The user, in this logon session, logged on to the network with explicit credentials to create the access token.
- The requested level is less than Impersonate, such as Anonymous or Identify.

An attacker with the Impersonate a client after authentication user right could create a service, trick a client to make them connect to the service, and then impersonate that client to elevate the attacker's level of access to that of the client.

- Level 1 - Domain Controller. The recommended state for this setting is: ''Administrators, LOCAL SERVICE, NETWORK SERVICE, SERVICE''.
- Level 1 - Member Server. The recommended state for this setting is: 'Administrators, LOCAL SERVICE, NETWORK SERVICE, SERVICE' and (when the _Web Server (IIS)_ Role with _Web Services_ Role Service is installed) 'IIS_IUSRS'.

Note: This user right is considered a 'sensitive privilege' for the purposes of auditing.

Note #2: A Member Server with Microsoft SQL Server _and_ its optional 'Integration Services' component installed will require a special exception to this recommendation for additional SQL-generated entries to be granted this user right.

Rationale:
An attacker with the Impersonate a client after authentication user right could create a service, trick a client to make them connect to the service, and then impersonate that client to elevate the attacker's level of access to that of the client.

Solution

To establish the recommended configuration via GP, configure the following UI path:


Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Impersonate a client after authentication


Impact:
In most cases this configuration will have no impact. If you have installed the _Web Server (IIS)_ Role with _Web Services_ Role Service, you will need to also assign the user right to 'IIS_IUSRS'.

See Also

https://workbench.cisecurity.org/files/1937

Item Details

Category: ACCESS CONTROL

References: 800-53|AC-6(7), CSCv6|5.1

Plugin: Windows

Control ID: 2bf9e4d5d3b2cca294854f4e0584d021831af7a9a4e79dc4b1d9e0abb23527c5