Please consider downloading the latest version of Internet Explorer
to experience this site as intended.
Tools Search Main Menu

Data Security Classifications

We are proposing changing the current data security classifications to tie more closely to the risk associated with unapproved access or inappropriate use of University data. We welcome comments on the following updated policy; please contact the Data Governance and Support Office.

Proposed Data Security Classification Policy

SCOPE: This policy applies to all information handled in the course of university business, including but not limited to education, research, healthcare, and administration. For purposes of this policy, information is defined as any points of data however recorded in any medium including information about the information (meta data) and regardless of the actions (e.g. use, access, storage, management) or origination (e.g. created, collected, received, contracted).

PURPOSE: Define the classifications of data, appropriate handling, and the required security controls associated with the data classification to establish consistency across the organization, including the University of Rochester, University of Rochester Medical Center, and affiliates.

This policy is not intended to supersede the law but is intended to be the governing rule for instances not covered by legal statute, subject to the following exceptions [TBD.]

PRINCIPLE: Enable the sharing of data as broadly as possible subject to legal and regulatory restrictions and following University security and privacy policies and standards.

DATA CLASSIFICATIONS: University information will be classified based on the risk posed to the University by inappropriate access, use, or handling of those data. 

Data should be treated at the highest classification of any data element contained within the system, collection, or set. If you have a question on the classification of data, please contact an Information Security Officer or Privacy Officer.

HIGH RISK

Definition: Data are classified as High Risk when protection of such data is required by law or regulation, protection is necessary in order for the University or its affiliates to meet compliance obligations, or the unauthorized disclosure, access, alteration, loss or destruction of those data could have a material impact on the University or its affiliates’ mission, assets, operations, finances, or reputation, or could pose material harm to individuals.

Examples: Examples include, but are not limited to, occurrences of personally-identifiable information (PII) such as social security numbers (SSNs), protected health information (PHI), payment card information (PCI), employee background investigations, employee immunization information, student information protected by FERPA, special categories of personal data identified by GDPR, as well as records and supporting materials of internal investigations performed to meet policy, regulatory, or legal requirements. In addition, any data the University receives that are contractually restricted, including research data, should be considered High Risk. For some industry sponsored research, the raw data may be considered high risk but the results can be more broadly shared.

Access and use: Access to High Risk information must be carefully safe-guarded. High Risk information must be stored, used, and disclosed to those who have a documented business need and who have followed the appropriate access management procedure. Such procedures may require special training, data use agreements, or other documentation. Protection of High Risk information is the responsibility of everyone who is granted access or uses such data.

Alternatives to using High Risk Information should be identified and used whenever possible.

Specific University policies may apply to particular data in this classification, e.g., Secure Handling of Social Security Numbers, Security of Electronic Protected Health Information, Information, protected by FERPA, etc.  See Appendix B for related policies.

High Risk information must be protected even if the data are allowed to be shared outside the University.  Disclosure of High Risk Information to a third party agent or vendor is permitted only if the agent or vendor assumes a legally binding obligation to safe-guard the use and disclosure of the information.

Storage and Protection: High Risk Information in paper form must be stored in locked or otherwise secured areas when not in active use. High Risk Information in electronic form must be stored in secure designated data centers or, if authorized to be stored elsewhere, only in encrypted (or similarly protected) form. It must not be stored on desktop, laptop or other portable devices or media without encryption or similar protection. High Risk data stored, processed, or managed by vendors or other third parties must also be similarly protected. Contact an Information Security Officer or a Privacy Officer for advice and assistance.

Transmission: Reports and communications should not include High Risk Information unless essential to perform the function for which the communication is made. Transmission of High Risk data must be by secure methods. If High Risk data are transmitted by e-mail or other electronic transmission, they must be encrypted or otherwise adequately protected. The electronic exchange of High Risk Information outside of the University of Rochester must have proper approval and follow documented procedures.

Labeling of High Risk Information: Information that is classified as High Risk should be clearly labeled as such. It is a best practice to provide such a label to warn others clearly that this information is High Risk and should be treated accordingly.

Destruction: When a record containing High Risk information is no longer needed according to record retention guidelines, it must be disposed of in a manner that makes the High Risk data no longer readable or recoverable. Destruction of paper records containing High Risk data normally should be accomplished by shredding. Destruction of electronic records containing High Risk data begins with deleting the data from its storage location(s), i.e. from all systems and devices including email, trash, backup, and file storage.

Reporting Unauthorized Disclosure of High Risk Information: Prompt reporting of unauthorized disclosure of High Risk Information is essential for the University to meets its obligations under law, regulation, and contract. The University will not take disciplinary action against any person solely because of his or her good faith reporting of a disclosure. Individuals who report violations of this Policy will be protected from retaliation resulting from providing information. Individuals who report violations of this Policy to the Hotline can remain anonymous.

MODERATE RISK

Definition: Much information necessary for people to perform their work at the University is properly available to others at the University but is not appropriate to be known by the general public. Data should be classified as Moderate Risk where the unauthorized disclosure, access, alteration, loss or destruction of those data would be expected to have an adverse but not material impact on the University and its affiliates’ mission, assets, operations, finances, or reputation, or only limited harm to individuals. This information is made available to members of the University community with a business need and is not restricted by local, state, national, or international statute regarding disclosure or use.

Examples: Examples include, but are not limited to, budgets, strategic or unit business plans, proposals, contracts, many policies and procedures, correspondence, grant related documents, financial records, hire and appointment letters, salary information, performance reviews, warning and disciplinary documents, etc. Also, experimental data generated under grants (NIH, CDC, NSF, etc.) which does not contain regulated data elements (PHI, etc.), but is not ready for public release would be considered moderate risk.

Access and use: Access may be granted without requiring an explicit data use agreement but with appropriate documentation. Moderate risk data are not intended for public dissemination but may be released to external parties subject to appropriate review and controls. The University reserves the right to designate that certain subsets of Moderate Risk data require training in the appropriate use and handling of the data.

Storage and Protection: Moderate Risk Information should be protected behind electronic firewalls or in private paper files in secured offices and should not accessible by the public or the University community at large without appropriate review and documentation. 

Transmission: Moderate Risk data can be freely shared with appropriate parties within the University environment.  If such data are transmitted by e-mail or other electronic transmission outside the University, there must be a documented business case and appropriate protection and usage guidelines must be followed.  Automatic forwarding of Moderate Risk data to external email or document storage sites is prohibited without explicit permission from Information Security Officers. 

Labeling of Moderate Risk Information: Information that is classified as Moderate Risk does not require labelling for internal use and distribution.  If data are shared outside the University, an explicit discussion of handling requirements by the external recipient should precede transmission.

LOW RISK

Definition: Data should be classified as Low Risk where the unauthorized disclosure, access, alteration, loss or destruction of that data would not be expected to have any effect on the University and its affiliates’ mission, assets, operations, finances, or reputation, would not be expected to pose any harm to individuals, or where such data are intended for public disclosure.

Examples: Examples include the University’s audited financial statements, schedule of classes, approved census facts and the information on the public University website, or de-identified or non-human research data.

Access and use: Low Risk data are available to all members of the University community and may be released to the general public. The University reserves the right to control the content and format of Low Risk information and may document access and use of low Risk data.

Appendix A: Definitions, Acronyms, and Related Information:

Protected Health Information (PHI) is health information (oral or recorded) that associates an individual with a health care provider, a health condition or diagnosis, a health care facility, or a health care plan. Because this information is so prevalent in the health care and research operations of the University, it is recommended that staff who work in these areas assume that most communication contains PHI. 

Personally Identifiable Information (PII) is information that can be used to uniquely identify, contact, or locate a specific person. Examples of PII data include social security number,  face, fingerprints, credit card numbers, date of birth, and birth place.

Payment Card Information is the 16-digit number on a credit or debit card, the security code, an individual’s PIN, the expiration date of the card and the individual card holder’s name. This information must comply with the Payment Card Policy. https://www.rochester.edu/adminfinance/treasury/pdf/Payment-Card-Policy.pdf

FERPA (Federal Education Rights and Privacy Act of 1974) is federal legisilation that protects the privacy of students’ records.  

FERPA Education Records are any records that are directly related to a student and maintained by the Universitiy.  https://www.rochester.edu/bulletin/policies/ferpa/.

GDPR (General Data Protection Regulation (EU) 2016/679) is a regulation in EU law on data protection and privacy for all individuals within the European Union (EU) and the European Economic Area (EEA). It also addresses the export of personal data outside the EU and EEA areas.

Data system: A technology platform that gathers or collects data as part of a business process or for reporting or other purposes.

Data collection: A group of data elements that support a business process.  Collections can be logical (not technology specific) or physical (residing in a particular system).

Data set: A prepared group of data elements put together for a specific consumption or reporting purpose from one or more data collections.

Appendix B: Related policies for specific information:

See the specific policies referenced for a more specific definition of each type of information and of the rules and procedures concerning their use