|Platform: win10||Date: (C)2016-09-23 (M)2017-10-18|
This policy setting determines which user accounts will have the right to attach a debugger to any process or to the kernel, which provides complete access to sensitive and critical operating system components. Developers who are debugging their own applications do not need to be assigned this user right; however, developers who are debugging new system components will need it.
Note: Microsoft released several security updates in October 2003 that used a version of Update.exe that required the administrator to have the Debug programs user right. Administrators who did not have this user right were unable to install these security updates until they reconfigured their user rights. This is not typical behavior for operating system updates. For more information, see Knowledge Base article 830846: 'Windows Product Updates may stop responding or may use most or all the CPU resources.'
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."
Remove the accounts of all users and groups that do not require the Debug programs user right.
If you revoke this user right, no one will be able to debug programs. However, typical circumstances rarely require this capability on production computers. If a problem arises that requires an application to be debugged on a production server, you can move the server to a different OU temporarily and assign the Debug programs user right to a separate Group Policy for that OU.
(1) GPO: Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Debug programs
(2) REG: ###
(3) WMI: root\rsop\computer
UserRight='SeDebugPrivilege' and precedence=1
|SCAP Repo OVAL Definition||oval:org.secpod.oval:def:36494|