|
Securing Desktop Workstations
Securing desktop workstations should be a significant part of your network and information-security strategy because of the sensitive information often stored on workstations and their connection to the rest of the networked world. Many security problems can be avoided if the workstations and network are appropriately configured. Default hardware and software configurations, however, are set by vendors who tend to emphasize features and functions more than security. Since vendors are not aware of your security needs, you must configure new workstations to reflect your security requirements and reconfigure them as your requirements change. The practices recommended here are designed to help you configure and deploy networked workstations that satisfy your organization's security requirements. The practices may also be useful in examining the configuration of previously deployed workstations. | ||
| ||
A note on terminology | The word "workstation" is used in this module to mean the
combination of the hardware, operating system, application software, and
network connection. When it is necessary to be more specific, we
explicitly mention one of those four components.
Although this module focuses on securing desktop workstations, many of the practices are also applicable to securing network servers or other computers on your network. To make it easier to include those practices in other modules, we use the word "computer" broadly; it can mean workstations, servers, or other computers. | |
| ||
Who should read these practices |
These practices are applicable to your organization if
We assume that you have the following security requirements for information resources stored on or accessed by users or processes on those workstations:
| |
| ||
What these practices do and do not cover |
These practices address security issues for desktop workstations within your organization. They do not attempt to address security issues for
Although many of the practices described here are applicable to these types of computers, we do not include other practices that are unique to them. These practices are limited to security issues related to configuring the workstation itself. We recognize that security of the workstation also depends on security of the network to which it is connected, and we plan to describe network security practices in subsequent modules. The focus of these practices is to help you establish an appropriate configuratin for a workstation when it is first deployed. They do not cover all security aspects of the day-to-day operations of a workstation, which we address in other modules. For example, activities related to detecting signs of intrusion on a desktop workstation are covered in the module Detecting Signs of Intrusion [Allen 00]. The practices do not include the initial setup of the workstation: unpacking it, confirming the hardware configuration, installing the default operating system, and making the network connection. However, some of the practices are most effective if performed during the process of installing the operating system. Finally, these practices do not address physical security of workstations in detail. | |
| ||
Security issues | There are three main security issues related to securing a
workstation:
| |
| ||
Security improvement approach |
To secure a desktop workstation, we recommend a four-part approach. It requires implementing security practices in the following areas:
The practices are designed to improve security in several ways:
| |
| ||
Summary of recommended practices | ||
|
Abbreviations used in these practices | ||
DNS | Domain Name Service | |
ftp | file transfer protocol | |
http | hypertext transfer protocol | |
IP | Internet Protocol | |
LAN | Local Area Network | |
NFS | Network File System | |
NIS | Network Information System | |
NTP | Network Time Protocol | |
smtp | simple mail transfer protocol | |
TCP | Transmission Control Protocol | |
WORM | Write Once, Read Many | |
WWW | World Wide Web | |
|
References | [Firth 97a] | Allen, Julia & Stoner, Ed. Detecting Signs of Intrusion. (CMU/SEI-SIM-009). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2000. Available at http://www.cert.org/security-improvement/modules/m09.html |
[Ford 99] | Ford, Gary, et al. Securing Network Servers. (CMU/SEI-SIM-007). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1999. Available at http://www.cert.org/security-improvement/modules/m10.html | |
[Kossakowski] | Kossakowski, Klaus-Peter, et al. Responding to Intrusions. (CMU/SEI-SIM-006). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 1999. Available at http://www.cert.org/security-improvement/modules/m06.html | |
| ||
| ||
Acknowledgements | This report and the effort to produce it were sponsored by the SEI primary sponsor, the U.S. Land Information Warfare Activity (LIWA) ACERT, and the U.S. Army Research Laboratory (ARL). |
Conditions for use, disclaimers, and sponsorship information can be found in http://www.cert.org/legal_stuff.html.
"CERT" and "CERT Coordination Center" are registered in the U.S. Patent and Trademark Office.
Any material furnished by Carnegie Mellon University and the Software Engineering Institute is furnished on an "as is" basis. Carnegie Mellon University makes no warranties of any kind, either expressed or implied as to any matter including, but not limited to, warranty of fitness for a particular purpose or merchantability, exclusivity or results obtained from use of the material. Carnegie Mellon University does not make any warranty of any kind with respect to freedom from patent, trademark, or copyright infringement.