Server Hardening Standard
Purpose - The UTSA Server Hardening Standard document
describes the requirements for installing a new server in a secure
fashion and maintaining the security and integrity of the server and
application software.
Audience - The UTSA Server Hardening Standard
applies to all individuals who are responsible for the installation of
new information resources that will be connected to the UTSA network,
the operations of existing information resources and individuals
charged with information resource security. |
-
A server must not be connected to the UTSA network
until it is secure and the network connection has been activated. This includes:
-
Internet traffic
-
Electronic mail traffic
-
LAN traffic, protocols and device
inventory
-
Operating system security
parameters
-
Rogue access points/devices
-
Installed software on servers and
desktops
-
In order to harden a server, follow these general
steps:
-
Install the operating system from
a source approved by the Office of Information Technology (OIT)
-
Apply vendor-supplied patches to
keep software properly updated
-
Remove unnecessary software,
system services and drivers
-
Set security parameters and file
protections; enable audit logging
-
Disable or change the password of
default accounts
-
UTSA OIT will monitor security issues (both
internal and external to UTSA) and will manage the testing and
application of patches to affected UTSA core systems managed by OIT.
-
Security patches must be implemented within a reasonable
timeframe after their release date. UTSA OIT will make periodic
announcements of required patches.
-
The server must run legally licensed versions of the operating
system and software.
-
The server must run only necessary services. All unnecessary
services should be shut down.
-
After the administrator determines what default accounts are
required on a server, all other default accounts must be disabled.
-
The server may not function as a relay for SMTP or other means
of relaying non-UTSA related mail; it may not function as an FTP
server or Web server without written approval from OIT.
-
The server must comply with all other IR security policies and
standards.
-
Servers must authenticate all users using
industry-standard procedures to ensure only authorized access to the
resource.
|
|