Skip to content

Security: datasciencecampus/ons-github-app

SECURITY.md

Security Notice

Overview (Public Version)

This document explains how security vulnerabilities should be reported to ONS. Our cyber security and information assurance teams assess and triage all reported issues.

Public scope: Vulnerability disclosure guidance for external reporters. Internal operational incident handling details have been intentionally omitted.

Reporting a Vulnerability

ONS advocates responsible vulnerability disclosure. If you've found a vulnerability, we would like to know so we can fix it. Please report potential vulnerabilities through the following channels:

When reporting a vulnerability to us, please include:

  • the website, page or repository where the vulnerability can be observed
  • a brief description of the vulnerability
  • details of the steps we need to take to reproduce the vulnerability
  • non-destructive exploitation details

If you are able to, please also include:

  • the type of vulnerability, for example, the OWASP category
  • screenshots or logs showing the exploitation of the vulnerability

If you are not sure if the vulnerability is genuine and exploitable, or you have found:

  • a non-exploitable vulnerability
  • something you think could be improved - for example, missing security headers
  • TLS configuration weaknesses - for example weak cipher suite support or the presence of TLS1.0 support Then you can still reach out via email.

Guidelines for Reporting a Vulnerability

When investigating and reporting a vulnerability on an ONS domain or subdomain, you must not:

  • break the law
  • access unnecessary or excessive amounts of data
  • modify data
  • use high-intensity invasive or destructive scanning tools to find vulnerabilities
  • try a denial of service - for example overwhelming a service on GOV.UK with a high volume of requests
  • disrupt ONS's services or systems
  • tell other people about the vulnerability you have found until we have disclosed it
  • social engineer, phish or physically attack our staff or infrastructure
  • demand money to disclose a vulnerability

Only submit reports about exploitable vulnerabilities through HackerOne.

Bug Bounty

ONS does not offer a paid bug bounty programme. Responsible disclosure is appreciated and helps improve security for everyone.

Code of Conduct

Please also review our contributor Code of Conduct: CODE_OF_CONDUCT.md

Further reading and inspiration about responsible disclosure and SECURITY.md


Internal Staff (Summary)

Internal operational security incidents (IT, personnel, physical) should be reported via the organisation's internal ticketing and escalation processes. Staff must follow internal policies and guidance available on the intranet. (Detailed internal steps, categories, contact numbers and hours are intentionally excluded from this public version.)

There aren’t any published security advisories