Designing Security by Server Role
A user right that determines the users that can connect to a computer over the network. Used by
A user right to adjust memory available to a process. In the wrong hands, it can cause a denial of service attack, as too much memory is used by a single process and none or little is available for others. The guide recommends High Security restrict this right to Administrators, NETWORK SERVICE, LOCAL SERVICE.
A user can attach a debugger to a process or to the kernel, providing access to sensitive operating system components. Debugging shouldn’t be occur?ring on a production computer. Revoke for all security groups and accounts. No one should have this privilege.
By default, this setting is not defined in other templates and the member server default is Administrators, NETWORK SERVICE, LOCAL SERVICE. The reason for repeating this information in the template is to be able to reapply the
This is a good place to restrict access to only those who need it, depending on computer role. Use the High Security recommendation, and make other deci?sions in the incremental templates. Restricting access further here might cause problems, especially if few server roles really need restrictions.
By default, this setting is not defined in other templates and the member server default is Administrators, NETWORK SERVICE, LOCAL SERVICE. The reason for repeating this information in the template is to be able to reapply the defaults. If an administrator granted this right to other users, thus making an attack or misuse more likely to succeed, a GPO that uses this template will maintain the defaults. This is a good use of templates, and you might consider using this strategy to protect other critical security settings.
There have been cases where a user with this right was able to elevate his privileges to administrator and thus take over a computer. Note how the template removes a right that could prove dangerous in the wrong hands a right that is not necessary anyway in a