Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Purpose

If you don’t report a security incident as soon as it is identified, you will delay receiving the help required to reduce the impact to your work and prevent loss of data.


Audience

FACULTY RESEARCHERS ADMIN STAFF IT STAFF STUDENTS


On this page

 Expand to view table of contents.

Initial considerations

Security incidents can be suspected, attempted, successful, or an imminent threat of disruption to or unauthorized access, use, disclosure, modification or destruction of university digital assets and/or data.

Consult your incident response plan.

  • Your divisional or departmental incident response plan should information you of (1) the incident response process and (2) how to escalate incidents to their academic, administrative, or technical leadership teams.

Determine the severity of the security incident.

High

  • “Significant fines, penalties, regulatory action, civil or criminal violations could result from disclosure. It could also cause significant harm to Institutional Information, major impairment to the Location’s overall operation, or the impairment of essential service(s).”

Medium

  • “Unauthorized use, access, disclosure, acquisition, modification, loss, or deletion could: (a) result in moderate damage to U of T, its students, employees, community or reputation; (b) result in moderate financial loss; or (c) require legal action.”

Low

  • “Unauthorized use, access, disclosure, acquisition, modification, loss or deletion could result in minor damage, small financial loss or affect the privacy of an individual or small group.”


What can I do?

For medium or high severity incidents.

For low severity incidents or if you are unsure of the severity.


  • No labels