Servana

Free starter template · SV-PLN-01

Incident response plan

A starter plan for detecting, containing and recovering from security incidents, with the POPIA breach notification section written out in full.

PDF · 8 pages

What is an incident response plan?

What it is

An incident response plan sets out what your organisation does when something goes wrong: a cyber attack, a data breach, a lost device or an incident at a supplier. It says who leads, how incidents are classified, and how you contain them, recover and learn from them.

This starter template writes the POPIA notification section out in full. For the rest, it gives you the structure and what to include.

A starter template: the key sections are written out in full, and the rest give you the structure and what to include.

Why you need this template.

Why you need it

  1. 01

    Decide before the bad day

    Decisions made in advance mean nobody is working out who to call while an incident spreads.

  2. 02

    Meets POPIA's notification duty

    Section 22 requires you to tell the Information Regulator and the people affected as soon as reasonably possible. The steps are written out for you.

  3. 03

    Limits the damage

    Clear containment and recovery steps stop one incident from becoming a business-wide outage.

  4. 04

    Shows you're prepared

    Customers, insurers and auditors ask whether you have a tested plan. This gives you one to test.

What's in the template.

What's inside

  • POPIA section 22 notification, written out in full: when, how fast and how
  • Information Regulator e-Portal steps and a notification checklist
  • What a notice to the people affected must say
  • Response team and severity level tables to fill in
  • What to include for every phase: detect, assess, contain, eradicate and recover
  • Other notifications: customers, insurers, the FSCA or PA, and SAPS
  • Evidence, testing and post-incident review sections

How to make it yours.

How to use it

  1. 01

    Start with section 6

    The POPIA notification section is complete. Adapt the details, and check the Regulator's current process before you rely on it.

  2. 02

    Write the other sections

    Each one says what to include. Write it for how your business actually works.

  3. 03

    Fill in and tidy up

    Replace every highlighted [placeholder] and delete the guidance boxes before you publish.

  4. 04

    Practise it

    A plan nobody has practised won't work on the day. Test it at least once a year (section 9).

Get the incident response plan.

It's free. Give us your first name and work email and it downloads straight away.

PDF · 8 pages

Questions, answered.

Questions

When do we have to notify the Information Regulator?

When there are reasonable grounds to believe that personal information you're responsible for has been accessed or acquired by an unauthorised person. POPIA section 22 requires you to notify the Regulator and the people affected as soon as reasonably possible after you discover it. Don't wait for certainty.

How do we notify the Information Regulator?

Through the Regulator's e-Portal, which security compromise notifications must now go through. Record the date, time and reference number, and keep the Regulator updated as your investigation develops. Check the Regulator's website for the current process.

What makes this a starter template?

It writes the hardest section out in full, here the POPIA notification steps, and gives you the structure and what to include for the rest. Your plan has to fit your own systems and people, so those parts are yours to write.

How often should we test the plan?

At least once a year, with a tabletop exercise or a simulation, and after any major change. Feed what you learn back into the plan.

All templates

Want it finished for you?

We tailor these policies and plans to how your business really works, and get the controls behind them ready for ISO 27001 or POPIA. Book a 30-minute call.