Vulnerability Disclosure Policy

How to tell us about a possible security weakness in our websites, what we ask of you while you do so, and what you can expect from us in return.

Security contact
security@ace-learning.org.uk
Policy owner
Trust Digital Lead
Version
2.1
Last reviewed
Next review

1. Our commitment

We are committed to protecting the security, confidentiality and integrity of our digital systems and of the information entrusted to us by pupils, families and staff.

Security researchers, technology professionals and members of the public can help us find weaknesses we have missed. We welcome reports made in good faith and will look into every credible report in a proportionate and timely way.

This policy follows the National Cyber Security Centre (NCSC) vulnerability disclosure guidance and supports our work towards the Department for Education’s cyber security standards for schools and colleges.

2. What this policy covers

In scope

The following public websites, which the Trust operates or manages directly:

Reports welcome, but not in scope for testing

You may also tell us about problems you notice with other Trust services, such as email sent from our domains. Being able to report on these does not give you permission to test them.

Out of scope

  • Third-party platforms and cloud services we use but do not run, such as management information systems, parent communication and payment platforms, learning applications and Microsoft 365. Please report these to the supplier first. If you are not sure who the supplier is, contact us and we will pass your report on.
  • Websites and services run by other organisations, even if they link to or from our sites.

Issues we do not normally treat as vulnerabilities

To help us focus on issues that put people or data at real risk, please do not report the following unless you can show a realistic way to exploit them:

  • missing security headers or other best-practice recommendations with no demonstrated impact
  • TLS or cipher configuration findings from automated tools
  • software version numbers or banners being visible
  • clickjacking on pages with no sensitive actions
  • SPF, DKIM or DMARC configuration reports
  • results from automated scanners that have not been checked by hand

This policy does not give permission for active security testing or penetration testing of any Trust system. Any such activity needs our explicit, written permission in advance.

3. How to report a vulnerability

Email security@ace-learning.org.uk with the subject line Security Vulnerability Report.

If you can, please include:

  • the website and page address (URL) where you found the issue
  • a short description of the issue and the type of vulnerability
  • how you came across it
  • what you saw and any steps that led to it, so we can check it ourselves
  • the impact you think it could have
  • how you would like us to contact you

You can report anonymously, but we will not be able to update you or ask follow-up questions.

Do not send passwords, access tokens, pupil records, staff information or any other personal or confidential data in your report. Describe what you saw instead. If we need more evidence, we will agree a secure way for you to send it.

4. What we ask of you

Please act responsibly, keep any harm to a minimum and respect the privacy of everyone who uses our services. In particular, you must not:

  • break the law, including the Computer Misuse Act 1990 and data protection law
  • try to access accounts, systems, networks or information that you are not authorised to access
  • access, copy, change, download, keep or share personal or confidential information
  • run automated vulnerability scans, penetration tests, brute-force or password attacks
  • carry out denial-of-service attacks, load or stress testing, or anything else that could disrupt our services
  • use phishing, social engineering or any other method to get information from pupils, staff, parents, governors, trustees or contractors
  • try to exploit a suspected vulnerability, confirm it through active testing or investigate it further without our written permission in advance. This includes escalating privileges, moving between systems or keeping access
  • upload malicious files, install software or change website content
  • test the physical security of Trust premises or equipment
  • contact us about a vulnerability through any channel other than the one in this policy and our security.txt files
  • ask for payment or any other reward in return for details of a vulnerability
  • publish details of a vulnerability that has not been fixed without agreeing this with us first (see section 7)

If you are not sure whether something is allowed, stop and ask us first.

5. If you find personal data

Our websites serve children and families, so protecting pupil and staff information is a safeguarding matter for us, not just a technical one.

If you come across personal or confidential information, or anything that suggests a system has already been compromised:

  1. stop straight away and do not look any further
  2. do not copy, keep or share the information
  3. tell us as soon as you can, using the contact details above, without sending us the information itself
  4. if you have already obtained any of it by accident, tell us and do not pass it on. We will tell you how to delete it securely or otherwise handle it

Prompt reporting matters. Under UK data protection law we may have to report a personal data breach to the Information Commissioner’s Office within 72 hours of becoming aware of it.

6. What happens next

If you give us a way to contact you, here is what you can expect. Working days exclude weekends and public holidays in England.

Our response targets
Stage What we will do Target
Acknowledge Confirm we have received your report. Within 5 working days
Triage Check whether the report describes a credible vulnerability, assess the impact and tell you our view. Within 10 working days
Fix Prioritise the work by severity, involving our technical suppliers where they host or manage the affected service. Depends on severity and complexity
Close Tell you when the issue is fixed. We may ask you to check the fix. When the fix is in place

We will keep you updated while we investigate. Please allow at least 14 days between requests for an update. During school holidays we may take longer to respond to issues that are not urgent.

We cannot promise a specific fix date or detailed technical updates in every case, particularly where a supplier must make the change.

7. Coordinated disclosure

Please give us a reasonable chance to investigate and fix the issue before you make any details public. Once the issue is fixed, we are happy to work with you on a coordinated disclosure and to agree a date and what will be said.

We aim to fix valid vulnerabilities as quickly as we reasonably can, prioritising them by severity and potential impact. Where possible we work towards a fix within 90 days, but complex issues, or those that need a third-party supplier to act, may take longer. If so, we will explain why and agree a revised timeline with you.

Any public write-up must not include personal data or information that could identify pupils, staff or families. Where safeguarding or data protection is involved, we may ask you to delay or limit what is published.

We will not ask you to sign a non-disclosure agreement just to submit a report.

This policy is designed to match common good practice in vulnerability disclosure. It does not authorise you to do anything unlawful, or anything that would cause the Trust or our suppliers to break our legal obligations.

If you make a report in good faith and follow this policy, we will treat it as helpful and will not seek legal action or refer you to the police because of your report.

This does not apply where activity goes beyond this policy, causes harm or disruption, involves personal data being kept or shared, or is otherwise unlawful. In those cases we will take whatever action is appropriate, which may include reporting to the police or the Information Commissioner’s Office.

9. Recognition and rewards

We are grateful for reports that help keep our pupils, families and staff safe.

As a multi-academy trust, we do not run a paid bug bounty programme and do not offer money or other rewards for reports.

We will not name you publicly without your permission. If you would like to be thanked publicly once an issue is fixed, tell us in your report.

10. Other concerns

This policy is only for technical security vulnerabilities. Please do not use it for:

  • Safeguarding concerns about a child. Contact the academy’s Designated Safeguarding Lead through the academy office. If a child is in immediate danger, call 999.
  • Data protection requests or concerns, such as a subject access request. Contact the Trust’s Data Protection Officer, as set out in our privacy notices.
  • Complaints. Use the Trust’s complaints procedure.
  • Everyday IT support. Contact the academy office.

If a vulnerability report shows that a security incident or personal data breach may have happened, we will manage it under our incident response, safeguarding and data protection procedures.

11. security.txt

Each of our websites publishes a security.txt file, following the RFC 9116 standard. These files give the same security contact and link back to this policy:

If this page and a security.txt file ever disagree, this page takes priority.

12. Review of this policy

The Trust Digital Lead maintains this policy. We review it every year, or sooner if our systems, security arrangements or the relevant guidance change significantly. When we review it, we also update the expiry date in each security.txt file.

Back to contents