Skip to content

nidirect.gov.uk

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

Accepting reports security.txt
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
1
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.
Partial safe harbor
Some legal protection; read the terms.
Replies within 5 days
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.

Pays cash
No You will not be paid a reward for reporting a vulnerability (known as a ‘bug bounty’).
Response
Within 5 days After you have submitted your report, we will respond to your report within 5 working days and aim to triage your report within 10 working days.
Safe harbor
Partial However, if legal action is initiated by a third party against you and you have complied with this policy, we can take steps to make it known that your actions were conducted in compliance 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

1 asset you may test.

Domains 1

  • nidirect.gov.uk

Rules

What the policy asks of you, and the bug types it won't reward, quoted from nidirect.gov.uk's policy. "We" in these lines means the program, not this site.

While testing

  • Please do not share the vulnerability information beyond the owner and us, without express consent from the owner.
  • Break any applicable law or regulations.
  • Access unnecessary, excessive or significant amounts of data.
  • Modify data in the Organisation's systems or services.
  • Use high-intensity invasive or destructive scanning tools to find vulnerabilities.
  • Attempt or report any form of denial of service, e.g. overwhelming a service with a high volume of requests.
  • Disrupt the Organisation's services or systems.
  • Social engineer, ‘phish’ or physically attack the Organisation's staff or infrastructure.
  • Demand financial compensation in order to disclose any vulnerabilities.
  • 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).

Not accepted

  • Submit reports detailing TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS1.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 12 Nov 2026. Last checked 3 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.