UCF Server Security Standards

The purpose of this document is to establish standards for the base configuration of UCF servers. Effective implementation of these standards will minimize unauthorized access to UCF proprietary information and technology.These standards apply to servers (see definition below) owned and/or operated by UCF, and to servers registered under any UCF internal network domain.

Ownership and Responsibilities

  • All servers deployed at UCF must be registered with Network Services (https://my.noc.ucf.edu) in compliance with the Use Information Technology and Resources Policy 4-002. At a minimum, the following information is required to positively identify the point of contact:
    • Primary Administrator (full-time staff) contact and location
    • Backup Administrator contact and location
    • Hardware and Operating System/Version
    • Main functions and applications
    • Services running
    • Services you are requesting from the Internet
  • Information on registered servers must be kept up-to-date on above Network Services site, including but not all: change of services, change of administrators.
  • If a server is no longer in service, the server manager should delete its entry from the Network Services site.

General Configuration Guidelines

  • Operating System configuration should be in accordance  the University’s Computer Security Standards.
  • Services and applications that will not be used must be disabled.
  • Access to services should be protected, and if possible logged, through access-control methods such as Windows firewall or TCP Wrappers.
  • 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.
  • Always use standard security principles of least required access to perform a function.
  • Do not use root or administrator when a non-privileged account will do.
  • 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).
  • Servers should be physically located in an access-controlled environment.
  • Servers are specifically prohibited from operating from uncontrolled cubicle areas.

Monitoring

  • All security-related events on critical or sensitive systems must be logged and audit trails saved as follows:
  • All security related logs will be kept online for a minimum of 6 months.
  • Data backup and retention should be in accordance with the IT Security Policy.
  • Security-related events will be reported to Network Services/Computer Services, who will review logs and report incidents to IT management. Corrective measures will be prescribed as needed. Security-related events include, but are not limited to:
  • Port-scan attacks
  • Evidence of unauthorized access to privileged accounts
  • Anomalous occurrences that are not related to specific applications on the host.

Compliance

  • Network Services Security Team will perform audits on a regular basis.
  • Every effort will be made to prevent audits from causing operational failures or disruptions.

Definitions

Term Definition
Server Server is defined as a system that provides services (such as; file, web, shell access, PC Anywhere, etc. ) to other systems. Desktop systems are not considered servers unless it has services running as mentioned above.
Services Service is an application type that runs in the background and is similar to UNIX daemon application. Service applications typically provide features such as client/server applications, Web servers, database servers, FTP servers, and other server-based applications to users, both locally and across the network.