Responsible disclosure policy

Roseman Labs B.V. (hereafter: Roseman Labs) is formalizing its policy for accepting vulnerability reports in our products. We hope to foster an open dialogue with the security community. The work the community does is important to ensure safety for all our customers.

Program and Scope
Roseman Labs’s Vulnerability Disclosure Program initially covers the following products:

  • Cranmera MPC engine
  • Virtual Data Lake software suite (input-module, privacy engine, analysis interface)
  • Roseman Labs' Website
  • Roseman Labs cloud (SaaS API and gateway)

While Roseman Labs develops several other products, we ask that all security researchers submit vulnerability reports only for the stated product list. We intend to increase our scope as we build capacity and experience with this process.

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 product security team.

Legal posture

We Will Not Take Legal Action If...
Roseman Labs will not engage in legal action against individuals who submit vulnerability reports through our email address security <at sign> rosemanlabs <dot> com. We openly accept reports for the scope described above.

We do not to pursue legal action against individuals who:

  • Test systems without harming Roseman Labs or its customers.
  • Test within the scope of our vulnerability disclosure program.
  • Test without affecting customers service, i.e. by DDoS-ing or engaging APIs/ports with traffic levels similar to DDoS.
  • Test with permission/consent from customers before engaging in vulnerability testing against their devices/ software, etc.
  • Adhere to the laws of their location and the location of Roseman Labs (The Netherlands). For example, violating laws that would only result in a claim by Roseman Labs (and not a criminal claim) may be acceptable as Roseman Labs 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.

Communication mechanisms and process

How to Submit a Vulnerability
To submit a vulnerability report to Roseman Labs’s Security Team, please email security <at sign> rosemanlabs <dot> com.

The use of a well written report is appreciated. A sample report form can be found here.

Submission prioritization

Preference, Prioritization, and Acceptance Criteria
We will use the following criteria to prioritize and triage submissions:

  • Well-written reports in English 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.
  • Reports that include products not on the initial scope list may receive lower priority.
  • Please include how you found the bug, the 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 1-5 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, we may bring in a neutral third party (such as a CERT, or the relevant regulator) to assist in determining how best to handle the vulnerability.