Gold University of Minnesota M. Skip to main content.University of Minnesota.
Driven to Discover.

What's Inside OIT



links related to OIT

University of Minnesota

STANDARDS & GUIDELINES



     

GUIDELINE—Critical Server Identification (Appendix O)


Responsible Office: Office of Information Technology
Responsible Officer: Chief Information Officer

EFFECTIVE DATE: February 2001
VIEW HISTORY
RELATED POLICY/PROCEDURE:

Securing Private Data Standard

GUIDELINE
A guideline is highly recommended.


Introduction

Identifying critical servers is an important part of the University's ongoing risk management and operational improvement initiatives, and is also related to our compliance obligations. OIT Security will work with departments to provide routine vulnerability scans and on a priority basis will consult with your technology staff to further improve security measures. It is important that computer and data owners identify critical servers. If in doubt, include the server.

For this purpose, a server is a multi-user computer, which provides some service for other computers connected to it via a network. The most common examples are departmental/collegiate file servers, web servers, mail servers, and database servers. A "critical" server is important to accomplishing the University/collegiate unit/business unit mission or one which stores legally protected or other important non-public data.

Note: Servers that store legally protected data are required to be identified by following the implementation steps below.

Critical servers meet at least one of the following criteria:

A. Data Criteria:

  1. Stores health information on individuals
  2. Stores nonpublic student data
  3. Stores nonpublic employee data
  4. Stores other legally protected, contractually protected or nonpublic data

B. Level of impact if server unavailable:

  1. University-wide
  2. Campus or Collegiate Unit
  3. Department
  4. Other important mission-related functions

C. Other Criteria:

  1. Important software applications
  2. Large number of users
  3. Potential large financial liability, including grants and contracts
  4. Impact upon reputation of the University

To learn more about nonpublic data or data legally protected by HIPAA Privacy or legally protected Student data, see http://www.ahc.umn.edu/privacy/what/home.html

Implementation

To assist with collecting information on critical servers, the following can be used for tracking:

Units should include the IP addresses for the critical servers in their "Critical" asset group in Qualys.  See Critical Server Scan Process.

Questions, send e-mail to oit.security@umn.edu

Resources and Links