Canvas CyberSecurity Incident FAQs
-
What has happened?
On 1st May 2026, Instructure, the provider of the Canvas Learning Management System (LMS), confirmed that it experienced a cybersecurity incident affecting data held within the Canvas platform. The criminal extortion group known as ShinyHunters has claimed responsibility for the attack.
Instructure has stated that the information involved appears to include names, email addresses, student identification numbers, and messages exchanged between users within Canvas. Instructure has stated that there is currently no evidence that passwords, financial information, government-issued identification numbers, or dates of birth were compromised.
Canvas was subsequently placed into maintenance mode while Instructure investigated the incident and implemented security measures.
In response, Instructure has
- Revoked privileged credentials and access tokens associated with affected systems
- Deployed patches to enhance system security
- Rotated certain keys, even though there is no evidence they were misused
- Implemented increased monitoring across all platforms
As a Data Controller, your organisation remains responsible for ensuring that any vendors processing personal data on your behalf comply with applicable data protection laws. This includes ensuring that your organisation has undertaken appropriate vendor due diligence (Vendor Assessments), completed the necessary Data Protection Impact Assessments (DPIAs), maintained Records of Processing Activities (ROPAs), and documented risk management decisions relating to the use of Canvas.
Where a breach occurs involving a Data Processor such as Instructure, the school or institution remains responsible for investigating the breach, assessing risks to individuals, and determining whether notification obligations apply under the laws in your jurisdiction.
-
How do we know if we are affected by the Canvas cybersecurity incident
Instructure is contacting affected institutions directly. If your organisation is impacted, you should expect to receive communication from Instructure.
Within schools, this communication is likely to be received by the internal owner of Canvas, such as an IT lead, digital learning lead, or EdTech manager.
Your organisation should therefore:
- Check with the internal business owner or system owner responsible for Canvas to confirm whether any communication has been received from Instructure.
- Ensure that any such communication has been escalated internally to appropriate stakeholders, including data protection, safeguarding, IT, and leadership teams.
- Avoid assuming that you are unaffected simply because central teams have not been notified. In many cases, notifications sit within operational or technical teams rather than governance functions.
If your organisation has received notification from Instructure, it is appropriate to proceed on the basis that your Canvas environment is affected.
-
We are affected by the Canvas cybersecurity incident. What should we do next?
Your school should carry out the following steps to ensure that the data breach is fully investigated and resulting risks are mitigated:
- Ensure you are following security best practices as recommended by Instructure, including:
- Enforcing multi-factor authentication (MFA) on privileged accounts.
- Reviewing and limiting administrative access to remove anyone who shouldn't have access.
- Rotating API tokens or keys where applicable.
- Following your internal incident breach policy and procedures, carry out an incident investigation to understand how data has been affected. 9ine’s Incident Management platform is one way to discharge this liability.
- Assess how Canvas is used within your organisation to understand what other information may be affected, in particular:
- Whether messaging functionality is enabled (teacher–student and/or student–student).
- The typical nature of communications taking place within Canvas.
- Whether messages are routinely used to discuss sensitive matters, such as SEN information, child safety concerns, pastoral support, behavioural issues, or other confidential student information.
- Once the scope of the breach has been confirmed, assess whether the breach exceeds the threshold for conducting a breach notification to your data protection regulator and data subjects.
- Ensure that you have appropriate due diligence in place for Canvas including:
- A completed vendor assessment, noting any risks posed by the vendor’s data processing practices.
- A completed Record of Processing Activity for the use of Canvas within the school.
- If use of Canvas meets the risk threshold, a completed Data Protection Impact Assessment or Privacy Impact assessment for the use of Canvas within the school.
9ine’s Vendor Management Platform is designed to provide schools with a ‘traffic light’ view of risks and issues pertaining to each Vendor’s compliance. Subscribing to this platform gives you access to 200+ pre-completed vendor assessments, including for Canvas, and allows you to request additional vendors to be assessed or vetted.
Additionally, our Privacy Platform provides a straight-forward way for schools manage their data protection and privacy obligations, including completion of DPIAs and capturing Records of Processing.
-
Do we need to notify the regulator and data subjects?
When considering whether you need to report a data breach to data subjects or the data protection regulator in your jurisdiction you must refer to the legal requirements in your country.
If your jurisdiction has a reporting requirement within the data protection law, it will specify a threshold that is met to trigger notification. When carrying out your incident investigation you should consider whether the scope of the data that has been breached triggers the notification requirement.
Some jurisdictions will list certain categories of data that must be included in the notification to the regulator. Others may state that your school makes an assessment based on the likelihood of harm that might come about from the breach and should that likelihood be considered high risk, a notification must be issued.
Schools in the United States
For schools operating in the United States, obligations are typically set out across a combination of state data breach notification laws, state education privacy laws as well as consumer protection and security laws. In some cases, sector-specific requirements (for example, those linked to student records or education data) will also apply
These laws often require notification to affected individuals, and in some cases state regulators or Attorneys General, where certain categories of personal information have been compromised.
Schools should be aware that US state laws can vary significantly in terms of notification thresholds and timelines as well as requirements for reporting to the regulator.
Whee your institution has students residing in multiple states, you may need to consider the requirements of each relevant state law.
Should your school require assistance with understanding the breach reporting thresholds, you can reach out for consultancy support by contacting support@9ine.com or via the website. -
How quickly should we notify the regulator, do we wait until we have all the information?
Most data protection regulations contain prescriptive timeframes that an organisation must adhere to when notifying data breaches to the regulator. It is recommended that your school reports within this timeframe, even if you do not have all the information known at that point to avoid breaching these statutory requirements.
Regulators generally recognise that organisations may need to submit an initial or partial notification while investigations remain ongoing. Additional information can usually be provided at a later stage.
In the United States, notification timelines are typically defined at state level and vary between jurisdictions. Some states require notification “without unreasonable delay”, while others specify defined timeframes (for example, 30, 45, or 60 days depending on the state and circumstances).
Where multiple state laws apply, organisations should take a cautious approach and work to the shortest applicable timeframe where feasible.
-
What do we need to include in our data notification to data subjects?
Generally, a notification to data subjects should include:
- The name and contact details of the data protection officer, data protection lead or another individual at the school who can provide further information to data subjects.
- What the consequences of the personal data breach are likely to be.
- The measures taken or planned to deal with the breach and the measures taken to mitigate any possible adverse effects (in this case these will include measures taken by Instructure and any you have taken at your school).
- Any specific advice on the steps individuals can take to protect themselves, and any help your school can offer. This could include advising that they reset passwords or telling them to be alert for phishing emails or fraudulent activity on their accounts.
However, the requirements may differ between jurisdictions.
-
Should we put information about the breach on our website?
It is important to notify data subjects about the breach in a clear and transparent manner and within the time frames set out by the relevant regulation for your jurisdiction. The best way to do this is via email. If however you do not have email addresses for all data subjects, you should consider other ways to inform them of the breach. This may be through your community portals or spaces, or via a notification on your website. You should however also consider that a data breach notification can be alarming and consider ways to minimise concern.
Guidance
If your school is affected, we can also provide support with
- Guidance on next steps at your school
- Determining if you need to notify the regulator and data subjects, and if so how to provide notification
- Carrying out a vendor assessment to identify any gaps in data privacy and protection requirements and how you can mitigate them.
- Completing a Records of Processing and a DPIA for your LMS
- Creating or review of an existing Incident and Data Breach Policy and Procedure to ensure you are ready for any future incidents
You can reach out for consultancy support by contacting your consultant or emailing support@9ine.com or via the website.

