Guidance

Vulnerability Disclosure Programme

Published 12 April 2024

Scope

This policy only applies to vulnerabilities found in Intellectual Property Office (IPO) products and services under the following conditions:

• “in scope” vulnerabilities must be original, previously unreported, and not already discovered by internal procedures

• volumetric vulnerabilities (DoS) are not in scope; this means that simply overwhelming a service with a high volume of requests will not be accepted

• reports of non-exploitable vulnerabilities and reports indicating that our services do not fully align with “best practice” (for example missing security headers) are not in scope

• TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS 1.0 support, are not in scope

This policy applies to all external parties, third party suppliers and general users of IPO public services.

Reporting

If you have discovered something you think is an in-scope security vulnerability (as listed in the Scope section), you can submit a report using the HackerOne platform. In your submission, include:

• details of the website or page where the vulnerability can be found

• a brief description of the type of vulnerability, for example, “an XSS vulnerability”

Your report should provide objective, non-destructive proof of exploitation. This helps to ensure that the report can be assessed quickly and accurately.

What to expect

After you have submitted your report, we will respond to it within five working days and aim to assess your report within 10 working days. We will keep you informed about our progress via HackerOne if you have registered for an account.

Priority for bug fixes or mitigations are assessed by looking at how complicated they are and how serious the consequences might be. Vulnerability reports might take some time to assess and address. You are welcome to enquire on the status of the process but should avoid doing so more than once every 14 days. This will allow our teams to focus on the reports.

When the reported vulnerability is resolved, or remediation work is scheduled, the Vulnerability Disclosure Team will notify you and invite you to confirm that the solution covers the vulnerability adequately.

Legalities

This policy is designed to be compatible with common vulnerability disclosure good practice. It does not give you permission to act in any manner that is inconsistent with the law, or that might cause the IPO to be in breach of any of its legal obligations, including but not limited to:

• The Computer Misuse Act (1990)

• The General Data Protection Regulation 2016/679 (GDPR) and the Data Protection Act 2018

• The Copyright, Designs and Patents Act (1988)

• The Official Secrets Act (1989).

The IPO will not seek prosecution of any security researcher who reports any security vulnerability in an IPO service or system where the researcher has acted in good faith and in accordance with this disclosure policy.

Guidance

You must not:

• access unnecessary amounts of data; two or three records are enough to demonstrate most vulnerabilities, such as an enumeration or direct object reference vulnerability

• use high-intensity invasive or destructive technical security scanning tools to find vulnerabilities

• violate the privacy of IPO users, staff, contractors, services or systems, for example, by sharing, redistributing or not properly securing data retrieved from our systems or services

• communicate any vulnerabilities or associated details using methods not described in this policy

• modify data in any IPO systems or services

• disrupt any IPO services or systems

• socially engineer, “phish”, or physically attack IPO staff or infrastructure

You must:

• securely delete all data retrieved during your research as soon as it is no longer required or within 1 month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law)

It is prohibited to disclose any vulnerabilities found in IPO systems or services to third parties or the public before the IPO has confirmed that they have been mitigated. However, this is not intended to stop you notifying third parties of a vulnerability for whom the vulnerability is directly relevant. For example, if a vulnerability being reported is in a third-party software library or framework, details of the specific vulnerability as it applies to the IPO must not be referenced in such reports.