Skip to content

Government of Netherlands

By Government of the Netherlands Vulnerability disclosure program on Self-hosted government.nl

Accepting reports Full safe harbor
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.
Report by email
[email protected]
Full safe harbor
Good-faith research is authorised; no legal action.
Replies within 3 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.

Response
Within 3 days The government will respond to your notification within three working days.
Safe harbor
Full If you do so, the government will not attach any legal consequences to your notification.
Hall of fame
Yes The government can, if you wish, mention your name as the one who discovered the security flaw.

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, 3 excluded.

Products and areas 1

  • ICT system belonging to central government
Out of scope (3)
  • an organisation with a vital function (such as an energy or telecoms company)
  • another government body (such as a municipality or province)
  • ICT systems outside central government

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Government of Netherlands's policy.

While testing

  • Report a vulnerability via a CVD-report form to the National Cyber Security Centre (NCSC).
  • Do not share any information about the flaw with others until it has been remedied.
  • Do nothing beyond what is necessary to demonstrate the security flaw.
  • Send malware;
  • Copy, change, or delete data in the ICT system concerned (as an alternative, you can create a directory listing of the system);.
  • Change the system;
  • Repeatedly visit the system or share access with others;
  • Use ‘brute force’ to open the system;
  • Try denial of service or social engineering.

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 5 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.