Coordinated Vulnerability Disclosure (CVD)

Introduction

This Coordinated Vulnerability Disclosure (CVD) policy applies to any vulnerabilities you are considering reporting to Dendi, Inc. (the "organization") so long as the organization's website has a published security.txt file that references this policy.

We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always acting in compliance with it.

We value those who take the time and effort to report security vulnerabilities according to this policy. However, we do not offer monetary rewards for vulnerability disclosures. We do have a 'Acknowledgements' page.

Reporting

If you believe you have found a security vulnerability relating to the organization's system, please do the following:

• E-mail your report to [email protected]
• If you need to send sensitive data, such as PHI, let us know over email. We will coordinate with you to setup an encrypted communication method for sending us the data.
• Include details to reproduce the issue in your report:
  • The website, IP, or page where the vulnerability can be observed.
  • A brief description of the type of vulnerability, for example; "XSS vulnerability".
  • Steps to reproduce. These should be a benign, non-destructive, proof of concept. This helps to ensure that the report can be triaged quickly and accurately. It also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain takeovers.

Guidance

You must NOT:

• Report issues that are 'out of scope'
• Transmit any of the organization's data in plain text, especially PHI data
• Take advantage of the vulnerability or problem you have discovered
• Reveal the problem to others until it has been resolved
• Break any applicable law or regulations
• Access unnecessary, excessive or significant amounts of data
• Modify data in the organization's systems or services
• Use high-intensity invasive or destructive scanning tools to find vulnerabilities
• Attempt or report any form of denial of service, e.g. overwhelming a service with a high volume of requests
• Disrupt the organization's services or systems
• Social engineer, 'phish', or physically attack the organization's staff or infrastructure
• Submit reports detailing non-exploitable vulnerabilities, or reports indicating that the services do not fully align with "best practice", for example missing security headers.
• Submit reports detailing TLS configuration weaknesses, for example "weak" cipher suite support or the presence of TLS1.0 support
• Demand financial compensation in order to disclose any vulnerabilities

You must:

• Always comply with data protection rules and must not violate the privacy of any data the organization holds. You must not, for example, share, redistribute or fail to properly secure data retrieved from the systems or services.
• Securely delete all data retrieved during your research as soon as it is no longer required or within 1 month of the vulnerability being resolved, whichever occurs first (or as otherwise required by data protection law).

What to expect

If you have followed the instructions above, we will not take any legal action against you in regard to the report. We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission

After you have submitted your report, we will respond to your report within 3 business days. We'll aim to keep you informed of our progress. We will notify you when the reported vulnerability is remediated, and you may be invited to confirm that the solution covers the vulnerability adequately.

Once your vulnerability has been resolved, we welcome requests to disclose your report. We'd like to unify our guidance, so please do continue to coordinate public release with us. We will give you credit and brief description of the vulnerability on our Acknowledgements page. We will reach out to you for your desired name to be credited as, and one (1) accompanying link to a site of your choice. Ex: your Twitter, Stack Overflow, or GitHub profile.

Scope

While we strive to secure all our operations, some systems are more critical than others. The best place to start testing and reporting vulnerabilities are the following systems:

• LIS
• LIS API

Our Wordpress site is not critical to our business operations and contains no private data or escalated rights. While we still want to hear about major problems on the Wordpress site, please keep in mind that Wordpress vulnerability reports will always be considered 'low priority'.

Out of Scope

To help keep our attention focused on the important issues, and so you don't waste your time in your research, we'll list of few things that are specifically 'out of scope':

• XSS or CSRF in a domain without an authenticated experience
• XMLRPC files on Wordpress
• Non-exploitable vulnerabilities
• Reports indicating that the services do not fully align with "best practice", for example missing security headers.
• Reports detailing TLS configuration weaknesses, for example "weak" cipher suite support or the presence of TLS1.0 support

Legalities

This policy is designed to be compatible with common vulnerability disclosure good practice. It does not give you permission to act in any manner that is inconsistent with the law, or which might cause the organization or partner organizations to be in breach of any legal obligations.

Acknowledgements

We do not have a formal bug bounty or swag program right now. We have an "Acknowledgements" page where we would like to thank and acknowledge the efforts of security researchers that have reached out to us:

Acknowledgements/Thanks