2.2.29 Ensure 'Deny log on as a service' to include 'No one' (STIG DC only)


This security setting determines which service accounts are prevented from registering a process as a service. This user right supersedes the Log on as a service user right if an account is subject to both policies.

The recommended state for this setting is to include: Guests.

Note: This security setting does not apply to the System, Local Service, or Network Service accounts.

Note #2: The CIS recommended state for this setting is: Guests, which differs from the STIG recommended state.


Accounts that can log on as a service could be used to configure and start new unauthorized services, such as a keylogger or other malicious software. The benefit of the specified countermeasure is somewhat reduced by the fact that only users with administrative privileges can install and configure services, and an attacker who has already attained that level of access could configure the service to run with the System account.


If you assign the Deny log on as a service user right to specific accounts, services may not be able to start and a DoS condition could result.


To establish the recommended configuration via GP, set the following UI path to include Guests:

Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Deny log on as a service

Default Value:

No one.

Additional Information:

Microsoft Windows Server 2019 Security Technical Implementation Guide:
Version 2, Release 1, Benchmark Date: November 13, 2020

Vul ID: V-205669
Rule ID: SV-205669r569188_rule
STIG ID: WN19-DC-000390
Severity: CAT II

See Also