|
POLICY ON
COMPROMISED SERVERS
The primary concern in such a situation is to prevent the
compromised machine from doing additional damage, either to its own
system and files, or to the rest of our network. The second priority,
also of urgency, is to restore the compromised machine to
functionality in a timely manner.
The recommended procedure for dealing with a compromised system is:
- Determination that a server has been compromised ("hacked"):
- By the user: Report the incident to the MSIS office if you
believe that your system may have been hacked. MSIS can
implement additional monitoring of your system.
- By MSIS: The School of Medicine network operator monitors the
network for unusual network traffic that can
indicate that a computer has been compromised. In the event that such
behavior has been detected, MSIS will notify the responsible operator
of the computer to discuss the problem.
- If the MSIS Network Supervisor determines that computer has been
compromised, he is empowered to disconnect the
system from the network.
- Initially request that the system owner unplug or disable the
network adaptor on the system.
- If the system owner is unreachable, block that system's network
communications. This can be done via firewall, router or
physical disconnection from the network.
- If the owner is unresponsive, block the system's network
communications.
- If applicable, backup important data. The owner is
responsible for system backups and MSIS cannot assure data
protection. MSIS will attempt to perform an emergency backup of
the system.
- Reinstall the OS from original media.
- Change root password and all other user passwords. This can
be performed by the system owner with the assistance of MSIS.
- Apply security measures to prevent future break-ins.
- Rebuild or restore applications and data.
- When the MSIS Network Supervisor determines that computer has
been repaired, he will reconnect the system to the network.
- MSIS will attempt to assist in the installation of other
applications but provides no guarantee of success. It is highly
recommended that the system owner maintain software support for any
special applications.
Approved by the Faculty Information Technology Committee, January
8, 2002, and ratified by the Executive Committee of the Faculty Senate on
January 10, 2002
|