mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-13 22:07:22 +00:00
Merge pull request #2960 from MaratMussabekov/882
Update create-global-objects.md, issue #882
This commit is contained in:
commit
73434c7140
@ -89,16 +89,6 @@ By default, members of the **Administrators** group, the System account, and ser
|
||||
|
||||
When non-administrators need to access a server using Remote Desktop, add the users to the **Remote Desktop Users** group rather than assining them this user right.
|
||||
|
||||
### Vulnerability
|
||||
|
||||
>**Caution:** A user account that is given this user right has complete control over the system, and it can lead to the system being compromised. We highly recommend that you do not assign this right to any user accounts.
|
||||
|
||||
Windows examines a user's access token to determine the level of the user's privileges. Access tokens are built when users log on to the local device or connect to a remote device over a network. When you revoke a privilege, the change is immediately recorded, but the change is not reflected in the user's access token until the next time the user logs on or connects. Users with the ability to create or modify tokens can change the level of access for any currently logged on account. They could escalate their privileges or create a denial-of-service (DoS) condition.
|
||||
|
||||
### Countermeasure
|
||||
|
||||
Do not assign the **Create a token object** user right to any users. Processes that require this user right should use the Local System account, which already includes it, instead of a separate user account with this user right assigned.
|
||||
|
||||
### Potential impact
|
||||
|
||||
None. Not Defined is the default domain policy configuration.
|
||||
|
Loading…
x
Reference in New Issue
Block a user