Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

🎓 Purpose

Preparatory activities, including documenting, training, and testing, are essential to identifying, containing, eradicating, and recovering from a security incident. It is important to act as if you a preparing for when an incident will occur, rather then if. Taking a proactive approach will help you return to normal activities as soon as possible.

👥 Audience

Status
colourBlue
titleresearchers
Status
colourRed
titleAdmin staff
Status
colourPurple
titleIT staff


🔖 Contents

Table of Contents
minLevel1
maxLevel3
include
outlinefalse
indent
styledefault
excludePurpose|Audience|Contents|Search|Additional help|Related articles
typelist
class
printablefalse

(question) Initial considerations

Departmental and divisional incident response plans.

Follow security best practices.


\uD83D\uDCD8 What can I do?

Review and adopt the University incident response plan or use it to create your own.

Report suspected incidents.


Page Properties
hiddentrue

Name

Role

Date

Michael Laurentius

Author

Sue McGlashan

Approver (Manager)

Reviewer

Live Search
spaceKeyISH
sizelarge
additionalpage excerpt
placeholderHow do I...
typepage
labelskb-how-to-article,kb-general-concepts,kb-spec-how-to-article


✉️ Additional help

General

https://uoft-infosec-cf.atlassian.net/wiki/spaces/ISH/pages/4948958/Additional+help#%F0%9F%9B%A1%EF%B8%8F-Information-Security-(IS)

https://uoft-infosec-cf.atlassian.net/wiki/spaces/ISH/pages/4948958/Additional+help#%F0%9F%96%A5%EF%B8%8F-Information-Technology-(IT)

Researchers

https://security.utoronto.ca/services/research-information-security-program/


Filter by label (Content by label)
showLabelsfalse
max10
maxCheckboxfalse
showSpacefalse
reversefalse
excerptTypesimple
cqllabel = "incident" and title !~ "Incident response"