(Approved by the Provost and Executive Vice President by authority of Executive Order No. 4, Senior Vice President for Finance and Facilities by authority of Executive Order No. 5, and the Vice President of UW Technology by authority of Executive Order No. 63)
The nature of the data largely determines what measures and operational practices need to be applied to protect it. To help clarify the various minimum requirements for UW data security, three categories of data have been defined. It is essential that those who are accountable for protecting the data (e.g., system owners and data custodians) understand and inventory their data assets according to these categories.
In most cases, it will be obvious how to categorize data. When in doubt about how a particular data element or set of data should be classified, the safe "rule of thumb" is to default to the higher classification of the choices involved. In other words, it is better to err on the side of privacy and security protection until clarification can be obtained.
For electronic information where the integrity of the data is important, but the data itself is classified as "Public" (e.g. UW financial business records), the source of the data — "the master data" (application, database, authorized data collection point, etc.) — should be treated as "Restricted" and the published versions of those data (e.g. reports) can be treated as "Public" data.
Any questions about the classification of data can be forwarded to the UW Chief Information Security Officer (CISO) for review by the PASS Council.
The table below clarifies the nature of each data category and provides criteria for determining which classification is appropriate for a particular set of data. When using this table, a positive response for the most restrictive (highest risk) category in any row is sufficient to place that set of data into that category.
| Confidential | Restricted | Public | |
| Legal Require- ments |
Protection of data is required by law. (See examples of specific HIPAA and FERPA data elements below.) |
UW has a contractual obligation or best practice (due care) reason to protect the data. |
|
| Risk Level |
High | Medium | Low |
| Examples of Risk |
The UW's reputation is tarnished by public reports of its failures to protect sensitive records of employees, students, or clients. |
Data is disclosed unnecessarily or in an untimely fashion, which causes harm to UW business interests or to the personal interests of an individual. |
Confusion is caused by corrupted information about enrollment and tuition that is displayed on the official UW website. |
| Examples of Specific Data |
|
|
|
1Health Insurance Portability and
Accountability Act (HIPAA) for the Human Subjects Division and Health Insurance Portability and Accountabiilty
Act (HIPAA) for UW Medicine
2Family Educational
Rights and Privacy Act (FERPA)
3Export Administration
Regulations (EAR) and International Traffic in Arms Regulations (ITAR)
4Gramm-Leach-Bliley Financial Services Modernization Act (GLB)
5UW Affirmative Action Data Collection