All University Data must be classified in accordance with the requirements of this policy. The appropriate classification for a collection of University Data will be based on the most sensitive information within the collection, even if the collection contains other information that would fall within a less sensitive classification if it were stored separately.
Data Owners are responsible for ensuring the proper classification and protection of all University Data that is under their control in accordance with University policy and all security safeguards required by University Information Security.
The classification of University Data will be based on how the data is used, its sensitivity to unauthorized disclosure, and any requirements imposed by external agencies or applicable laws. All University Data, except for Classified National Security Information and third-party owned Proprietary Data, must be classified under the following four levels of data sensitivity classification:
WSU Public Data generally has a very low sensitivity, but it still warrants protection since the integrity and protection of the data can be important. WSU Public Data is explicitly or implicitly approved for distribution to the public without restriction. Examples of WSU Public Data include, but are not limited to, the following:
WSU Campus Data is information that has a low level of sensitivity but is intended only for students, on-campus industry partners, University personnel, and Controlled Affiliated Organizations. Examples of WSU Campus Data include, but are not limited to, the following:
WSU Private Data is information that has low to moderate sensitivity and that is intended for internal University business use only, with access restricted to a specific workgroup, department, group of individuals, or affiliates with a legitimate need to use or access the information. Unauthorized disclosure could adversely impact the University, Controlled Affiliate Organizations, third parties, or individuals. Examples of WSU Private Data include, but are not limited to, the following:
WSU Restricted Data is highly sensitive information maintained, collected, or recorded by WSU that is intended for limited, specific use by a workgroup, department, group of individuals, or third party (typically pursuant to a contract or agreement) with a legitimate need to use or access the data. Explicit authorization by the designated Data Owner is required for access to WSU Restricted Data because of legal, contractual, privacy, or other constraints. Unauthorized disclosure could have a serious adverse impact on the business or research functions of the University, affiliates, or external parties and violate the personal privacy of individuals, federal or state laws and regulations, or contractual obligations of the University. Examples of WSU Restricted Data include, but are not limited to, the following:
Any classification and security standards for Proprietary Data that is owned by a third party, such as an individual, corporation, or government agency, will be specified by the third-party owner. The following are examples of proprietary data:
Any classification and security standards for data classified by the federal government as CNSI will be specified by the federal government in accordance with the National Industrial Security Program Operating Manual (32 CFR Part 117).
University Data may be governed by state and/or federal laws, regulations, executive orders, guidance, or other policies. Data Owners must ensure compliance not only with University policies and all security safeguards required by University Information Security, but also with any state and/or federal requirements that govern the University Data for which they are responsible. The following are some examples of University Data that are subject to additional requirements:
University Data must be protected in accordance with this policy and all security safeguards as required by the University Information Security department, and in accordance with all governing state and federal requirements. All University Data shall follow the concepts of Least Privilege and Need to Know.
Data with the highest risk requires the greatest level of protection to prevent compromise, whereas data with lower risk requires proportionately less protection. University Data may fall within multiple classification schemes. For instance, research data and non-sensitive PII could span across all four classifications. The level of protection required for research data and non-sensitive PII is dependent upon the entities who create, store, process or transfer it and the contractual agreements, laws, or regulations that govern those entities.
A University department, division, or unit that operates and is responsible for its own information technology system is required to follow the security safeguards required by University Information Security, unless University Information Security has expressly approved department-specific written security safeguards that address the safeguards for University Data within that department. Any department-specific security safeguards must comply with this policy.
Contracts between the University and third parties involving University Data must include language requiring compliance with all applicable laws, regulations, and University policies related to data and information security. If University Data is used or disclosed in any manner other than allowed by the contract the University General Counsel office must be notified immediately.
This is a new policy.
19.20 / Data Sensitivity Classification
Information Security and Chief Data Officer
The State of Kansas requires that all State agencies classify data based upon the sensitivity of the information. This policy provides the criteria and classification levels for all University data. This is also a federal requirement for protecting information under NIST 800-171/CMMC for NIAR, in addition to providing protections to the University.
This policy has been created to ensure compliance with state and federal requirements for data classification and protection and to address audit findings related thereto.
October 22, 2024