Effective August 24, 2021 and last updated October 11, 2024

 

Introduction

Kumi Analytics is committed to ensuring the security of our customers and partners by protecting their information from unwarranted disclosure. 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 want security researchers to feel comfortable reporting vulnerabilities they've discovered – as set out in this policy – so we can fix them and keep our users safe. We have developed this policy to reflect our values and uphold our sense of responsibility to security researchers who share their expertise with us in good faith.

​

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 Kumi Analytics 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 command line access and/or persistence, 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.

• You do not intentionally compromise the privacy or safety of Kumi Analytics personnel or any third parties.

• You do not intentionally compromise the intellectual property or other commercial or financial interests of any Kumi Analytics personnel or entities, or any third parties.

 

Scope

All systems and services associated with domains listed below are in scope. Likewise, subdomains of each listing, unless explicitly excluded, are always in scope. Additionally, any website published with a link to this policy shall be considered in scope. Vulnerabilities found in non-federal 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 or endpoint is in scope or not, contact support@kumianalytics.com before starting your research.

 

Rules of Engagement

Security researchers must not:

• Test any system other than the systems set forth in the 'Scope' section above

• Disclose vulnerability information except as set forth in the 'Reporting a Vulnerability' and 'Disclosure' sections below

• Engage in physical testing of facilities or resources

• Engage in social engineering

• Send unsolicited electronic mail to Kumi Analytics users, including "phishing" messages

• Execute or attempt to execute "Denial of Service" or "Resource Exhaustion" attacks

• Introduce malicious software

• Test third-party applications, websites, or services that integrate with or link to or from Kumi Analytics' systems

• Delete, alter, share, retain, or destroy Kumi Analytics' data, or render Kumi Analytics' data inaccessible

 

Reporting a Vulnerability

We accept vulnerability reports at support@kumianalytics.com. Reports may be submitted anonymously. We do not support PGP-encrypted emails at this time.

Information submitted under this policy will be used for defensive purposes only – to mitigate or remediate vulnerabilities.

 

Disclosure

Kumi Analytics 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 versus decreases risk. Accordingly, we require that you refrain from sharing information about discovered vulnerabilities for 180 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.

​

Questions

Questions regarding this policy may be sent to legal@kumianalytics.com. We also invite you to contact us with suggestions for improving this policy.