What is a Process Level Token?
Every program running on a system needs specific permissions to access files, networks and other resources. A process level token acts as an ID for each program determining what it is allowed to do and access on the system. Tokens are critical for certain Windows functionalities, such as Task Scheduler, which uses this privilege to manage processes on behalf of different users.
What Does Replacing a Process Level Token Mean?
This Windows security setting allows token levels to be changed either by the user or another program, whilst the program is already running. Additionally it allows one process or service (the parent process) to start another process or service (the child process) with a different access token, including the permission to also change the second program’s token. This is done via the CreateProcessAsUser() API.
The Importance of Correct Configuration
This setting allows a program to change its access levels. This could allow for a program to escalate its own privileges to gain access to unauthorized data or parts of a system, leading to security risks.
As well as changing permissions, this setting can also be used to start a process as another user whose credentials are known. Imitating another user’s credentials can be used to cover up unauthorized actions.
How to Configure Replace a Process Level Token
To establish the recommended configuration via GP, set the following UI path to LOCAL SERVICE, NETWORK SERVICE:
| Computer ConfigurationPoliciesWindows SettingsSecurity SettingsLocal PoliciesUser Rights AssignmentReplace a process level token |
Or, to configure via Windows Settings use the following path:
| Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesUser Rights Assignment |
Default value
LOCAL SERVICE, NETWORK SERVICE.
Recommended settings
The recommended state for this setting is: LOCAL SERVICE, NETWORK SERVICE.
Best Practices
Incorporating server hardening practices is vital for enhancing system security. Server hardening involves configuring the server to minimize vulnerabilities by reducing the attack surface. This includes limiting privileges like replace a process level token, applying security patches, disabling unnecessary services, and enforcing strong authentication mechanisms.
By combining these practices with strict monitoring and regular reviews of sensitive privileges, organizations can better protect their systems against potential threats and ensure a robust security posture. The integration of these measures not only enhances security but also allows IT teams to focus on more critical tasks, knowing that their systems are well-protected.
