Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Privacy & Compliance 6 min read

Security incident notification planning checklist

Who decides, who is told and what gets said. A checklist for building an incident notification plan that works under time pressure.

E
EncryptTechBD · 0 comments
Fountain pen on paper
Photo: Vintage RS / StockSnap

Many incident response plans explain how to contain an attack. Far fewer explain who decides to notify, who writes the message, which regulator is called first, and what the call centre should say when a customer asks whether their data was stolen. Notification is a decision process under time pressure, and it deserves its own plan.

This checklist covers the parts of notification planning that are usually missing: authority, legal mapping, evidence, templates, channels, third parties and verification. It is written for a business in Bangladesh that may also have customers, staff or contracts in other jurisdictions.

1. Authority and decision rights

  • Incident lead named. Owner: CEO or managing director. Evidence: a named person and a deputy, with the authority to convene the response team.
  • Notification decision group defined. Owner: Incident lead. Evidence: a small group covering legal, operations, communications and finance, with a quorum rule.
  • Board or owner contact confirmed. Owner: Company secretary. Evidence: an up-to-date contact list, including out-of-hours numbers.
  • Legal privilege decision made. Owner: Legal counsel. Evidence: a documented decision on whether advice is obtained under privilege and how that is preserved.
  • Delegation recorded. Owner: Incident lead. Evidence: who may notify if the lead is unavailable, and the limit of that authority.

2. Legal and regulatory mapping

  • Regulators identified by scenario. Owner: Legal. Evidence: a matrix of data type, regulator, trigger and deadline. Include Bangladesh Bank where financial services rules apply, and sector regulators for education, health or telecoms.
  • Contractual notification duties listed. Owner: Legal and procurement. Evidence: clauses from customer, supplier and cloud contracts with their notice periods.
  • Cross-border obligations checked. Owner: Legal. Evidence: a note on whether GDPR, sector rules or customer contracts apply to specific data sets.
  • Threshold and assessment questions written. Owner: Legal and security. Evidence: a short test covering data sensitivity, number of people affected, likelihood of harm and whether the data was encrypted or exposed.
  • Signatory and filing details ready. Owner: Compliance. Evidence: portal accounts, registration numbers and the person authorised to submit.

Do not rely on a single generic deadline. Different regulators, contracts and jurisdictions impose different clocks, and the clock usually starts when the incident is discovered, not when it is fully understood.

3. Evidence and facts

  • Incident timeline maintained. Owner: Incident lead. Evidence: timestamped entries for detection, containment, decisions and notifications, in a single log.
  • Data categories identified. Owner: Data owner. Evidence: a list of the fields involved, whether they were encrypted, and who is affected.
  • Confidence level stated. Owner: Security lead. Evidence: each fact marked confirmed, probable or unknown, so the message does not overstate certainty.
  • Containment status recorded. Owner: Security lead. Evidence: what has been stopped, what remains exposed and the next review time.
  • Evidence preserved. Owner: Security lead. Evidence: logs, disk images and access records retained with a chain of custody.

4. Message and template pack

  • Regulator notification template. Owner: Legal. Evidence: a draft covering nature of incident, data categories, likely consequences, measures taken and contact point.
  • Customer notification template. Owner: Communications. Evidence: plain-language version in Bangla and English, reviewed by legal.
  • Employee notification template. Owner: HR. Evidence: what staff should do, what they should not say and where to route questions.
  • Call centre script and FAQ. Owner: Customer service. Evidence: tested answers for "was my data stolen?", "do I need to change my password?" and "will you compensate me?".
  • Status page and media holding statement. Owner: Communications. Evidence: pre-approved wording that can be published within the first hour.

5. Channels and contact routes

  • Regulator contact route tested. Owner: Compliance. Evidence: a test call or portal login completed in the last six months.
  • Customer contact data current. Owner: Marketing operations. Evidence: consent status and deliverability checked for the channels you would use.
  • Out-of-hours coverage confirmed. Owner: Operations. Evidence: a rota with named deputies for the first 24 hours.
  • Insurer and law enforcement contacts listed. Owner: Finance and legal. Evidence: policy number, notification contact and a decision rule for involving police.
  • Third-party contacts listed. Owner: Procurement. Evidence: security and account contacts for cloud, payment, payroll and messaging providers.

6. Third parties and supply chain

A breach at a payment provider, payroll bureau or cloud host can trigger your own notification duties. Confirm in writing that each critical supplier will notify you within a defined period, name the contact, and provide enough detail for you to assess the incident. Put the same expectation on your own subcontractors.

7. Records and after-action review

  • Notification log complete. Owner: Incident lead. Evidence: who was told, when, by which channel and what was said.
  • Copies retained. Owner: Legal. Evidence: submitted forms, emails and published statements stored with the incident record.
  • Post-incident review scheduled. Owner: Incident lead. Evidence: a review within two weeks covering what worked, what was slow and what changed.
  • Plan updated. Owner: Security lead. Evidence: a new version with the changes and the date of the next test.

Verification

  1. Run a tabletop exercise with a realistic scenario and a two-hour clock.
  2. Test the call tree, including one person who is unavailable.
  3. Complete a draft regulator notification without submitting it.
  4. Ask a customer-service agent to answer three scripted questions.
  5. Confirm the supplier notification clause with your two largest vendors.
  6. Repeat at least annually, and after any major change in systems or regulation.

Common mistakes

  • Waiting for complete facts before notifying, when the law requires an early notification.
  • Letting the technical team write customer messages.
  • Using a single channel that may itself be compromised.
  • Promising that no data was accessed before the forensic review is complete.
  • Forgetting that a supplier's incident can be your incident.
  • Keeping no record of what was said and when.

Where this fits in our work

If you need the plan tested rather than written, start with Managed Technology and Cybersecurity. The pricing page explains how we scope readiness work. For the technical response side, read the SME incident response guide.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes