A breach response checklist that is first opened during a breach is already too late. The contacts will be stale, the evidence instructions will be unfamiliar and the person with authority to shut down a system may be on leave. Preparation is the work of making the checklist boring through repetition.
Use this document as a quarterly working record. Each item has an owner, the evidence that proves it is done, and a review frequency. Mark each line green, amber or red, and record the date and the person who signed it off. The checklist is deliberately operational: it covers what the business must have ready before an incident, not the forensic steps taken during one.
How to use this checklist
Assign one accountable owner per section, not one committee. Evidence should be a file, a screenshot, a test record or a signed note that another person can inspect. Frequency means the maximum interval between reviews; a role change or a new system can trigger an earlier one. At the end of each review, the incident lead signs the summary and records the next review date.
Schedule the review as a standing meeting with the section owners. A checklist completed by email without a conversation tends to collect optimistic answers.
1. Authority, scope and contacts
- Incident lead and alternate named. Owner: chief operating officer. Evidence: written appointment in the plan. Frequency: annual and on role change.
- Contact tree tested for responders, legal counsel, insurer and IT support. Owner: incident lead. Evidence: call log with dates and outcomes. Frequency: quarterly.
- Authority to isolate systems and commit emergency spend. Owner: managing director. Evidence: delegated limits recorded in the plan. Frequency: annual.
- Data map showing systems, vendors, backups and retention. Owner: IT manager. Evidence: current register with owners. Frequency: twice yearly.
- Regulator and bank contacts with reporting channels. Owner: legal counsel. Evidence: verified list and access test. Frequency: annual.
2. Detection and triage
- Severity matrix with examples. Owner: incident lead. Evidence: one-page matrix used in the last exercise. Frequency: annual.
- Triage script recording what was seen, when and by whom. Owner: IT manager. Evidence: template stored offline. Frequency: annual.
- Evidence preservation instruction issued before cleanup. Owner: IT manager. Evidence: printed card in the response kit. Frequency: annual.
- Out-of-hours escalation tested. Owner: incident lead. Evidence: test result with response time. Frequency: quarterly.
- Log sources and retention confirmed. Owner: IT manager. Evidence: source list with retention periods. Frequency: twice yearly.
3. Containment and evidence
- Procedure to isolate a host or account without destroying logs. Owner: IT manager. Evidence: reviewed runbook and last test note. Frequency: twice yearly.
- Credential reset and session revocation procedure. Owner: IT manager. Evidence: runbook with system owners listed. Frequency: twice yearly.
- Evidence log with chain of custody. Owner: incident lead. Evidence: template and a completed sample. Frequency: annual.
- Pre-approved forensic or incident support provider. Owner: IT manager. Evidence: contract or retainer with contact route. Frequency: annual.
4. Legal, regulatory and contractual notification
- Notification decision tree reviewed with counsel. Owner: legal counsel. Evidence: signed decision tree and named reviewers. Frequency: annual.
- Customer and supplier contracts with breach clauses indexed. Owner: legal counsel. Evidence: clause register with notice periods. Frequency: annual.
- Privacy obligations mapped to the data held. Owner: privacy lead. Evidence: data inventory and obligation summary. Frequency: annual.
- Insurance notification deadlines recorded. Owner: finance manager. Evidence: policy summary with dates. Frequency: annual.
5. Communication
- Holding statements for customers, staff, regulators and media. Owner: communications lead. Evidence: approved drafts stored offline. Frequency: twice yearly.
- Single spokesperson and approval path. Owner: managing director. Evidence: named spokesperson and deputy. Frequency: annual.
- Staff channel independent of compromised email. Owner: IT manager. Evidence: tested alternate channel. Frequency: quarterly.
- Customer support script for breach enquiries. Owner: customer service lead. Evidence: approved script and escalation route. Frequency: twice yearly.
- Status update cadence and template. Owner: communications lead. Evidence: cadence written in the plan. Frequency: annual.
6. Recovery and validation
- Restore priority order agreed by process owners. Owner: incident lead. Evidence: signed priority list. Frequency: annual.
- Clean rebuild procedure for affected systems. Owner: IT manager. Evidence: runbook and last rebuild test. Frequency: twice yearly.
- Validation tests for login, payment, data integrity and reporting. Owner: IT manager. Evidence: test checklist with results. Frequency: twice yearly.
- Post-restore monitoring window and owner. Owner: IT manager. Evidence: monitoring schedule. Frequency: annual.
7. Closure and learning
- Timeline and evidence pack template. Owner: incident lead. Evidence: completed sample from the last exercise. Frequency: annual.
- Root cause and control-change log. Owner: incident lead. Evidence: register with actions and dates. Frequency: after every exercise or incident.
- Post-incident review scheduled with affected teams. Owner: incident lead. Evidence: calendar entry and attendance record. Frequency: after every exercise or incident.
- Plan, training and contact details updated from findings. Owner: incident lead. Evidence: revision log and training record. Frequency: after every review.
Sign-off and review record
| Role | Name | Date | Version |
|---|---|---|---|
| Incident lead | |||
| IT owner | |||
| Legal counsel | |||
| Managing director |
What to exercise each quarter
- Call the contact tree and record how long it takes to reach every responder.
- Run one tabletop scenario and change at least one item in the plan afterwards.
- Restore a backup into an isolated environment and validate the data.
- Print the response kit, confirm the offline copies and replace anything outdated.
Response preparation and backup testing sit under Managed Technology & Cybersecurity, alongside monitoring and access review. The pricing page explains how a preparation engagement differs from an active incident. For the most common entry point, read what phishing prevention for employees costs in Bangladesh.
Sources
- NIST, SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management, accessed 17 November 2026.
- NIST, Privacy Framework, accessed 17 November 2026.
- DataGuidance, Bangladesh: data protection overview, accessed 17 November 2026.
- Information Commissioner's Office, Report a breach, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.