- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 3
- 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
we do not offer monetary rewards for vulnerability disclosures.
- Response
-
Within 5 days
we will respond within 5 working days
- Safe harbor
-
Partial
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
3 assets you may test.
Domains 3
- gov.scot
- mygov.scot
- scotland.gov.uk
Rules
What the policy asks of you, and the bug types it won't reward, quoted from gov.scot's policy.
While testing
-
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
-
communicate any vulnerabilities or associated details other than by means described in the published security.txt
-
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
Not accepted
-
TLS configuration weaknesses, for example “weak” cipher suite support or the presence of TLS 1.0 support
-
any form of denial of service
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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.