Introduction
The purpose of this document is to introduce the set of standards that are required to adhere to for the operation within the University at Albany's network. This document is not designed to be all-encompassing, but provides general requirements.
Server Definition
A server can be virtual or physical, that offers services to other network systems. This includes networked printers, mobile devices, desktops, laptops, virtual machines, and Internet of Things (IoT). Each server must be actively administered by a system administrator who must adhere with these standards. Servers found to pose an active threat to University assets will be subject to remediation steps as determined by the Information Security Office (ISO).
Virtual System Definition and Standards
Virtual system has the same standards as the physical systems. The caveat here is that virtual systems need to have further considerations on risk management.
- Access to the hypervisor is strictly restricted. Virtualization software, such as hypervisors, represents a layer of privileged software that can be attacked and therefore must be protected.
- The potential loss of separation of duties for administrative tasks can lead to a breakdown of the defense in-depth approach. Role definition and separation of duties must be properly planned for in a virtual environment.
- Patching, signature updates, and protection from tampering for production, as well as offline, VM and VM appliance images needs to be accounted for.
- Virtualization can result in limited visibility into the host operating system and virtual network to find vulnerabilities and assess system configurations (e.g., file integrity checking, log inspection).
- Likewise, virtualization can limit the view of inter-VM traffic for inspection by Intrusion Detection Systems (IDS) and Intrusion Prevention Systems (IPS).
- Security tools for virtual environments may not provide the same level of visibility and protection as they do for physical systems.
- Business processes and policies must be applied when defining the organizational roles and responsibilities for processes and authorities within the virtualized environment.
UAlbany Network Server Standards
- The server must be registered in the NetReg with ownership and contact information provided. Servers must be labeled or identified as a server in Netreg.
- The server must be managed by at least one system administrator.
- The server must be running a supported operating system as well as the latest approved patch.
- Patches must be evaluated and applied in a timely fashion by the system administrator.
- The server must be configured in a secure manner.
- If the server holds Category 1 data, it must meet all applicable regulatory requirements. Learn more about the University's Data Classification Standard.
- Only properly licensed software must be run on the server.
- The server or service must not interfere with any UAlbany Enterprise services (e.g., DHCP, DNS).
- The network services provided by the server must be configured to be accessible from the minimum set of systems and networks as determined by the server's business or academic requirements.
- The system administrator must continuously monitor and remediate any security issues. The University provides Tenable Vulnerability Management as a solution. Learn more about the University's Vulnerability Management. For more information on vulnerability management, please contact the ITS Service Desk.
Process of Requesting a Connection to the UAlbany Network
The process of requesting a connection to the UAlbany network usually involves submitting a ticket through footprints to the network services team. In this ticket you must specify what server and how many, the type of connections you need (one management copper, two data uplink fiber, DAC, etc). You also need to include the VLAN you need to be connected to for various connections.
Prepping a Server for the UAlbany Network
- Verify that the computing needs are not already met by existing UAlbany ITS or departmental servers.
- Assign a system administrator team to setup, maintain, and monitor the server.
- Take appropriate precautions during the installation of a server and/or software.
- Consider the physical environment and access of the server in regard to security.
- Install a supported version of the OS and service(s).
- Perform and validate backups and archives.
- Enable logging for server(s) and service(s).
- Disable default accounts and sample scripts; change any default passwords.
- Only activate/operate needed services. Any unnecessary ports and services turned on by default must be disabled.
- Restrict network access.
- Setup secure methods of authentication.
- Configure administrator level accounts to be compliant with the University's Privileged Access Standard.
- Employ file integrity checks on system and configuration files.
- Designate your server as a server system in NetReg by indicating it so in the comment box.
Prepping a Virtual System for the UAlbany Network
When considering virtualization, it's crucial to address risks associated with software layers like hypervisors and the nuances of virtual environments, such as patch management and visibility issues. The same number of steps are applied as if it was a physical server.
Maintaining UAlbany Server Services and Security
- Review service logs and backup logs regularly.
- Periodically review running services and evaluate the continued needs for those service(s) and server(s).
- Keep abreast of security issues and patches of product.
- Apply vendor/community provided updates regularly for the OS and applications.
- Regularly monitor and maintain all user accounts.
- Maintain current registration information in NetReg.
- Manage the server End-of-Life processes appropriately.
Last Review: February 2024