| Was the response appropriate? | |
|---|
| What lessons have been learned from the incident? | |
|---|
| Should any Security Policies be updated? | |
|---|
| Additional Comments: |
Appendix B: Incident Handling Checklist
| Action | Completed |
|---|
| Detection and Analysis |
| 1 | Determine whether an incident has occurred | |
| 1.1 | Review Impact Categories | |
| 1.2 | Determine if Restricted or Confidential Info was breached | |
| 1.3 | Determine Systems Impacted | |
| Communication |
| 2 | Determine appropriate notification requirements. | |
| 3 | Develop an action plan for meeting notification requirements | |
| Containment, Eradication, Preservation of Evidence |
| 4 | Acquire, preserve, secure and document evidence | |
| 5 | Contain the incident | |
| 5.1 | Stop potential loss of data | |
| 5.2 | Prevent further damage of compromised system and/or info | |
| 6 | Eradicate the incident | |
| 6.1 | Identify and mitigate all vulnerabilities that were exploited | |
| 6.2 | Remove all traces of the attack (Malware, inappropriate materials and/or other components) | |
| Remediate the Incident |
| 7 | Return affected system to an operationally ready state | |
| 8 | Confirm that the affected systems are functioning normally | |
| Documentation |
| 9 | Create and issue final reports. | |
| 10 | Archive evidence and documentation. | |
| Post-Incident Activities |
| 11 | Determine lessons learned. | |
| 12 | Make recommendations to prevent subsequent similar incidents. | |
| 13 | Close out the incident. | |