The Create a token object user right must not be assigned to any groups or accounts.

From Windows Server 2016 Security Technical Implementation Guide

Associated with: CCI-002235

SV-88411r1_rule The Create a token object user right must not be assigned to any groups or accounts.

Vulnerability discussion

Inappropriate granting of user rights can provide system, administrative, and other high-level capabilities.The "Create a token object" user right allows a process to create an access token. This could be used to provide elevated rights and compromise a system.

Check content

Verify the effective setting in Local Group Policy Editor. Run "gpedit.msc". Navigate to Local Computer Policy >> Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment. If any accounts or groups are granted the "Create a token object" user right, this is a finding. If an application requires this user right, this would not be a finding. Vendor documentation must support the requirement for having the user right. The requirement must be documented with the ISSO. The application account must meet requirements for application account passwords, such as length (WN16-00-000060) and required frequency of changes (WN16-00-000070). Passwords for application accounts with this user right must be protected as highly privileged accounts.

Fix text

Configure the policy value for Computer Configuration >> Windows Settings >> Security Settings >> Local Policies >> User Rights Assignment >> "Create a token object" to be defined but containing no entries (blank).

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.