DEKA Research & Development Corporation

Vulnerability Disclosure Policy

January 2024

Introduction

DEKA Research & Development is committed to ensuring the security of its software, services and products. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.

This policy describes what systems and types of research are covered under this policy, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.

We encourage you to contact us to report potential vulnerabilities in our systems.

Authorization

If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized we will work with you to understand and resolve the issue quickly, and DEKA will not recommend or pursue legal action related to your research.

Guidelines

Under this policy, “research” means activities in which you:

• • Notify us as soon as possible after you discover a real or potential security issue.
  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
  • Only use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
  • Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
  • Do not submit a high volume of low-quality reports.

Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.

Test Methods

The following test methods are not authorized:

• • Test any system other than the systems set forth in the ‘Scope’ section;
  • Disclose vulnerability information except as set forth in the ‘Reporting a Vulnerability’ section below;
  • Engage in physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing;
  • Send unsolicited electronic mail to DEKA users, including “phishing” messages;
  • Execute or attempt to execute “Denial of Service” or “Resource Exhaustion” attacks or introduce malicious software;
  • Test in a manner known to degrade the operation of DEKA systems; or intentionally impair, disrupt, or disable DEKA systems;
  • Test third-party applications, websites, or services that integrate with or link to or from DEKA systems;
  • Delete, alter, share, retain, or destroy DEKA data, or render DEKA data inaccessible; or,
  • Use an exploit to exfiltrate data, establish command line access, establish a persistent presence on DEKA systems, or “pivot” to other DEKA systems.

Security researchers may:

• • View or store DEKA nonpublic data only to the extent necessary to document the presence of a potential vulnerability.

Security researchers must:

• • Cease testing and notify us immediately upon discovery of a vulnerability,
  • Cease testing and notify us immediately upon discovery of an exposure of nonpublic data, and
  • Purge any stored DEKA nonpublic data upon reporting a vulnerability.

Scope

This policy applies to the following systems and services:

DEKA-managed software embedded in, utilized by, or used in connection with operation of DEKA medical devices, that is available from the internet.

Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities found in systems from our vendors fall outside of this policy’s scope and should be reported directly to the vendor according to their disclosure policy (if any). If you aren’t sure whether a system is in scope or not, contact us at cybersec@dekaresearch.com.

Though we develop and maintain other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you think merits testing, please contact us to discuss it first. We may adjust the scope of this policy over time, and may amend or terminate this policy at any time.

Reporting a Vulnerability

DEKA is committed to timely correction of vulnerabilities. However, we recognize that public disclosure of a vulnerability in absence of a readily available corrective action likely increases rather than decreases risk. Accordingly, we require that you refrain from sharing information about discovered vulnerabilities for 90 calendar days after you have received our acknowledgement of receipt of your report. If you believe others should be informed of the vulnerability prior to our implementation of corrective actions, we require that you coordinate in advance with us.

Information submitted under this policy will be used for defensive purposes only – to mitigate or remediate vulnerabilities. If your findings include newly discovered vulnerabilities that affect all users of a product or service and not solely DEKA, we may share your report with the appropriate vendors or government agencies. We will not share your name or contact information without express permission.

We accept vulnerability reports at cybersec@dekaresearch.com. Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days.

By submitting a vulnerability, you acknowledge that you have no expectation of payment and that you expressly waive any future pay claims against the DEKA or its affiliates related to your submission.

What we would like to see from you

In order to help us triage and prioritize submissions, we recommend that your reports:

• • Describe the location the vulnerability was discovered and the potential impact of exploitation.
  • Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
  • Be in English, if possible.

What you can expect from us

When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.

• • Within 3 business days, we will acknowledge that your report has been received.
  • To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.
  • We will maintain an open dialogue to discuss issues.

Questions

Questions regarding this policy may be sent to cybersec@dekaresearch.com. We also invite you to contact us with suggestions for improving this policy. Please contact us prior to conducting research if you are unsure if a specific test method is inconsistent with or unaddressed by this policy.