Skip to main content
CUI

Vulnerability V-254496

Back

V-254496

CAT I

Windows Server 2022 create a token object user right must not be assigned to any groups or accounts.

Ships Affected
1
Total Findings
1
Open
0
Closed
1

Check Text

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. For server core installations, run the following command: Secedit /Export /Areas User_Rights /cfg c:\path\filename.txt Review the text file. If any SIDs are granted the "SeCreateTokenPrivilege" 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 Information System Security Officer (ISSO). The application account must meet requirements for application account passwords, such as length (WN22-00-000050) and required frequency of changes (WN22-00-000060). 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).

STIG Reference

STIG
Microsoft Windows Server 2022 Security Technical Implementation Guide
Version
2
Release
8
Rule ID
SV-254496r958726_rule

All Occurrences

This vulnerability appears on 1 ship(s)

Ship Hull # Source File Status Assigned To Scan Date Actions
LAB BASELINES BASELINE SCHR-P3-DP-001_WinServer2022_V2R7_20260305-133436.cklb
Unassigned 2026-03-05T13:34:36 View in Context
CUI