لطفا منتظر باشید ...
Chapter 11. Additional Security Issues and Solutions
The previous two chapters examined permissions, the Public Key Infrastructure, and user authentication as aspects of securing a Windows Server 2003 system or domain. Although these are the cornerstones of Windows Server security, a variety of other security issues and solutions must be discussed.This chapter rounds out the discussion of Windows Server security. First we examine the snap-in tools for security management. Then we look at how to secure the computer systems primarily against internal abuses. Finally we turn our attention to securing the Windows Server 2003 environment against external intrusions over the network.Security breaches compromise protocols, services, permission settings, readable network data, downloadable components, and e-mail messages. Practically every feature on the operating system can be used against it, which is why it must be secured against outside "crackers," or criminal hackers.Protecting against malicious outside attack is only one aspect of a totally secure program. Authorized users are also the cause of purposeful or inadvertent data destruction or even system crashes. A proper framework must include control over hardware and file system access, data archiving and restoration, and data transmission.Security vulnerabilities can result in a number of crippling results. The user is denied service when a system is crashed, damaged, or taxed so that it cannot perform intended duties. Data corruption can cost both time and money. The invasion of privacy through improper sniffing or other forms of intrusion can result in the loss of confidential information. A common hacker practice known as spoofing permits an unauthorized user to pretend to be another person or service. Finally, physical security breaches can result in the theft of equipment or sensitive data. In this chapter, we identify these issues in greater detail and suggest both commonsense and specific Windows Server 2003 solutions.
