What else do I need to know?
Definitions
Notification: the act of informing persons affected by a breach of Protected Personal Data (PPD) that their information was included in the breach and the steps they can take to protect themselves and their privacy. Notification also includes required noticing to federal and state agencies. Notification to affected individuals will be overseen by Chief Privacy Officer, and depending on the data breached, may include the following components:
- A general description of the unauthorized access or acquisition;
- The type of personal information affected;
- A general description of the steps the University will take to protect the information from further unauthorized access or acquisition;
- Instructions and necessary information for notifying the major credit agencies of suspected or potential identity theft as needed; and
- A toll free number to obtain more information and resources.
Non-Public Protected Data (NPPD): for the purpose of this Policy will be the same as the definition found in ¶¶Òõ̽̽’s Privacy Policy.
Protected Personal Data (PPD): includes, without limitation, any NPPD relating to an identified or identifiable natural person.
Security Breach:
- The unauthorized acquisition of electronic data or a reasonable belief of an unauthorized acquisition of electronic data that compromises the confidentiality, integrity and availability of PII as defined by the State of Vermont’s Security Breach Notice Act (9 V.S.A. §2430(9))(or any other applicable similar state law) maintained by ¶¶Òõ̽̽;
- The unauthorized acquisition of- or a reasonable belief of an unauthorized acquisition of login credentials issued by ¶¶Òõ̽̽ that compromises the security, confidentiality, or integrity of PII maintained by ¶¶Òõ̽̽ as defined in (1) above;
- A breach of unsecured protected health information, regardless of the form and format of the information (i.e., electronic, paper) in accordance with the HIPAA Breach Notification rule, 45 CFR § 164.402 and HITECH Act (P.L. 111-5, § 13407); or
- An unauthorized acquisition or reasonable belief of an unauthorized acquisition of NPPD or login credentials that University management determines to merit notification to affected persons notwithstanding the lack of regulatory obligation to do so.
Security Incident: An event that a User has reason to believe may have encompassed a Security Breach.
User: Any user of NPPD, including any faculty, staff, consultant, contractor, student, or agent thereof.
Identifying and Reporting Security Incidents
In the event that a User detects a suspected Security Breach, the User must report the Security Incident to the ¶¶Òõ̽̽ Information Security and Assistance Line at 802-656-2123, toll-free at 866-236-5752, or by email to ISO@uvm.edu. The User will be asked to provide the following information:
- User contact information
- Name(s) of University Department(s) involved
- A brief description of what happened
- A general description of the NPPD affected
As directed by the Information Security Officer (ISO) or their designee (herein referred to as the Incident Handler or IH), the reporter shall follow instructions regarding preserving evidence. The Incident Handler shall activate the Computer Security Incident Response Team (CSIRT) to advise on- and assist in addressing technical aspects of securing data.
Security Incident Protocol
- The IH will notify the Chief Privacy Officer (CPO) of the Security Incident, log the incident, and initiate evaluation.
- The evaluation process shall include:
- Establishing the scope of the Incident,
- Securing the Data,
- Preserving evidence, and
- Contacting Law Enforcement, if appropriate.
- Once the IH has completed the initial evaluation, the IH shall communicate the results to the CPO.
- The CPO in coordination with the Office of General Counsel (OGC) will make a determination regarding whether a Security Breach has occurred and the type of NPPD involved. See “Guidance for Data Breach Determination and Notice.â€
- If it is determined that a Security Breach did occur:
- The CPO will notify the University Communications Office, and, as deemed appropriate, brief the Office of Federal, State and Community Relations, and executive management.
If it is determined that the Security Breach included PPD, the CPO will advise the University Department where the breach occurred regarding the required form of notice, if any, to be sent to the affected individuals or business associates, if applicable. The University Department shall inform the CPO of the existence of any business associate agreement.
If notice is required, the University Department that was responsible for maintaining the breached information will be responsible, in consultation with the CPO, for noticing affected individuals or business associates. The affected University Department is responsible for expenses related to the breach.
- The CPO, in consultation with the OGC, shall notify any governmental entity, as required, of the breach, or shall ask the University Department to do so.
- The ISO will make recommendations to the University Department(s) to correct or improve information security practices that may have led to the incident.
- If it is determined a security breach did not occur, the ISO will, when appropriate, make remedial suggestions to the User and/or University Department(s) to correct or improve information security practices that may have led to the incident.
Notice Requirements
Depending on the determination, ¶¶Òõ̽̽ will take one of the following next steps:
- If GDPR covered PD was breached and notification is required or merited, affected individuals shall receive a notice of the incident, in the most expedient time possible and without unreasonable delay, consistent with the legitimate needs of law enforcement agencies.
- If PII as defined under VT law or if login credentials were breached, affected individuals must be provided notice in accordance with legal requirements.
- If HIPAA covered PHI was breached, affected individuals must be provided notice without unreasonable delay and in no case later than 60 days from discovery of the breach.
The method of noticing a breach may vary dependent on the number of individuals affected, the cost of noticing, and the normal means of communication with affected individuals, but in all instances as guided by the applicable legal requirements.
¶¶Òõ̽̽ may outsource some or all of the breach notification requirements depending on the nature and extent of the breach.
Documentation
The University will document all reported information security incidents. Documentation responsibilities include:
ISO
- Log of incidents received
- The evaluation process and outcome of the evaluation
- Recommended corrective action to contain the incident and prevent future incidents
CPO
- Breach determination outcome
- Identification of Responsible Department
- Documentation of notice made to affected individuals, Federal offices, State offices, and business associates, where applicable
Is there education available?
Training will be provided on an as-needed basis as determined by the Approval Authority or the Responsible Official.