TABLE OF CONTENTS | 1.1 | Configure security for servers that are assigned specific roles. |
| 1.2 | Plan security for servers that are assigned specific roles. Roles might include domain controllers, Web servers, and mail servers. |
| 1.2.1 | Deploy the security configuration for servers that are assigned specific roles. |
| 1.2.2 | Create custom security templates based on server roles. |
| 4.3 | Plan security for data transmission. |
| 4.3.1 | Secure data transmission between client computers to meet security requirements. |
| 4.3.2 | Secure data transmission by using IPSec. |
| 5.3 | Plan a framework for planning and implementing security. |
| 5.3.1 | Plan for security monitoring. |
| 5.3.2 | Plan a change and configuration management framework for security. |
| 5.4 | Plan a security update infrastructure. Tools might include Microsoft Baseline Security Analyzer and Microsoft Software Update Services. |
It probably goes without saying that IT security is currently a hot topic and will continue to be important for some time to come. Most network and security administrators have discovered that security isn't a static condition but rather is constantly flowing and morphing in scope. At this juncture, it is not unusual to find that new security vulnerabilities are identified and patches for those vulnerabilities are released on what might seem a daily basis. A fix that you applied two weeks ago might not cover 10 or 15 issues that have come up since that day.
Although you will never have a 100 percent secure environment, that doesn't mean that you can't take steps to protect yourself from would-be intruders. Working with...
