2.2 Server Security Standard

2.2.1. Overview

Unsecured and vulnerable servers continue to be a major entry point for malicious threat actors.  Consistent Server installation policies, ownership and configuration management are all about doing the basics well.

2.2.2. Purpose

The purpose of this standard is to establish standards for the base configuration of internal server equipment that is owned and/or operated by Highline College. Effective implementation of this standard will minimize unauthorized access to Highline College proprietary information and technology.

2.2.3. Scope

All employees, contractors, consultants, temporary and other workers at Highline College and its subsidiaries must adhere to this standard. This standard applies to server equipment that is owned, operated, or leased by Highline College or registered under a Highline College-owned internal network domain.

2.2.4. Standard

2.2.4.1 General Requirements

2.2.4.1.1 All internal servers deployed at Highline College are managed by ITS Infrastructure Services which is responsible for system administration.

The following items must be met:

• Servers must be registered within the corporate enterprise management system. At a minimum, the following information is required to positively identify the point of contact:
  • Server contact(s) and location, and a backup contact
  • Hardware and Operating System/Version
  • Main functions and applications, if applicable
• Information in the corporate enterprise management system must be kept up-to-date.
• Configuration changes for production servers must follow the appropriate change management procedures

2.2.4.1.2 For security, compliance, and maintenance purposes, authorized personnel may monitor and audit equipment, systems, processes, and network traffic.

2.2.4.2 Configuration Requirements

2.2.4.2.1 Operating System configuration should be in accordance with Operating System Guideline.

2.2.4.2.2 Services and applications that will not be used must be disabled where practical.

2.2.4.2.3 Access to services should be logged and/or protected through access-control methods such as a web application firewall, if possible.

2.2.4.2.4 The most recent security patches must be installed on the system as soon as practical, the only exception being when immediate application would interfere with business requirements.

2.2.4.2.5 Trust relationships between systems are a security risk, and their use should be avoided. Do not use a trust relationship when some other method of communication is sufficient.

2.2.4.2.6 Always use standard security principles of least required access to perform a function. Do not use root when a non-privileged account will do.

2.2.4.2.7 If a methodology for secure channel connection is available (i.e., technically feasible), privileged access must be performed over secure channels, (e.g., encrypted network connections using SSH or IPSec).

2.2.4.2.8 Servers should be physically located in an access-controlled environment. See Physical Security Standard.

2.2.5. Compliance

2.2.5.1 Compliance Measurement

ITS will verify compliance to this standard through various methods, including but not limited to, periodic walk-thrus, video monitoring, business tool reports, internal and external audits, and feedback to the standard owner.

2.2.5.2 Exceptions

Any exception to the standard must be approved by ITS in advance.

2.2.5.3 Non-Compliance

An employee found to have violated this standard may be subject to disciplinary action, up to and including termination of employment.

2.2.6. Related Standards, Policies, and Processes

2.5 Operating System Guideline

1.7 Physical Security Standard

2.2.7. Revision History