Guardian360
By Guardian360 B.V. Bug bounty on Self-hosted guardian360.net
- Top reward
- €300
- 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.
- Pays up to €300
- top reward.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 7 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.
The policy page has no reward table. Here is what it says, in its own words.
- Top reward
-
€300
Depending on the severity of the security issue and the quality of the report, this reward can range from a T-shirt to a maximum of 300 euros’ worth of gift vouchers.
- Response
-
Within 7 days
Guardian360 will respond to a report within 7 working days with an assessment of the report and an expected date for a solution.
- Safe harbor
-
Full
If you comply with the above conditions when reporting a vulnerability in a Guardian360 ICT system, Guardian360 will not impose any legal consequences on this notification.
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.
Domains 1
- guardian360.net
Products and areas 1
- Guardian360's ICT systems
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Guardian360's policy.
While testing
-
Do not share the information about the security issue with others until it is resolved.
-
Handle the knowledge about the security issue responsibly by refraining from actions beyond what is necessary to demonstrate the security problem.
-
Placing malware.
-
Copying, modifying, or deleting data in a system (an alternative is to create a directory listing of a system).
-
Making changes to the system.
-
Repeatedly gaining access to the system or sharing access with others.
-
Using the so-called “brute force” method to gain access to systems.
-
Using denial-of-service or social engineering techniques.
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 6 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.