- Top reward
- No cash rewards
- Top severity paid
- Critical
- Assets in scope
- 43
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report on HackerOne
- Submit through the program page.
- Replies within 2 days
- As the policy promises.
- No public write-ups
- Keep findings private.
Rewards
What HackerOne lists as the payout for each severity.
This program does not pay cash rewards.
- Response
-
Within 2 days
| First Response | 2 days |
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
43 assets you may test.
Wildcard domains 41
- *.21st.com Critical No bounty
- *.blueinsurance.ie Critical No bounty
- *.bristolwest.com Critical No bounty
- *.chilena.cl Critical No bounty
- *.covermore.com Critical No bounty
- *.covermore.com.au Critical No bounty
- *.da-direkt.de Critical No bounty
- *.dentolo.de Critical No bounty
- *.farmers.com Critical No bounty
- *.farmersinsurance.com Critical No bounty
- *.farmerslife.com Critical No bounty
- *.foremost.com Critical No bounty
- *.foremoststar.com Critical No bounty
- *.klinc.com Critical No bounty
- *.poweredbycovermore.com Critical No bounty
- *.rcis.com Critical No bounty
- *.sabadellproteccion.com Critical No bounty
- *.travelguard.com Critical No bounty
- *.travelguard.zurichna.com Critical No bounty
- *.zurich.at Critical No bounty
- *.zurichbank.it Critical No bounty
- *.zurich.co.ae Critical No bounty
- *.zurich.co.id Critical No bounty
- *.zurich.co.jp Critical No bounty
- *.zurich.com Critical No bounty
- *.zurich.com.ar Critical No bounty
- *.zurich.com.au Critical No bounty
- *.zurich.com.br Critical No bounty
- *.zurich.com.cn Critical No bounty
- *.zurich.com.hk Critical No bounty
- *.zurich.com.my Critical No bounty
- *.zurich.com.sg Critical No bounty
- *.zurich-connect.at Critical No bounty
- *.zurich.co.uk Critical No bounty
- *.zurich.de Critical No bounty
- *.zurichempresas.es Critical No bounty
- *.zurich.es Critical No bounty
- *.zurich.it Critical No bounty
- *.zurichkotak.com Critical No bounty
- *.zurichna.com Critical No bounty
- *.zurichseguros.com.ec Critical No bounty
Products and areas 2
- Farmer's Insurance Critical No bounty
- Zurich Insurance Critical No bounty
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Zurich Insurance (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Please provide detailed reports with reproducible steps.
-
Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
-
Social engineering (e.g. phishing, vishing, smishing) is prohibited.
-
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
-
Only interact with accounts you own or with explicit permission of the account holder.
Not accepted
-
Clickjacking on pages with no sensitive actions
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
-
Attacks requiring MITM or physical access to a user's device.
-
Previously known vulnerable libraries without a working Proof of Concept.
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
-
Missing best practices in SSL/TLS configuration.
-
Any activity that could lead to the disruption of our service (DoS).
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Rate limiting or bruteforce issues on non-authentication endpoints
-
Missing best practices in Content Security Policy.
-
Missing HttpOnly or Secure flags on cookies
-
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
-
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
-
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
-
Tabnabbing
-
Issues that require unlikely user interaction
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 45 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope added
*.zurich.com.cn
-
Scope added
*.zurich.com.sg
-
Scope removed
*.formoststar.com
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.
Original policy
Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
At Zurich Insurance, we recognize the importance of information security and the need to protect our customers' sensitive data. As a leading provider of insurance and risk management solutions, we are responsible for ensuring that our systems and technologies are robust and resilient against cyber threats. To achieve this goal, we have established a Vulnerability Disclosure Program (VDP) designed to encourage responsible disclosure of security vulnerabilities by external hackers and security professionals. Through our VDP, we invite individuals and organizations to report potential security vulnerabilities in our systems and products, allowing us to address these issues promptly and effectively and ensuring our services' continued security and integrity.
Response Targets
Zurich Insurance will make a best effort to meet the following SLAs for hackers participating in our program:
| Type of Response | SLA in business days |
|---|---|
| First Response | 2 days |
| Time to Triage | 2 days |
| Time to Resolution | depends on severity and complexity |
We’ll try to keep you informed about our progress throughout the process.
Disclosure Policy
- As this is a private program, please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
- Do be specific
- Do provide a detailed and complete submission (masking or encrypting if necessary)
- Do reference existing vulnerability information where relevant
- Follow HackerOne's disclosure guidelines.
Program Rules
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
- Submit one vulnerability per report, unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only triage the first report that was received (provided that it can be fully reproduced).
- Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.
Out of scope vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
- Clickjacking on pages with no sensitive actions
- Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
- Attacks requiring MITM or physical access to a user's device.
- Previously known vulnerable libraries without a working Proof of Concept.
- Comma Separated Values (CSV) injection without demonstrating a vulnerability.
- Missing best practices in SSL/TLS configuration.
- Any activity that could lead to the disruption of our service (DoS).
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- Rate limiting or bruteforce issues on non-authentication endpoints
- Missing best practices in Content Security Policy.
- Missing HttpOnly or Secure flags on cookies
- Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
- Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
- Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
- Tabnabbing
- Issues that require unlikely user interaction
- Findings involving exposed documents marked as "Internal Use Only" are considered out of scope unless the documents contain Personal Identifiable Information (PII).
Confidentiality
You must treat all information about our systems, staff or customers that comes into your possession or that you otherwise become aware of, which is not publicly available, as strictly confidential and not share or otherwise use it for any purpose other than submitting it to us as a submission as described above.
Thank you for helping keep Zurich Insurance and our users safe!