| Introduction | |
| Before You Begin | |
| Securing Your Domain Controllers | |
| Enabling Additional Services on Domain Controllers | |
| Keeping Your Domain Controllers Secure | |
| Related Information |
The loss of data or revenue that can result from a malicious attack on a computer system can be devastating to an organization. To protect your company's computer systems and data from the ever present threat of malicious code used in worms, viruses, and malicious attacks, it is critical that you implement security measures to help reduce the exposure to your company's assets.
The domain controllers in your network are the centerpiece of your Active Directory directory service. They contain all of your user account information, without which, users cannot log on to your network and access the resources that they need to perform their jobs.
Because of the information that domain controllers contain and their critical role in any environment, they are obvious targets of malicious attacks. For this reason, you should place your domain controllers in the most secure location possible; you should keep your domain controllers up-to-date with the latest security updates; and you should disable unnecessary services to minimize their exposure to worm, virus, and malicious attacks.
This guide provides step-by-step guidance to help you implement security measures that will help lock down the configuration of your domain controllers.
To improve the security of your environment, you will apply Group Policy, which is the change and configuration management technology included with Active Directory. This guide leads you through the following tasks:
| • | Securing your domain controllers by using Group Policy. |
| • | Configuring Group Policy to provide for additional domain controller functionality. |
| • | Keeping your domain controllers up-to-date with the latest security updates. |
Note: Configuring Group Policy on your domain controllers is only the first step toward enhancing the security of your domain controllers and your entire environment.
Review and complete the tasks in "Securing Windows 2000 Professional Clients in a Windows Server Environment" and "Securing Windows XP Professional Clients in a Windows Server Environment" of the Security Guidance Kit. Completing the tasks in these guides will greatly contribute to enhancing the security of your domain controllers.
After you complete these tasks, your domain controllers will contain a base level of security that can help protect your environment from a large number of security threats. Completing these tasks ensures that domain controllers run only the services they need to provide for your environment. Furthermore, configuring Automatic Updates helps you keep your domain controllers up-to-date by automatically downloading and installing the latest security updates as Microsoft releases them.
IMPORTANT: All the step-by-step instructions included in this document were developed by using the Start menu that appears by default when you install your operating system. If you have modified your Start menu, the steps might differ slightly.
To complete the tasks in this guide, you must be logged on to your domain controller as a member of the Domain Admins account. Keep in mind that some steps require you to restart your domain controller; so make sure you complete these steps during non-business hours to minimize the impact to your users.
This guide assumes that your client environment consists of computers running Microsoft Windows 2000 Service Pack 2 (SP2) or later, and Windows XP SP1. Several of the tasks and recommendations detailed in this guide are not compatible with older versions of Windows.
If your computers do not have these service packs installed or if you are unsure whether they are installed, go to the Windows Update page on the Microsoft Web site http://go.microsoft.com/fwlink/?LinkID=22630 and have it scan your systems for updates. If service packs show up as an available update, you should install them before proceeding with the tasks in this document. More information about using Windows Update is provided later in this document.
You can improve security on your domain controllers by using Group Policy. The following steps show you how to configure Group Policy to disable unnecessary or unused services on your domain controllers that might otherwise create unwanted exposure if left enabled. To configure Group Policy for your domain controllers, complete the following tasks:
| • | Create a new Group Policy object (GPO), and link it to the Domain Controllers organizational unit (OU). |
| • | Import baseline security settings into the new GPO by using the security template that is included with this guide. |
| • | Verify your new settings by reviewing the Application log on your domain controllers. |
You need to complete the following steps just one time. The security of all of your domain controllers is enhanced simultaneously after you configure the Domain Controllers Baseline Policy.
IMPORTANT: You must restart all your domain controllers for the Domain Controllers Baseline Policy to take effect. Make sure to complete these steps during non-business hours to minimize the impact to your users.
Requirements
| • | Credentials: You must be logged on as a member of the Domain Admins group. |
| • | Tools: Active Directory Users and Computers. |
| • | Files: You need to download the MSS DCBaseline Role.inf file included with the Securing Windows 2000 Server Guide. After downloading this file, copy it to the systemroot\Security\Templates folder of the domain controller on which you are performing these steps. (For example, in a typical configuration, you would copy the .inf file to the C:\Windows\Security\Templates folder.) |
| • | To download the MSS DCBaseline Role.inf file
|
| • | To create a new GPO in the Domain Controllers OU
|
| • | To import the baseline security settings into the Domain Controllers Baseline Policy
|
After configuring the Group Policy security settings, be sure to verify that the policies have been applied successfully.
Requirements
| • | Credentials: You must be logged on as a member of the Domain Admins group. |
| • | Tools: Event Viewer and Services. |
Verify that the Application log on each of your domain controllers contains an Event ID 1704.
| • | To check the Application event log
|
Next, verify that unnecessary services are disabled on your domain controllers.
| • | To check for disabled services
|
The Domain Controllers Baseline Policy that you implemented in the previous section disables several services that are not used to provide base domain controller functionality. Making this configuration change greatly enhances the security of your domain controllers; however, the change prevents certain services, which domain controllers typically provide in small and medium businesses, from operating properly.
The following steps show you how to modify your Group Policy in order to re-enable these additional services. Review the following tasks, and complete them on your domain controllers only if your network requires the additional functionality that is provided by these services:
| • | Enabling DHCP services |
| • | Enabling WINS services |
| • | Enabling Print services |
| • | Enabling Certificate services |
| • | Enabling IAS services |
| • | Enabling and securing the Task Scheduler service |
If your domain controller is configured as a Dynamic Host Configuration Protocol (DHCP) server, you need to modify Group Policy settings for the domain controller to provide DHCP services to your environment. This section provides step-by-step instructions for configuring Group Policy in order to re-enable the DHCP service.
You must edit the Domain Controllers Baseline Policy to re-enable the DHCP Server service on your domain controllers. Following these steps enables the DHCP Server service on all domain controllers that provide DHCP services.
Requirements
| • | Credentials: You must be logged on as a member of the Domain Admins group. |
| • | Consider impact to users: You will need to restart your domain controllers to complete these steps. You should complete these steps during non-business hours to minimize the impact to your users. |
| • | To configure Group Policy to enable DHCP services
|
After you modify your Group Policy settings to enable the DHCP Server service, verify that the service is running.
| • | To verify that the DHCP Server service is running
|
IMPORTANT: Also verify that client computers are obtaining DHCP server IP addresses from your domain controller.
If your domain controller is configured as a Windows Internet Name Service (WINS) server, you need to modify Group Policy settings for your domain controller to provide WINS services to your environment. This section provides step-by-step instructions for configuring Group Policy to re-enable the WINS service.
You must edit the Domain Controllers Baseline Policy Group Policy object to enable the WINS service on your domain controllers. Following these steps enables the WINS service on all of your domain controllers.
Requirements
| • | Credentials: You must be logged on as a member of the Domain Admins group. |
| • | Consider impact to users: You will need to restart your domain controllers to complete these steps. You should complete these steps during non-business hours to minimize the impact to your users. |
| • | To edit Group Policy to enable the WINS service
|
After you modify your Group Policy settings to enable the WINS service, verify that the service is running.
| • | To verify that WINS is running
|
Access to file shares on your domain controller is not affected by the Domain Controllers Baseline Policy that you implemented in the previous sections. No modifications are necessary for your domain controllers to provide secure file-sharing services.
However, if your domain controller is configured as a Print server, you need to configure Group Policy to enable the Print Spooler service for your domain controller to provide Print services to your environment.
You must edit the Domain Controllers Baseline Policy Group Policy object to enable the Print Spooler service on your domain controllers. Following these steps enables the Print Spooler service on all of your domain controllers.
Requirements
| • | Credentials: You must be logged on as a member of the Domain Admins group. |
| • | Consider impact to users: You will need to restart your domain controllers to complete these steps. You should complete these steps during non-business hours to minimize the impact to your users. |
| • | To configure Group Policy to enable print services on your domain controller
|
After you modify your Group Policy settings to enable the Print Spooler service, verify that the service is running.
| • | To verify that the Print Spooler service is running
|
IMPORTANT: Also verify that client computers can print to the printer shares on your domain controllers.
If any of your domain controllers is configured as an Internet Authentication Service (IAS) server, you need to modify Group Policy settings for the domain controller to provide IAS services to your environment. This section provides step-by-step instructions for configuring Group Policy to re-enable IAS services.
You must edit the Domain Controllers Baseline Policy to re-enable IAS services on your domain controllers. Following these steps enables Certificate Services on all domain controllers that provide IAS services.
Requirements
| • | Credentials: You must be logged on as a member of the Domain Admins group. |
| • | Consider impact to users: You will need to restart your domain controllers to complete these steps. You should complete these steps during non-business hours to minimize the impact to your users. |
| • | To configure Group Policy to enable IAS services
|
After you modify your Group Policy settings to enable IAS services, verify that the service is running.
| • | To verify the IAS service is running
|
If any of your domain controllers is configured as a certification authority (CA) server, you need to modify Group Policy settings for the domain controller to provide Certificate Services to your environment. This section provides step-by-step instructions for configuring Group Policy to re-enable Certificate Services.
You must edit the Domain Controllers Baseline Policy to re-enable Certificate Services on your domain controllers. Following these steps enables Certificate Services on all domain controllers that provide Certificate Services.
Requirements
| • | Credentials: You must be logged on as a member of the Domain Admins group. |
| • | Consider impact to users: You will need to restart your domain controllers to complete these steps. You should complete these steps during non-business hours to minimize the impact to your users. |
| • | To configure Group Policy to enable Certificate Services
|
After you modify your Group Policy settings to enable Certificate Services, verify that the service is running.
| • | To verify that Certificate Services is running
|
If any of your domain controllers use scheduled tasks to automatically run scripts or programs, you need to modify Group Policy settings for the domain controller to run the Task Scheduler service.
To help improve the security of your domain controllers, after you re-enable the Task Scheduler service, restrict any tasks that are scheduled using AT commands from using the Local System account. If you maintain the default account configuration, your domain controllers are open to attacks by malicious users.
This section provides the following step-by-step instructions:
| • | Configuring Group Policy to enable Task Scheduler. |
| • | Securing the Task Scheduler service by modifying the AT Service Account. |
You must edit the Domain Controllers Baseline Policy GPO to enable the Task Scheduler service on your domain controllers. Following these steps enables the Task Scheduler service on all of your domain controllers.
Requirements
| • | Credentials: You must be logged on as a member of the Domain Admins group. |
| • | Consider impact to users: You will need to restart your domain controllers to complete these steps. Rebooting all your domain controllers simultaneously might temporarily prevent users from logging on to the network or accessing network resources. To minimize the impact on your users, you should complete these steps during non-business hours. |
| • | To configure Group Policy to enable Task Scheduler on your domain controllers
|
After you modify your Group Policy settings to enable the Task Scheduler service, verify that the service is running.
| • | To verify that the Task Scheduler service is running
|
You can also use AT commands to schedule tasks in Task Scheduler. By default, tasks that you schedule by using AT commands run under the Local System account and run regardless of which user is logged on to the computer. Often, these tasks run in the background and are unnoticed by administrators.
The Local System account is a special, predefined account that is used to start and run many services on your domain controllers. This account allows full access to your domain controllers and also has access to network resources. Hence, many security-related attacks try to exploit services that run by using the Local System account.
To help improve the security of your domain controllers, you can limit a malicious user's ability to run programs that use the Local System account. This guide recommends that you modify the configuration of Task Scheduler so that any tasks that are scheduled using AT commands do not run using the Local System account.
After you complete the following steps, any tasks that are scheduled by using AT commands only run using the account that you specify.
Requirements
| • | Credentials: You must be logged on as a member of the Domain Admins group. |
| • | Repeat these steps: You must complete these steps on each one of your domain controllers. |
| • | To modify the AT Service Account configuration
|
To keep your domain controllers up-to-date, you must routinely download and install the latest Microsoft security updates. These updates are provided to help resolve known issues and to help protect your computer from known security vulnerabilities.
The following steps provide you with automatic and manual methods for keeping your domain controllers up-to-date with available security updates. You will complete the following tasks:
| • | Configure Automatic Updates to automatically download and install security updates on the schedule you specify. |
| • | Review how to use Windows Update to manually download and install security updates. |
IMPORTANT: You should keep all computers on your network up-to-date with the latest security updates. Configuring Automatic Updates and using Windows Update on your domain controllers will keep only your domain controllers up-to-date. Make sure that Automatic Updates and Windows Update are configured and used with all the computers on your network that are running Windows 2000, Microsoft Windows Server 2003, and Windows XP.
You can configure your Windows 2000 domain controllers to automatically download and install the latest Microsoft security updates while your computer is turned on and connected to the Internet.
Requirements
| • | Credentials: You must be logged on as a member of the Domain Admins group. |
| • | Repeat these steps: You must complete these steps on each of your domain controllers. |
| • | To configure your domain controllers to automatically download and install security updates
|
Windows Update is the online extension of Windows that helps you keep computers connected to the Internet up-to-date. You can run Windows Update to ensure that Automatic Updates has installed all the latest security updates. Windows Update is useful if Microsoft notifies you of a new security issue and you want to immediately ensure that your computers are up-to-date.
Requirements
| • | Credentials: You must be logged on as a member of the Server Operators group or Domain Admins group. |
| • | Repeat these steps: You must complete these steps on each of your domain controllers. |
| • | To run Windows Update to manually download and install security updates
|
Note: Security updates often require that you restart your domain controller. When running Windows Update, be sure to consider the impact that restarting your domain controllers can have on your users.
For more information about securing Windows 2000, see the following:
| • | Microsoft Security Web site on the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkId=102. |
| • | Authoritative Security Guidance for the Enterprise on the TechNet Web site at http://go.microsoft.com/fwlink/?LinkId=22698. |
| • | Microsoft Guide to Security Patch Management on the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkId=16286. |
For more information about Windows 2000, see the following:
| • | Windows 2000 Home page on the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkId=4297. |
| • | Windows 2000 Group Policy white paper on the Microsoft Web site at http://go.microsoft.com/fwlink/?LinkId=203. |