Vulnerability Disclosure Policy

Homepage Vulnerability Disclosure Policy

Scope

Witekio welcomes responsible disclosure of vulnerabilities in any of our products or services. Researchers who submit a vulnerability report to us will be given full credit on our website once the submission has been accepted and validated by our security team.

Please refrain from any wider publication until Witekio agrees to wider publication, which may need to wait until a security patch has been successfully rolled out and affected customers protected.

Legal Posture

Witekio will not engage in legal action against individuals who submit vulnerability reports through our Vulnerability Reporting Form. We agree not to pursue legal action against individuals who:

  • Engage in testing of systems/research without harming Witekio or its customers.
  • Test on products without affecting customers, or receive permission/consent from customers before engaging in vulnerability testing against their devices/software, etc.
  • Adhere to the laws of their location and the locations of Witekio. For example, violating laws that would only result in a claim by Witekio (and not a criminal claim) may be acceptable as Witekio is authorizing the activity (reverse engineering or circumventing protective measures) to improve its system.
  • Refrain from disclosing vulnerability details to the public before a mutually agreed-­upon timeframe expires

How to submit a vulnerability

Our contact details can be found in the file security.txt, which contains the email address security@witekio.com and our GPG public key which you can use to encrypt information about the vulnerability.

Preference, Prioritization, and Acceptance Criteria

We will use the following criteria to prioritize and triage submissions.

What we would like to see from you:

  • Well-­written reports in English, French, or German will have a higher chance of resolution.
  • Reports that include proof-­of-­concept code equip us to better triage.
  • Reports that include only crash dumps or other automated tool output may receive lower priority.
  • Please include how you found the bug, its impact, and any potential remediation.
  • Please include any plans or intentions for public disclosure.

What you can expect from us:

  • A timely response to your email (within 7 business days).
  • After triage, we will send an expected timeline and commit to being as transparent as possible about the remediation timeline as well as on issues or challenges that may extend it.
  • An open dialog to discuss issues.

  • Notification when the vulnerability analysis has completed each stage of our review.

  • Credit after the vulnerability has been validated and fixed.

If we are unable to resolve communication issues or other problems, Witekio may bring in a neutral third party (such as CERT/CC, ICS-­‐CERT, or the relevant regulator) to assist in determining how best to handle the vulnerability.

Reported Vulnerability Disclosures

  • Dave J (cmd.123457@gmail.com):

DNSSEC wasn’t enabled for our website.
DNSSEC records prevent third parties from forging the records that guarantee a domain’s identity.