General internal procedure in the event of a data breach
Please note: within 72 hours the notification must be made to the Dutch Data Protection Authority after the discovery of the data breach, regardless of the weekend or public holidays.
1. Detection of a breach of the security of the systems by:-
- Employee
- Register the incident and report it directly to the Privacy Officer. If the Privacy Officer is not available, the employee will report this to his manager. The manager is then responsible for informing the Privacy Officer as soon as possible.
- Inventory of the data breach in collaboration with the manager on the basis of the questions formulated in Appendix 1
- Customer / supplier
- Sends an e-mail or makes contact by telephone.
- Employees register the information and forward the report to the Privacy Officer. If the Privacy Officer cannot be reached, the employee makes an inventory in collaboration with his manager, based on Appendix 1 and processes it in the ticket. The manager is then responsible for informing the Privacy Officer as soon as possible.
- Employee
2. Investigation into the scope and technical aspects of a data breach by the concerned department manager in collaboration with engineers (within 24 hours).
-
- What breach of security measures has taken place and when?
- Which part of the IT system is involved and/or which equipment. Possibly: where is the equipment lost/stolen?
- What data is (possibly) involved?
- What are the (expected) consequences of the incident?
Simultaneous entry into force of the legal step-by-step plan by the Privacy Officer.
3. The engineers identify and implement measures to restore security after discussing the data breaches with the team (within 72 hours of reporting. If not feasible, as soon as possible).
4. If the incident must be reported or if reporting is desirable, the Privacy Officer, in consultation with the management, the lawyer and possibly the engineers, will prepare the report to the AP (within 72 hours).
5. If necessary: inform the parties involved (at the same time as the AP report).
6. If necessary: feedback to reporter (after AP report).
7. Inform (relevant) employees (after notification to the AP).
8. If necessary: marketing prepares a press release (after notification by AP).
9. Evaluation of the procedure with all concerned. Initiation by Privacy Officer.Procedure in the event of a data breach during the weekend/free days
- Detection or suspicion of a breach of the security of the systems by an employee, via a customer or third party.
- The person who makes or receives the observation will inform the Privacy Officer. If the Privacy Officer is not available, the employee will report this to the escalation manager. The escalation manager is then responsible for informing the Privacy Officer as soon as possible.
- Privacy Officer consults with the management.
- Management decides whether action should be taken.
- Privacy Officer calls in blue team when necessary.
- Continue from step 5 of the above procedure.
Legal procedure
- Detection of a breach of security systems or loss of equipment.
- What data was accessible?
- Can this data be regarded as personal data?
- Personal data is any information relating to an identified or identifiable person. A person is identifiable if his identity can reasonably be established without disproportionate effort.
- Is there a data breach?
- Have the processed personal data been irretrievably deleted/affected, or is it unlawful processing? Illegal processing is the unintentional/unauthorized change, provision or accessibility of personal data. Use the following rule of thumb: personal data goes where it should not be.
- If so, then there is a data breach.
- Can it reasonably be excluded that personal data has been lost or unlawfully processed?
- If so, then there is no question of a data breach.
- Have the processed personal data been irretrievably deleted/affected, or is it unlawful processing? Illegal processing is the unintentional/unauthorized change, provision or accessibility of personal data. Use the following rule of thumb: personal data goes where it should not be.
- Is my company the data controller?
- The controller is the person who, alone or together with others, determines the purpose and means of the processing of personal data.
- Example: you have outsourced the payroll administration to an external company. This company needs data from your staff to carry out payroll processing. In this construction you are responsible, because:
- you set the goal, namely the data is used for the purpose of salary processing;
- you (partially) determine the resources. You have selected the company and made an inventory of which systems are used, you have indicated how you want to receive the data, etc. There is no objection to the fact that the other party also partly determines its own working method.
- If your company cannot be regarded as responsible, you are obliged to inform the person responsible of the data breach.
- Should this leak be reported to the Dutch Data Protection Authority?
- A data breach must be reported to the AP, unless it is not likely that the breach poses a risk to those involved. For example when:
- The personal data is publicly available (public information);
- The personal data is encrypted and the password has not been leaked;
- It concerns accidental loss of personal data, while this data can be restored via a backup.
- A report can be made on the website of the AP (www.autoriteitpersoonsgegevens.nl).
- A data breach must be reported to the AP, unless it is not likely that the breach poses a risk to those involved. For example when:
- Should this leak be reported to the data subject?
- A data breach must be reported to the data subject when the breach is likely to pose a high risk to the data subject.
- High risk occurs when the expected adverse consequences of the data breach are likely to occur. Examples of adverse consequences: identity theft, reputational damage, financial losses, unwanted communication, and so on.
- Do the technical protection measures (such as encryption) that have been taken provide sufficient protection to be able to omit the notification to the data subject?
- Have the personal data been irretrievably deleted or damaged? Then encryption makes no sense and those involved must be informed.
- Was all personal data encrypted at the time of the breach?
- Is the encryption adequate?
- Is the residual risk acceptable?
- Have immediate measures been taken to ensure that data subjects are not adversely affected by the data breach? If so, no notification to data subjects is required.
- Is informing all those involved a disproportionate effort (for example because a very large number of those involved are involved)? In that case, a personal communication per data subject is not necessary and data subjects can be informed in a different way.
- A data breach must be reported to the data subject when the breach is likely to pose a high risk to the data subject.
Appendix 1 – Inventory plan for data breaches
- Record the name, company, telephone number and e-mail address of the reporter.
- When (date and time) and how was the leak detected?
- In which system is the leak located?
- How can the leak be used?
- Make sure that the operation of the leak is clear. The leak must be reproducible.
- What data is accessible?
- What actions are possible with regard to the data?
- Think of viewing, copying, changing, deleting or destroying, etc.
- Does the reporter have ideas on how the leak can be repaired?
- Will the reporter make the data breach public? If so, when?
- If yes, request the reporter to wait 72 hours so that measures can be taken first.
Appendix 2 – Informing data subjects
Some data breaches are so serious that the data subject(s) must be informed. Data subjects are the persons to whom the leaked personal data relates. Exactly when the data subject must be informed has already been described above. This appendix deals with the question of how the data subject should be informed.In any case, the notification will state:
- The nature of the infringement (what happened?).
- When describing the nature and content of the infringement, a general description will suffice. It is not necessary to dwell on the technical details. It must be discussed which personal data has been leaked, what the consequences may be for the data subject and what measures have been taken to tackle the breach. It is important that the description is in clear and simple language.
- The estimated date and time of the incident.
- The seriousness of the data breach.
- Inform the data subject about the consequences that are likely to occur as a result of the data breach. Think of identity theft, reputation damage, financial losses, unwanted communication, etc.
- The measures that have been taken to tackle the breach and limit the negative consequences for those involved.
- How was the vulnerability closed? Has a procedure been tightened up? Can the person concerned file a claim for damages, for example?
- The measures that the data subject must take to limit the negative consequences of the infringement.
- Think of changing usernames and passwords.
- Contact details/a central information point.
- In this way, the data subject can reach you if he or she has any questions about the data breach.
- The authorities where the data subject can obtain more information about the infringement, if applicable.