- 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.
- 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.
- Safe harbor
-
Full
Idura is committed to not pursuing legal action against security researchers who report vulnerabilities in accordance with this Policy and act in good faith.
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
- All Idura products and services
Out of scope (3)
- electronic identification means providers
- external service providers
- Non-production systems provided by Idura
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Idura's policy. "We" in these lines means the program, not this site.
While testing
-
We ask you to only execute proofs of concept against resources in tenants owned by your own account.
-
Please make sure you always select "No, I am here for the vulnerability bounty program" in the "Are you joining an existing project" dropdown.
-
Please use the same email address for setting up an account as the one you will send your report from.
-
Never attempt to gain access to another user's account or data.
-
Never attempt a proof of concept against another user's account or resources.
-
Never attempt a proof of concept of a denial of service attack.
-
Not exploit the vulnerability or problem you have discovered beyond what is strictly necessary to demonstrate its existence, and refrain from downloading, deleting, or modifying data belonging to others.
-
Allow our security team reasonable time to resolve any issues you have found before publicly announcing them.
-
Please refrain from submitting LLM-generated reports.
-
If the vulnerability was found by an automated tool, please do not report it to us unless you have manually validated the proof of concept yourself.
Not accepted
-
Volumetric/Denial of Service vulnerabilities.
-
Vulnerabilities requiring physical access to a user's device.
-
Self-XSS.
-
Social engineering attacks.
-
Physical security attacks.
-
Brute force attacks on cryptography.
-
Clickjacking with no demonstrated security impact.
-
JavaScript warnings with no demonstrated security impact.
-
Known CVEs without a demonstrated proof of concept.
-
Open ports with no demonstrated security impact.
-
Vulnerabilities affecting outdated browser/platform versions.
-
Outdated libraries with no demonstrated security impact.
-
Missing security headers with no demonstrated security impact.
-
Application error codes (e.g. HTTP 500) with no demonstrated security impact.
-
Lack of adherence to best practices with no demonstrated security impact.
-
Unexploitable vulnerabilities.
-
Disclosure of information with no demonstrated security impact.
-
Subdomain takeover with no demonstrated proof of concept.
-
Vulnerabilities that have recently been publicly disclosed (30 days or less).
-
Vulnerabilities caused by deliberate misconfiguration of our products.
-
Exploitation of generic operating system vulnerabilities.
-
Vulnerabilities in our customers' systems or integrations.
-
Vulnerabilities in non-production systems.
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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.