Security in C#.NET

Paint QR Code in C#.NET Security

Root Directory Permissions (Rootsec.inf)

By default, the Rootsec.inf template specifies the new permissions, introduced in Windows XP Professional, for the root of the system drive. This template can be used to reapply the default root directory permissions if they are inadvertently changed. In addition, the template can be used to apply the same root permissions to other volumes. Note

This template does not overwrite explicit ACEs defined on child objects. It propagates only the permissions that are inherited by child objects.

Setup Security (Setup security.inf)

Setup security is a computer-specific template that represents the default security settings applied during installation of the operating system, including the file permissions for the root of the system drive. This template, or portions thereof, can be used for disaster recovery purposes. Setup security.inf replaces the combination of Basic.inf and Ocfiles.inf that existed in versions of Windows earlier than Windows XP Professional. Setup security.inf should not be applied by using Group Policy.

No Terminal Server SID (Notssid.inf)

The default file system and registry ACLs on servers grant permissions to a Terminal Server SID. The Terminal Server SID is used only when Terminal Server is running in application compatibility mode. If Terminal Server is not in use, this template can be applied to remove the unnecessary Terminal Server SID from these file system and registry locations. Removing the ACE for the Terminal Server SID does not, however, increase the security of the system. Therefore, instead of removing the Terminal Server SID, it is recommended that you run Terminal Server in full security mode rather than application compatibility mode. When Terminal Server is running in full security mode, the Terminal Server SID is not used.

To view and implement security policy on a local computer, you must have Administrator rights to the computer. Administrators can use the following Windows XP Professional tools to view and configure security policy settings:

Local Security Policy. This Group Policy snap-in can be used to configure security settings on individual computers. The Local Security Policy snap-in can be used to configure Account Policies, Audit Policies, User Rights, and numerous other security options. Security Settings extension to Group Policy. This Group Policy snap-in can be used to establish security policies for domains or organizational units (OUs). The Group Policy snap-in can be used to configure the same settings that Local Security Policy configures, as well as Event Log settings, Restricted Groups, System Services, file ACLs, and registry ACLs.

17:

Security Templates snap-in. This is a stand-alone Microsoft Management Console snapin that can be used to create a text-based template file that contains security settings for all security areas. The security templates snap-in can be used to configure Account Policies, Local Policies, Event Log settings, Restricted Groups, System Services, registry settings, and File System settings. Security Configuration and Analysis snap-in. This is a stand-alone MMC snap-in that can configure or analyze Windows XP Professional operating system security. Its operation is based on the contents of a security template that was created by using the Security Templates snap-in. Secedit.exe. This is a command-line version of the Security Configuration and Analysis snap-in. It allows security configuration and analysis to be performed without a graphical user interface (GUI).

You can use the following procedure to view the security policy settings on a computer running Windows XP Professional. To view Local Security Policy settings

In Control Panel, click Performance and Maintenance, click Administrative Tools, and then double-click Local Security Policy.

The Local Security Settings snap-in is illustrated in Figure 17-7. You can also view the Local Security Settings container from the command line.

Figure 17-7

Part III: