Skip to content

Office for National Statistics (ONS)

Vulnerability disclosure program on security.txt ons.gov.uk

Accepting reports Full safe harbor security.txt
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
2
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 1 day
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Response
Within 1 days After you have submitted your report, we will acknowledge it within 1 working day and aim to find a resolution within 30 working days.
Safe harbor
Full The ONS will not seek prosecution of any security researcher who reports a security vulnerability in an ONS service or system, where the researcher has acted in good faith and in accordance with this policy.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

2 assets you may test, 3 excluded.

Domains 1

  • ons.gov.uk

Products and areas 1

  • ONS services and systems
Out of scope (3)
  • reports of non-exploitable vulnerabilities or indicating that our services do not fully align with “best practice”, for example, missing security headers
  • TLS configuration weaknesses, for example, “weak” cipher suite support or the presence of TLS 1.0 support
  • volumetric vulnerabilities, for example, simply overwhelming a service with a high volume of requests

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Office for National Statistics (ONS)'s policy. "We" in these lines means the program, not this site.

While testing

  • 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 ONS users, staff, contractors, services or systems, for example, by sharing, redistributing and/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 ONS systems or services
  • disrupt any ONS services or systems
  • socially engineer, “phish”, or physically attack ONS staff or infrastructure
  • You must also not disclose any vulnerabilities in ONS systems or services to third parties or the public before the ONS has confirmed that they have been mitigated or rectified.

Not accepted

  • volumetric vulnerabilities, for example, simply overwhelming a service with a high volume of requests
  • reports of non-exploitable vulnerabilities or indicating that our services do not fully align with “best practice”, for example, missing security headers
  • TLS configuration weaknesses, for example, “weak” cipher suite support or the presence of TLS 1.0 support

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 2 hours ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.