Statement of Policy
Washington University in St. Louis (WashU) is committed to conducting all university activities in compliance with all applicable laws, regulations, and university policies. WashU has adopted this policy to outline the security measures required to protect electronic information systems and related equipment from unauthorized use.
Objective
The policy and associated guidance provide a common methodology and organized approach to Information Security risk management whether based on regulatory compliance requirement or a threat to the university.
Applicability
This policy is applicable for all WashU information, infrastructure, network segments, and devices.
Audience
The audience for this policy is all WashU faculty, staff, and students. It also applies for all other agents of the university with access to WashU information and network for contracted services. This includes, but not limited to partners, affiliates, contractors, temporary employees, trainees, guests, and volunteers. The titles will be referred collectively hereafter as “WashU community”.
Roles & Responsibilities
Policy
The Office of Information Security (OIS) will develop and maintain an Information Security Risk Management Process to frame, assess, respond, and monitor risk. Guidance for this process will be based on the International Organization for Standardization, ISO27001, ISO27005, ISO31000 frameworks and specific security regulations (e.g. HIPAA, PCI-DSS, FERPA, etc.). The risk management process will be designed to assist WashU maintain compliance with regulatory requirements, federal, state, and local laws. Refer to the Information Security Risk Management Process for instructions.
Risk management will involve the entire WashU community. The OIS will engage with our stakeholders, departments and schools to increase awareness and communication of risk and to identify methods to integrate risk management in university culture, events, projects, processes, strategic, and operational planning. Expectations for WashU community will be open, clear, and transparent.
The OIS will identify, categorize, prioritize, and report risks based on the probability and potential impact to the environment if confidentiality, availability, and/or integrity is compromised. The risk evaluation will be uniform and consistent for WashU departments and schools. Dependencies for departments and schools will also be included in the risk evaluation.
Risk Register
The Risk Register is currently comprised of a series of unrelated spreadsheets across a combination of administrative and academic units and risk types. The purpose of the risk register is to consolidate all information about risk into a central repository. This allows risk management participants to use a single resource to obtain the status of the risk management process.
The Chief Information Security Officer (CISO) is responsible for maintaining the risk register.
The risk register shall comprise the following minimum components:
Date: |
The date that risks are identified or modified. Optional dates to include are the target and completion dates. |
Risk Number: |
A unique identifying number for the risk. |
Assessment ID: |
Unique Identifier from risk assessment reports that identified the risk. |
Risk Description: |
A brief description of the risk, its causes, and its impact. |
Existing Controls: |
A brief description of the controls that are currently in place for the risk. |
Consequence: |
The consequence (severity or impact) for the risk. |
Risk Ranking: |
A priority list which is determined by the relative ranking of the risks by their qualitative risk score. |
Risk Mitigation Strategy: |
The action which is to be taken to reduce the risk. |
Risk Owner: |
The person who has the responsibility for the risk, manages the risk mitigation efforts, and the risk response if the risk occurs. |
Risk Management Roles and Responsibilities
Roles |
Responsibilities |
Board of Directors Audit Committee |
|
Executive Leadership |
|
CIO |
|
CISO |
|
Information Security Office (ISO) |
|
Internal Audit |
|
School & Departmental Stakeholders |
|
WashU Community Members |
|
Reporting
The ISO will use a risk log or register to assist with documenting the identified risks and their status.
The CISO will deliver a risk management report annually to the Board of Directors Audit Committee. The report will provide a view of the strategic and operational risks identified and any steps taken to mitigate the risk.
Response
The appropriate university response will be based upon identified risk tolerance levels – remediate, mitigate, transfer, accept, or avoid. Plans will be developed and response to the risk will be assigned to the department or school to take the steps to reduce risk to an acceptable level. Cooperation from all departments or schools will be required to reduce risk in the WashU environment. These steps will be monitored, tracked in the risk register, tested, and reported to senior leadership.
Risk Management Performance
Performance will be identified and measured by:
- The reduction or risks reported quarterly.
- Completion and reporting of reviews.
- Compliance with regulation.
- Information Security incidents that are investigated and analyzed for risk resulting in the appropriate response or controls implemented.
- Risk assessments completed for all university events and projects.
Policy Compliance
The OIS will measure the compliance to this policy through various methods, including, but not limited to – reports, internal/external audits, and feedback to the policy owner. Exceptions to the policy must be approved by the OIS in advance. Non-compliance will be addressed with management, Area Specific Compliance Office, Human Resources, or the Office of Student Conduct.
Related Policies
None
Reference
Risk Management Plan
Risk Assessment Process
Policy Review
This policy will be reviewed at a minimum every three years.
Title: Information Security Risk Management Policy
Version Number: 3.0
Reference Number: RA-01.01
Creation Date: November 27, 2007
Approved By: Security and Privacy Governance Committee
Approval Date: December 6, 2016
Status: Final
Scheduled Review Date: March 1, 2016
Revision Date: February 26, 2019
Revision Approval Date: March 15, 2019
Policy Owner: Office of Information Security