Skip to content
EterShield

Responsible disclosure

Acknowledgements and responsible disclosure

If you found a vulnerability in EterShield, thank you for telling us. Here are the rules, what we promise in return and the list of people who have helped.

How to report

Write to security@etershield.com with the subject [SECURITY]. Whenever possible, include:

  • a description of the vulnerability and its possible impact
  • the steps to reproduce it
  • the affected addresses or components
  • the version or date you tested

security@etershield.com

Use only your own test accounts. Never test with real customer data.

For sensitive reports, you can encrypt your email with our public PGP key. Check the fingerprint before using it.

Key fingerprint: 76F1 C5B4 3C91 AB3E 8B47 6A82 20FD 7748 293F 7570

Download the public key

What we promise

  • Acknowledge receipt of the report within 2 business days.
  • Give an initial assessment within 5 business days.
  • Take no legal action against anyone who acts in good faith and follows this policy.
  • Keep the person informed about the progress of the fix.
  • Publicly acknowledge relevant contributions, with their consent.

Deadlines by severity

Deadlines by severity
Severity (CVSS 3.1)AcknowledgementTarget fix
Critical (9.0 to 10.0)24 hours15 days
High (7.0 to 8.9)2 business days30 days
Medium (4.0 to 6.9)5 business days90 days
Low (0.1 to 3.9)5 business daysNext release cycle

Fix deadlines may be adjusted with notice to the reporter, for example when the fix requires architectural changes.

What is in and out of scope

In scope: the *.etershield.com addresses (the application, the public API and the Trust Center pages) and *.etergrowth.com.

Out of scope:

  • denial of service attacks
  • social engineering against staff or customers
  • physical access to premises
  • known vulnerabilities in third-party components with no demonstrable exploit in EterShield
  • tests against real customer data

Coordinated disclosure

We ask for 90 days, or until the fix is confirmed (whichever comes first), before any public disclosure of the technical detail, to protect customers.

Open the full policy (opens in a new tab)

The full policy, with the severity criteria, is in the public documentation.

Acknowledgements

No acknowledgements have been published yet. When someone reports a valid vulnerability and allows a mention, their name (or pseudonym) and the month will appear here.

See the security.txt