Checklist
Breach readiness checklist
What to have in place before an incident so that the intimations Rule 7 calls for can be made in time.
Rule 7 requires intimation to affected Data Principals and to the Board without delay, and detailed information to the Board within seventy-two hours of becoming aware. This checklist covers what to have in place before an incident so that those intimations can be made.
What the Act and the Rules require
- Section 8(5)Reasonable security safeguards are in place to prevent a personal data breach, including for processing by Data Processors.
- Rule 6(1)(c)Logs, monitoring and review give visibility of access to personal data, so that unauthorised access can be detected and investigated.
- Rule 6(1)(e)Those logs, and the personal data, are retained for one year unless another law requires otherwise.
- Rule 7(1)You can tell each affected Data Principal, through her user account or registered mode of communication: what happened, the likely consequences for her, what you have done, what she can do, and whom to contact.
- Rule 7(2)(a)You can tell the Board without delay: the nature, extent, timing and location of the breach and its likely impact.
- Rule 7(2)(b)You can give the Board, within seventy-two hours of becoming aware: detailed information, the facts and reasons, mitigation, findings on who caused it, remedial measures, and a report on the intimations to Data Principals.
People and decisions
- Good practiceA named person decides whether an incident is a personal data breach, with a deputy.
- Good practiceA named person approves each intimation before it is sent.
- Good practiceContact details for the response team are available without access to the affected systems.
- Good practiceStaff know how and to whom to report a suspected incident.
Materials
- Good practiceA template exists for the intimation to Data Principals, covering each element of Rule 7(1).
- Good practiceTemplates exist for both stages of the intimation to the Board.
- Good practiceThe inventory shows which systems hold which people's data, so that affected Data Principals can be identified.
- Good practiceAn incident log records the time you became aware and the time of each intimation.
Processors
- Rule 6(1)(f)Contracts with Data Processors provide for reasonable security safeguards.
- Good practiceEach contract states how quickly the processor will tell you of an incident.
- Good practiceYou hold a current incident contact for each processor.
Rehearsal
- Good practiceThe process has been walked through at least once with a realistic scenario.
- Good practiceLessons from that exercise, and from real incidents, are recorded and acted on.
Related reading
Personal data breach intimation under Rule 7
Who has to be told, what they have to be told and by when, taken from the text of Section 8(6) and Rule 7, with the preparation that makes it achievable.
DPDP readiness: a starter checklist
Thirty questions, grouped by theme, to establish where an organisation stands before detailed assessment begins.
Data Fiduciary or Data Processor: who carries which duty
The Act places its obligations on the Data Fiduciary, including for work done by its processors. A practical look at what that means on each side of the contract.