CERT Coordination Center
HomeSite IndexSearchContactFrequently Asked Questions
Incidents, Quick fixes, and VulnerabilitiesSecurity Practices and EvaluationsSurvivability Research and AnalysisTraining and Education
 
    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

  • you operate or plan to operate a network that includes desktop workstations

  • users of those workstations have network access to hosts inside your organization and to hosts outside through common Internet protocols

We assume that you have the following security requirements for information resources stored on or accessed by users or processes on those workstations:

  • Some or all of the information is sensitive or proprietary. Access must be limited to authorized and properly authenticated users (inside or outside your organization).

  • The integrity of that information is critical. It must not be compromised; that is, not modified by unauthorized users or processes operating on their behalf.

  • That information must be readily accessible by authorized users whenever they need it to perform their work.


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

  • portable workstations and laptop computers

  • workstations at geographically remote sites that may connect to your site through the Internet or public telephone networks

  • desktop machines that operate as network servers

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:

  1. Confidentiality - Information stored on the workstation may be disclosed inappropriately. This can happen when
    • unauthorized users gain access to the workstation
    • authorized users gain access to information that they are not supposed to see
    • authorized users inappropriately transmit information via the network
  2. Integrity - The integrity of information stored on the workstation may be changed, either accidentally or maliciously.
  3. Availability - Authorized users may be unable to use the workstation, the network, or the information and services stored on each to perform their jobs. This can result when
    • the information has been damaged, deleted, or otherwise rendered inaccessible (such as being encrypted or having its access privileges changed)
    • the computational resources of the workstation have been damaged or overloaded to the point of preventing authorized users' work
    • access to services has been denied


Security improvement approach  

To secure a desktop workstation, we recommend a four-part approach. It requires implementing security practices in the following areas:

  1. planning and executing the deployment of workstations
  2. configuring workstations to prevent security incidents
  3. maintaining the integrity of the deployed workstation
  4. improving user awareness of security issues

The practices are designed to improve security in several ways:

  • They promote consistency. When the configuration and deployment of workstations is consistent, it is easier to manage security and to predict or identify use outside the norm.

  • They help to maximize security on each workstation. This provides vital protection in case of failure of perimeter defenses. Host security is also a first-line of defense against internal threats, which generally have a higher probability of occurrence than external threats via the network.

  • They help you recognize security incidents sooner, help prepare you to recover from security breaches, and prevent similar breaches from recurring. As a result, you can reduce damages from security incidents.


Summary of recommended practices  
Area Recommended Practice
Planning deployment

1. Develop a computer deployment plan that includes security issues

Configuring workstations

2. Keep operating systems and applications software up to date

3. Configure computers for user authentication

4. Configure computer operating systems with appropriate object, device, and file access controls

5. Identify data that characterize systems and aid in detecting signs of suspicious behavior

6. Manage logging and other data collection mechanisms

7. Configure computers for file backups

8. Protect computers from viruses and similar programmed threats

9. Configure computers for secure remote administration

10. Configure computers to provide only selected network services

11. Configure network service clients to enhance security

12. Configure multiple computers using a tested model configuration and a secure replication procedure

Maintaining workstation integrity

13. Allow only appropriate physical access to computers

Improving user awareness

14. Develop and promulgate an acceptable use policy for workstations


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).
Last updated April 20, 2001
Copyright 1999, 2000, 2001, 2002 Carnegie Mellon University.

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.


Use of any trademarks in this report is not intended in any way to infringe on the rights of the trademark holder.


NO WARRANTY

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.