Topics Map > Do-IT Yourself > Security

Resolving Risks to the Rice University Network

This page explains the Responsibility of Owners to resolve risks to Rice networks by their systems and the steps involved in doing so.

The Information Security Office (ISO) works with the campus to identify risks to University systems and data.  If you have been identified as the owner (or responsible party) of a system with at least one vulnerability that introduces potential risk to Rice University, you are required to do one or more of the following:

  • Remediate (resolve) the risk
  • Mitigate the risk (minimize it through controls) 
  • Request a temporary acceptance of risk for that system (approved by the CIO for Rice University) 
Any vulnerable system that has been identified as a risk to the university is subject to removal from the network until such time as the risk can be addressed. There will be a grace period for each system, defined by the level of severity of the vulnerability. The grace period will be communicated to you by the Information Security Office or the Office of Information Technology, allowing the risk to be addressed before the system is removed from the network.

Remediation

In the majority of cases, a vulnerability can be resolved by applying a patch or series of patches, usually provided by the operating system or application vendor (i.e. Microsoft, Apple, Adobe, etc.) or simply updating the operating system or application to its latest version.  Work with your OIT representatives or the helpdesk if you have concerns or questions about how to do this.  

Mitigation

In some cases, patching or updating a system can be problematic for a variety of reasons. If this situation applies to you, OIT and ISO recommend that you attempt to mitigate the vulnerability by taking one or more of the following actions, which will minimize the risk to the university, and then request a temporary exception. This will allow your system to remain on the network for a time while you attempt to address the risk to the university. 

Mitigation or compensating controls:

  • Implement third party support agreements for extended hardware or software support
  • Disallow remote access to the system
  • Relocate research data, personally identifiable information (PII), financial or other critical data to a more secure system
  • Reduce and/or remove all services not specifically required by the core function of the system (such as SMB, FTP, and RDP)
  • Upgrade all required service software to current versions
  • Discontinue using the system for normal user-based operations (such as web browsing and email clients)
  • Remove user applications not required for primary function (personal user apps, i.e. email browsers)
  • Restrict access to the system by using host-based firewall configurations to limit access to mission critical functions
  • Restrict outbound access to only critical local sites
  • Restrict user access to the system
  • Disable or remove file sharing services
  • Disable USB support on the device
  • Enable multi-factor authentication for system access
  • Ensure that the system is configured with centralized management controls and end point management solutions (i.e. MSAD, JAMF, RH Satellite)
  • Install antivirus and anti-malware software that is updated regularly
  • Review systems configurations with professional OIT staff regularly
  • Remove or disable unused local credentials and back doors

As always, OIT and the ISO will work with you to evaluate and apply controls that address your specific issue. 

NOTE: Mitigation controls are always temporary and eventually the system will need to be resolved or removed from the network.

Conditional Exception Request

Should you feel that you require an exemption from having your system or systems removed from the network, you may initiate a Conditional Exception Request, which will go to the CIO for review and approval.  You will have 30 days to complete this process or the vulnerable system may be removed from the network. The Conditional Exception Request Form is attached here. Please review the form before requesting an exception.

To be able to request an exception, the following criteria must be met:

  • System cannot be compromised or publicly accessible (contain viruses, malware, or command and control software or have a public IP address).          
  • System cannot have access to or contain Rice confidential or sensitive data  (email, FERPA  data, ePHI/PII, financial or research data, unrestricted file services).      
  • System must have a defined Owner and Steward.       
  • System / Service must be critical to Rice University or Department operations.     

Process Steps:

1. Form is sent to the identified "Form Filler" in AdobeSign. This is the person who will provide the relevant system information, purpose of the system, justification for requesting an exception, and a remediation plan to resolve the issue.
2. Form is sent back to ISO staff for review and assignment of a severity risk level.
3. Form is then sent to the Owner for signature.
4. Form is then sent to the ISO Management and the CIO for review and approval. 

The ISO and OIT are committed to assisting you with resolving vulnerabilities to Rice University. Thank you for helping us maintain a culture of security here at Rice!








Keywords:conditional exception request, mitigate, remediate, risk, vulnerability, vulnerable, system vulnerablesystem   Doc ID:102964
Owner:JoAnna P.Group:Rice University
Created:2020-06-10 17:19 CDTUpdated:2020-08-21 15:28 CDT
Sites:Rice Sandbox, Rice University
CleanURL:https://kb.rice.edu/vulnerablesystem
Feedback:  0   0