All News

How to contact us for support, subject access requests, data breaches and FOI's

This article lists the ways that Data Protection Education can be contacted for general data protection queries, data breaches, subject access requests and freedom of information requests.

While all our customers have a dedicated consultant who can be contact directly, if there is an urgent issue we would always advise emailing This email address is being protected from spambots. You need JavaScript enabled to view it..

When you email This email address is being protected from spambots. You need JavaScript enabled to view it. a ticket in our Knowledgebank will be automatically created and you will receive an email notification of this.  The ticket can then be seen by all members of the Data Protection Education team which then means the person most suitable to your ticket query can provide an answer.

How do I update the ticket I raised?

If you email a reply to the original email notification or any updates you received, then the ticket will be automatically be updated and is something we would recommend. If you send a new email to This email address is being protected from spambots. You need JavaScript enabled to view it. then a new ticket will be created.  There is currently no way for us to merge tickets, so replying to the original email notification is helpful.

You could also login to the Knowledge Bank:

https://dataprotection.education/

and update your ticket directly with the information.

How do I tell DPE about data breaches/subject access requests/freedom of information requests?

How to add a Subject Access Request:

By logging a subject access request on the Knowledge Bank as soon as you receive it, we can guide you through the process and give any additional support and advice.

Login to the Knowledge Bank and go to 'Data Rights Log', select the white text in the title bar. Choose  on the next screen to add a new data breach log. Then complete as much detail as you can in the data       breach form.

 

You can also report a subject access request by emailing This email address is being protected from spambots. You need JavaScript enabled to view it. which will raise a ticket but it will not add it to the data rights log. We always recommend that a subject access request is added to the data rights log where possible.

 

How to add a Data Breach:

The ICO says you must keep a record of any personal data breaches, regardless of whether you are required to notify them.  Logging those breaches in the DPE Knowledge Bank is a good way of keeping a record that your DPO can access and advise on.

Login to the Knowledge Bank and go to 'Breach Log', select the white text in the title bar. Choose  on the next screen to add a new data breach log. Then complete the form with as much detail as you can.

 

 

You can can also report a data breach by emailing This email address is being protected from spambots. You need JavaScript enabled to view it. which will raise a ticket but it will not add it to the data breach log. We always recommend that a data breach is added to the breach log where possible.

How to add a Freedom of Information (FOI) Request:

By logging a freedom of information request on the Knowledge Bank as soon as you receive it, we can guide you through the process and give any additional support and advice.

Login to the Knowledge Bank and go to 'FOI Log', select the white text in the title bar. Choose  on the next screen to add a FOI. Complete as much detail as you can in the form.

You can also raise a ticket to ask for advice about an FOI by emailing This email address is being protected from spambots. You need JavaScript enabled to view it. which will raise a ticket but it will not add it to the data breach log. We always recommend that a data breach is added to the breach log where possible.  Often advice and updates about current FOI's are posted on our news page:

https://dataprotection.education/news-top/news

It is also possible to contact us on: 0800 0862018

 

How a school fought back after a cyberattack

The following article talks about how a school thwarted a cyber attack, more through luck than judgement.  Our advice is for the whole organisation to be cyber aware and review how your organisation might respond when attacked.    The article gives ideas on how to begin making a cyber ready plan.

In October 2020 Kellett School was subject to a ransomware denial-of-service (DoS) attack orchestrated by a Russian criminal hacker group.  After the attack, a post mortem diagnostic showed that they had most likely got into the school's system through a member of staff clicking on a link in a phishing email, which, because staff had admin rights to their school devices, installed malware on the school system.  The full article can be read here:

 https://www-tes-com.cdn.ampproject.org/c/s/www.tes.com/magazine/leadership/data/how-our-school-fought-back-after-cyberattack?amp

Things to note from this attack:

  • Staff had been given admin access to to their school devices so that they could download any software from home that they needed during the period of home learning.
  • There were no protocols in place to ensure that access to the school network was limited to current staff.
  • There were no additional controls in place to the creation and deletion of admin accounts.
  • Staff had not been made to change their passwords for years.
  • Shutdowns and updates on school devices had not been forced
  • Staff had never been trained in cyber-awareness

Recommendations:

  • Senior Leadership makes cyber security part of the organisational culture
  • Everyone in the organisation should understand cybersecurity.  The organisation should make use of complex passwords.
  • Policies and procedures should be correctly followed.
  • There should be cyber insurance and emergency support in place
  • There should be an incident response plan
  • There are recommended experts on stand-by for help

Further resources can be found in our Information Security best practice area: 

https://dataprotection.education/index.php/best-practice-library/best-practice/information-security

and our Cyber Security checklist:

https://dataprotection.education/component/tjucm/itemform/cyber-security?id=90881&cluster_id=114

What to do in the event of a Cyber Attack 

Incidents or attacks where any security breaches may have taken place, or other damage was caused, should be reported to an external body. 

The SLT digital lead will be responsible for assigning someone to report any suspicious cyber incidents or attacks. This person will need to report this to: 

  • Report Fraud on 0300 123 2040, or the Report Fraud website 
  • the DfE sector cyber team at This email address is being protected from spambots. You need JavaScript enabled to view it. 

You may also need to report to: 

You must act in accordance with: 

Police investigations may find out if any compromised data has been published or sold and identify the perpetrator. 

Preserving evidence is as important as recovering from the crime.

Forward suspicious emails to This email address is being protected from spambots. You need JavaScript enabled to view it.. Report SMS scams by forwarding the original message to 7726 (spells SPAM on the keypad).

Little Guide to ACTION FRAUD

Compliance Manager released

We've released version 1 of the Compliance Manager tool.

What is it?
The Compliance Manager allows you to assign any document to staff and enable the following interactions

  • I have read and understood
  • I have used this in practice

or

Any standard document type can be uploaded and interactions selected. Then select the users to assign the document too and a date by which the users should have responded.

Search