EterShieldDocs
etershield.com
PTLog in
Trust and security/Security

Responsible Vulnerability Disclosure Policy (VDP)

Version: 1.4 Date: 8 November 2026 Owner: Security Officer (CTO), Eter Growth, Lda. Related control: NIST CSF 2.0 ID.RA-08: "Processes for receiving, analyzing, and responding to vulnerability disclosures are established". Regulatory alignment: Contributes to the "secure by design" requirement of the CRA (Cyber Resilience Act) and to COM(2026) 577 (EU Action Plan on Cybersecurity and AI), which requires coordinated vulnerability disclosure (CVD) processes as a baseline control.

1. Commitment

Eter Growth welcomes and encourages the responsible reporting of security vulnerabilities found in EterShield and in the company's other products and services. We commit to:

  • Acknowledge receipt of any report within 2 business days.
  • Provide an initial assessment (validation/triage) within 5 business days.
  • Not take legal action against researchers who act in good faith and respect this policy ("safe harbor").
  • Keep the researcher informed about the progress of remediation.
  • Publicly acknowledge (with the researcher's consent) relevant contributions.

2. Scope

The following are within the scope of this policy:

  • *.etershield.com (application, public API, Trust Center portal /trust/[slug])
  • *.etergrowth.com
  • Production infrastructure operated by Eter Growth (the application production server and the WAF, SOC and AI proxy server, both dedicated and in France) to the extent that it is accessed through the domains above

The following are out of scope:

  • Denial-of-service attacks (DoS/DDoS)
  • Social engineering against employees or customers (phishing, vishing)
  • Physical access to premises
  • Vulnerabilities in third-party dependencies that are already publicly known and have no demonstrable exploit in the context of EterShield
  • Testing against real customer data: use only your own test accounts

3. How to report

Dedicated email: security@etershield.com (subject: [SECURITY])

Include, whenever possible:

  1. Description of the vulnerability and potential impact
  2. Steps to reproduce (proof of concept)
  3. Affected URLs, endpoints or components
  4. Version/date of testing

PGP encryption is available upon prior request for highly sensitive reports.

4. Response and remediation SLA

Severity (CVSS 3.1) Acknowledgement Target fix
Critical (9.0-10.0) 24h 15 days
High (7.0-8.9) 2 business days 30 days
Medium (4.0-6.9) 5 business days 90 days
Low (0.1-3.9) 5 business days Next release cycle

Fix deadlines may be adjusted by notifying the researcher, in particular where the fix involves architectural changes.

5. Coordinated disclosure

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

6. Internal vulnerability detection processes (provider side)

In addition to receiving external reports, Eter Growth runs internal processes to detect and manage technical vulnerabilities in EterShield itself: monitoring of vulnerabilities in third-party components, automated code security analysis and an application firewall. These processes do not replace this policy, which remains the channel for reports from external researchers.

As a complementary transparency channel, Eter Growth also publishes an institutional Trust Center, with information on the organization's security, compliance and data practices.

EterShield, an Eter Growth platform