Data Breach Policy

 

 

1. Purpose of Policy

 

1.1. Sandhill Consultants Limited (“the Company”) are obliged under GDPR to have in place an institutional framework designed to ensure the security of all personal data during its lifecycle, including clear lines of responsibility.
1.2. This Policy sets out the procedure to be followed to ensure a consistent and effective approach is in place for managing data breach and information security incidents across the organisation.

2. Context of Policy

 

2.1. The Company holds, processes and shares a minimal amount of personal data, data is a valuable asset that needs to be suitably protected.
2.2. Every care is taken to protect personal data from incidents (either accidentally or deliberately) to avoid a data protection breach that could compromise security.
2.3. Reference should always be made to the Company Privacy Policy, when handling personal data, to avoid such occurrence.
2.4. Compromise of information, confidentiality, integrity, or availability may result in harm to individual(s), reputational damage, detrimental effect on service provision, legislative non-compliance, and/or financial costs.

3. Scope of Policy

 

3.1. This Policy relates to all personal and business sensitive data held by the Company regardless of format.
3.2. This Policy applies to all staff. This includes temporary, casual or agency staff and contractors, consultants, suppliers and data processors working for, or on behalf of the organisation.
3.3. The objective of this Policy is to contain any breaches, to minimise the risk associated with the breach and consider what action is necessary to secure personal data and prevent further breaches.

4. Risk Appetite of Organisation

 

4.1. The organisation has no risk appetite to the financial penalties that result from misuse of personal data, nor the reputational damage associated with misuse.

 

5. Details / Policy Breakdown

 

5.1. For the purpose of this Policy, data security breaches include both confirmed and suspected incidents.
5.2. An incident in the context of this Policy is an event or action which may compromise the confidentiality, integrity or availability of systems or data, either accidentally or deliberately, and has caused or has the potential to cause damage to the organisation’s information assets and/or reputation.
5.3. An incident includes but is not restricted to, the following:
5.3.1. Loss or theft of confidential or sensitive data or equipment on which such data is stored (e.g. loss of laptop, USB stick, iPad/tablet device, or paper record)
5.3.2. Equipment theft or failure
5.3.3. Unauthorised use of, access to or modification of data or information systems
5.3.4. Attempts (failed or successful) to gain unauthorised access to information or IT system(s)5.3.5. Unauthorised disclosure of sensitive / confidential data
5.3.6. Website defacement
5.3.7. Hacking attack
5.3.8. Unforeseen circumstances such as a fire or flood
5.3.9. Human error
5.3.10. ‘Blagging’ offences where information is obtained by deceiving the organisation who holds it.

 

6.0 Reporting an Incident:

 

6.1. Any individual who accesses, uses or manages the organisations information is responsible for reporting data breach and information security incidents immediately to the Company Data Protection Officer who can be contacted at [email protected]
6.2. If the breach occurs or is discovered outside normal working hours, it must be reported as soon as is practicable.
6.3. The report of breach will include full and accurate details of the incident, when the breach occurred (dates and times), who is reporting it, if the data relates to people, the nature of the information, and how many individuals are involved. An Incident Report Form should be completed as part of the reporting process. See Appendix A.

7. Containment and Recovery

7.1. The Company Data Protection Officer will firstly determine if the breach has occurred and is still occurring. If so, the appropriate steps will be taken immediately to minimise the effect of the breach.
7.2. An initial assessment will be made by the Company Data Protection Officer in liaison with relevant officers to establish the severity of the breach and who will take the lead investigating the breach (this will depend on the nature of the breach in some cases it could be the Company Data Protection Officer).
7.3. The Lead Investigation Officer (LIO) will establish whether there is anything that can be done to recover any losses and limit the damage the breach could cause.
7.4. The LIO will establish who may need to be notified as part of the initial containment and will inform the police, if appropriate.
7.5. Advice from experts across the organisation may be sought in resolving the incident promptly.
7.6. The LIO, in liaison with the Company Data Protection Officer, relevant officer(s) will determine the suitable course of action to be taken to ensure a resolution to the incident.

8. Investigation and Risk Assessment

8.1. An investigation will be undertaken by the LIO immediately and wherever possible within 24 hours of the breach being discovered / reported.
8.2. The LIO will investigate the breach and assess the risks associated with it, for example, the potential adverse consequences for individuals, how serious or substantial those are and how likely they are to occur.
8.3. The investigation will need to take into account the following:
8.3.1. the type of data involved
8.3.2. its sensitivity
8.3.3. the protections that are in place (e.g. encryptions)
8.3.4. what’s happened to the data, has it been lost or stolen
8.3.5. whether the data could be put to any illegal or inappropriate use
8.3.6. who the individuals are, number of individuals involved and the potential effects on those data subject(s)

8.3.7. whether there are wider consequences to the breach

 

9. Notification

9.1. The LIO and / or the Company Data Protection Officer will determine who needs to be notified of the breach.
9.2. Every incident will be assessed on a case by case basis; however, the following will need to be considered:

  • Whether there are any legal/contractual notification requirements;
  • Whether notification would assist the individual affected – could they act on the information to mitigate risks? Whether notification would help prevent the unauthorised or unlawful use of personal data?
  • If a large number of people are affected, or there are very serious consequences, whether the relevant Data Supervisory Authority should be notified. The Supervisory Authority will only be notified by the Company Data Protection Officer if personal data is involved.
  • The dangers of over notifying: Not every incident warrants notification and over notification may cause disproportionate enquiries and work.

9.3. Notification to the individuals whose personal data has been affected by the incident will be triggered by the Company Data Protection Officer. The service departments are responsible for communicating a description of how and when the breach occurred, and the data involved. Specific and clear advice will be given on what they can do to protect themselves and include what action has already been taken to mitigate the risks. Individuals will also be provided with a way in which they can contact the organisation for further information or to ask questions on what has occurred.
9.4. The LIO and or the Company Data Protection Officer must consider notifying third parties such as the police, insurers, bank or credit card companies. This would be appropriate where illegal activity is known or is believed to have occurred, or where there is a risk that illegal activity might occur in the future.
9.5. The LIO and or the Company Data Protection Officer will consider whether the Marketing Team should be informed regarding a press release and to be ready to handle any incoming press enquiries.
9.6. All actions will be recorded by the Company Data Protection Officer.

10. Evaluation and Response

10.1. Once the initial incident is contained, the Company Data Protection Officer will carry out a full review of the causes of the breach; the effectiveness of the response(s) and whether any changes to systems, policies and procedures should be undertaken.
10.2. Existing controls will be reviewed to determine their adequacy, and whether any corrective action should be taken to minimise the risk of similar incidents occurring.

10.3. The review will consider:

  • Where and how personal data is held and where and how it is stored;
  • Where the biggest risks lie, and will identify any further potential weak points within its existing measures;
  • Whether methods of transmission are secure; sharing minimum amount of data necessary;
  • Identifying weak points within existing security measures;
  • Staff awareness;
  • Implementing a data breach plan and identifying a group of individuals responsible for reacting to reported breaches of security.

10.4. If deemed necessary a report recommending any changes to systems, policies and procedures will be considered by the organisation.