|Platform: win10||Date: (C)2016-09-23 (M)2017-10-18|
Log on as a service
This policy setting allows accounts to launch network services or to register a process as a service running on the system. This user right should be restricted on any computer in a high security environment, but because many applications may require this privilege, it should be carefully evaluated and tested before configuring it in an enterprise environment. On Windows Vista-based computers, no users or groups have this privilege by default.
When configuring a user right in the SCM enter a comma delimited list of accounts. Accounts can be either local or located in Active Directory, they can be groups, users, or computers.
The default set of security principals that have the Log on as a service user right is restricted to Local System, Local Service, and Network Service, all of which are built-in local accounts. You should minimize the number of other accounts that have this user right.
On most computers, this is the default configuration and there will be no negative impact. However, if you have installed optional components such as ASP.NET or IIS, you may need to assign the Log on as a service user right to additional accounts that are required by those components. IIS requires that this user right be explicitly granted to the ASPNET user account.
(1) GPO: Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Log on as a service
(2) REG: ###
(3) WMI: root\rsop\computer
UserRight='SeServiceLogonRight' and precedence=1
|SCAP Repo OVAL Definition||oval:org.secpod.oval:def:36502|