Details
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.
Rationale:
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.
Solution
To establish the recommended configuration via GP, set the following UI path to include Guests:
Computer ConfigurationPoliciesWindows SettingsSecurity SettingsLocal PoliciesUser Rights AssignmentDeny log on as a service
Impact:
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.
Default Value:
No one.
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Access Control.This control applies to the following type of system Windows.