University Policies and Procedures Manual (previously Business Policies and Procedures Manual)

UPPM 87.23

For more information contact:
   Information Technology Services

---

1.0 Overview and Purpose

1.1 Information Assurance Policies Generally

The purposes of the information assurance policies in UPPM Chapter 87: Information Technology and Security are to:

• Set requirements to ensure the privacy, confidentiality, integrity, and availability of Washington State University (WSU) data;
• Support institutional goals and strategies with appropriate methods for administratively, technically, and operationally protecting data; and
• Define the criteria WSU follows to meet requirements for protecting data, which are determined by Information Owners.

The policies in this chapter comply with Federal Information Processing Standards (FIPS 199), which are intended to help organizations achieve a common level of quality and interoperability in information technology (IT) by requiring categorization of systems as low-impact, moderate-impact, or high-impact for the stated security objectives of confidentiality, integrity, and availability.

To determine the potential consequence of a loss event, the Federal Information Processing Standards:

• Define WSU Information Owners’ impact categorization rating (Low, Moderate, or High);
• Dictate which security controls are mandatory based upon the categorization level;
• Define the strength, frequency, and formalization of those controls; and
• Influence audit burden and continuous monitoring rigor.

See UPPM 87.01 for definitions, general information, and violations related to this policy, as well as additional information regarding roles and responsibilities.

1.2 Specific Policy Overview and Purpose

The policies in Chapter 87: Information Technology and Security set forth requirements intended to protect WSU’s technology resources and institutional data. However, WSU recognizes there may be exceptional circumstances in which adherence to established policies and/or standards could inadvertently hinder critical academic, scholarly, outreach, or operational activities.

This policy sets forth requirements for requesting a temporary exception from a WSU information security policy or standard. By allowing limited exceptions, WSU supports its goals of facilitating innovation and operational efficiency while safeguarding data and technology resources.

2.0 Applicability

This policy applies to all WSU system users who have contact with, or potentially may have contact with, WSU data, applications, and computing resources.

Security control exceptions to policy statements in UPPM Chapter 87 are managed and maintained in accordance with UPPM 87.23.

3.0 Roles and Responsibilities

3.1 Chief Information Officer

The Chief Information Officer (CIO) of WSU, or designee, is responsible for administering this policy and reviewing it on an annual basis.

3.2 Information System Owners

Information System Owners, or their delegates, are responsible and accountable for developing appropriate Standard Operating Procedures (SOPs) for this policy’s implementation. 

3.3 Office of Information Security and Assurance (OISA)

WSU’s Office of Information Security and Assurance (OISA) shall maintain the standard (PDF) associated with this policy and provide guidance for the associated procedures for the implementation of this policy (see examples (PDF)).

Note: While all units are required to adhere to the standard established by OISA (NIST SP 800-53), procedural examples for implementation are optional.

4.0 Requirements

If an Information System Owner, or delegate, cannot comply with a WSU information security policy or standard statement, a completed Control Exception request must be submitted to the Office of Information Security and Assurance (OISA).

Exceptions are to be documented and approved in a Plan of Action and Milestones (POA&M) in accordance with the WSU Control Exception Process before it is considered a valid exception.

WSU Information System Owners, or their delegates, must coordinate and work with Information Owners, or their delegates, to determine the risk associated with policy variance in accordance with UPPM 87.25.

Information System Owners, or their delegates, must submit the completed and approved Control Exception package to OISA for monitoring and reporting in accordance with UPPM 87.25.

Information Owner(s) and Information System Owner(s), or their delegates, must review Control Exceptions annually and submit an updated Control Exception package to the OISA for monitoring and reporting in accordance with UPPM 87.25.

5.0 Training

See UPPM 87.21 for training requirements related to UPPM Chapter 87.

In addition to the requirements in UPPM 87.21, Information System Owners are responsible for ensuring that users receive appropriate information security and privacy training commensurate with their roles, responsibilities, and authorized access to information systems under the Information System Owner’s authority.

_______________________
Revisions: Feb. 2026 (Rev. 651 – NEW).