Act as part of the operating system
Applies To: Windows Vista, Windows Server 2008, Windows 7, Windows 8.1, Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2012, Windows 8
This security policy reference topic for the IT professional describes the best practices, location, values, policy management, and security considerations for this policy setting.
Reference
The Act as part of the operating system policy setting determines whether a process can assume the identity of any user and thereby gain access to the resources that the user is authorized to access. Typically, only low-level authentication services require this user right. Potential access is not limited to what is associated with the user by default. The calling process may request that arbitrary additional privileges be added to the access token. The calling process may also build an access token that does not provide a primary identity for auditing in the system event logs.
This policy setting is supported on versions of Windows that are designated in the Applies To list at the beginning of this topic.
Constant: SeTcbPrivilege
Possible values
User-defined list of accounts
Not defined
Best practices
Do not assign this right to any user accounts. Only assign this user right to trusted users.
If a service requires this user right, configure the service to log on by using the local System account, which inherently includes this user right. Do not create a separate account and assign this user right to it.
Location
\Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment
Default values
The following table lists the actual and effective default policy values for the most recent supported versions of Windows. Default values are also listed on the policy’s property page.
Server type or GPO |
Default value |
|---|---|
Default domain policy |
Not defined |
Default domain controller policy |
Not defined |
Stand-alone server default settings |
Not defined |
Domain controller effective default settings |
Not defined |
Member server effective default settings |
Not defined |
Client computer effective default settings |
Not defined |
Operating system version differences
This setting was introduced with Windows Vista and Windows Server 2008. There are no differences in the way this policy setting works between the supported versions of Windows that are designated in the Applies To list at the beginning of this topic.
Policy management
A restart of the computer is not required for this policy setting to be effective.
Any change to the user rights assignment for an account becomes effective the next time the owner of the account logs on.
Group Policy
Settings are applied in the following order through a Group Policy Object (GPO), which will overwrite settings on the local computer at the next Group Policy update:
Local policy settings
Site policy settings
Domain policy settings
OU policy settings
When a local setting is greyed out, it indicates that a GPO currently controls that setting.
Security considerations
This section describes how an attacker might exploit a feature or its configuration, how to implement the countermeasure, and the possible negative consequences of countermeasure implementation.
Vulnerability
The Act as part of the operating system user right is extremely powerful. Users with this user right can take complete control of the computer and erase evidence of their activities.
Countermeasure
Restrict the Act as part of the operating system user right to as few accounts as possible—it should not even be assigned to the Administrators group under typical circumstances. When a service requires this user right, configure the service to log on with the Local System account, which inherently inlcudes this privilege. Do not create a separate account and assign this user right to it.
Potential impact
There should be little or no impact because the Act as part of the operating system user right is rarely needed by any accounts other than the Local System account.