Incident Tracking Form
Incident Tracking Form
G E N E R A L I N F O R M AT I O N
Complete the following fields to document general information about the incident.
Occurrence Date & Time Reported Date & Time Email Address
- Select One -
Summary
HANDLERS
Document the names and contact information of the individuals responsible for managing the incident.
Data Breach
Data accessed, modified, and/or exfiltrated by an System Failure
unauthorized entity. Subcategories could include breaches The failure of or vulnerability in a system which can cause
of customer data, privacy data (e.g., PII or PHI), the delays in processing, monetary loss, or loss of data.
organization’s proprietary data, etc. Subcategories could include application failure, network
failure, power failure, etc.
Denial-of-Service
Malicious activity preventing authorized access to Third Party
resources. An incident originating from or through a third party,
causing direct or indirect damage to the organization.
Subcategories could include third-party data breaches,
service unavailability, etc.
Human Error
An accidental, improper, or otherwise ill-chosen act by an
individual (e.g., employee, third-party, etc.) which results in
Unauthorized Use
processing delays, equipment damage, or compromised
The unapproved use of systems or data.
data.
Other
Lost / Stolen Asset
Lost or stolen systems, equipment, and/or applications (e.g.,
desktops, laptops, mobile devices, removable media, etc.).
Malicious Code
Unauthorized software applications designed to access a
system, including a variety of forms of hostile, intrusive, or
annoying code. Subcategories could include botnets,
keyloggers, ransomware, rootkits, trojans, viruses, worms,
etc.
Natural Event
Uncontrollable events caused by nature (e.g., tornado,
hurricane, earthquake, lightning, flood, etc.).
Severity Level
- Select One -
EVIDENCE
List of Evidence
Document a list of evidence gathered during the investigation, as well as chains of custody, when applicable.
A N A LY S I S
Scope Origins
Describe the areas, networks, systems, applications, etc. which Describe who or what originated the incident, such as names
are affected by the incident. Document specific details, such as and IP addresses of systems conducting the attack, or publicly
model numbers, serial numbers, host names, IP addresses, etc. available information about the attacker(s).
C O N TA I N M E N T
Could the containment strategy interfere with Could the containment strategy interfere with
evidence preservation? service availability?
Yes No Yes No
RECOVERY
Recovery Actions Performed
Examples of recovery strategies include restoring data from a backup, rebuilding servers, replacing hardware, and reprovisioning
accounts.
POSTMORTEM
Meeting Date Damage Estimate
Meeting Attendees
Meeting Notes
Document notes from the postmortem meeting, including lessons learned, details of what occurred with the incident, steps which were
taken to intervene, outcomes of the handling process, and next steps to be taken.