The mark of a great security administrator has been said to be the ability to successfully balance the security of propriety and personal data with the usability of the system in a way that maximizes the productivity of the organization–none of which is as easy as it may sound.
Fortunately, in Windows Server 2003, many of the security features that were either optional or suspect in earlier Windows operating systems have become solid and effective, making it the most secure operating system Microsoft has ever produced, and thereby facilitating the job of the security administrator. That is, if you know how to configure it properly.
The “Windows Server 2003 Security Cookbook” provides recipes for more than 250 of the security tasks that an administrator is likely to deal with in a Windows Server 2003 network. Each recipe starts with a brief description of the task or problem, followed by one or more step-by-step solutions and a discussion of the expected results, along with caveats and alternative approaches. Up to five solutions are presented for each recipe–from menu-drive, command-line, and scripting solutions to Registry and Group Policy approaches – to give administrators flexibility in choosing how to perform any given task.
Recipes in the 21 chapters are sorted by task domain or system service, topics includes: Encrypting File System; Active Directory and Group Policy; IIS; DNS and DHCP; Patch management; Security templates; Auditing and event logs.
The book assumes a basic knowledge of Windows Server 2003 and how it works, and that the reader performs security tasks as one of his or her primary job functions. As Mike Danseglio and Robbie Allen said, “We wrote these recipes to get right to the technical details, so we do not expect a novice or someone unfamiliar with Windows to be totally comfortable with our writing style.”