As the leading provider of IT and security management solutions for managed service providers (MSPs) and small to medium sized businesses, we welcome security researchers and the public to help improve our security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of our products, we want to hear from you. This policy outlines steps for reporting vulnerabilities to us, what we expect and what you can expect from us.
When adhering to this policy, you can expect us to:
- Extend Safe Harbor for your vulnerability research that is related to this policy.
- Respond to your report promptly, and work with you to understand and validate your report;
- Work to remediate discovered vulnerabilities in a timely manner, within our operational constraints.
To encourage good-faith vulnerability research and avoid any confusion, we expect that you:
- Play by the rules so both you and Kaseya have a great experience working together. If there is any inconsistency between this policy and any other applicable terms, the terms of this policy will prevail;
- Report any vulnerability you have discovered promptly;
- Use only the Official Channels to discuss vulnerability information with us;
- Provide us a reasonable amount of time to resolve the issue before you disclose it publicly (we try to resolve issues within 90 days from the initial report);
- Perform testing only on in-scope systems, and respect systems and activities that are out-of-scope;
- Limit the amount of data that you access to the minimum required for effectively demonstrating a Proof of Concept and do not remove any data from the system under test;
- Avoid violating the privacy of others, disrupting our systems, destroying data, and/or harming user experience;
- Cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information;
- Only interact with test accounts that you own or accounts that you explicit permission from the account holder to use; and
- Do not engage in extortion.
When conducting vulnerability research, according to this policy, we consider this research conducted under this policy to be:
- Authorized concerning any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy;
- Authorized concerning any relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls;
- Exempt from restrictions in our Terms of Service (TOS) and/or Acceptable Usage Policy (AUP) that would interfere with conducting security research, and we waive those restrictions on a limited basis; and/li>
- Lawful, helpful to the overall security of the Internet, and conducted in good faith.
You are expected, as always, to comply with all applicable laws. If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.
* Please submit all vulnerability information to this program (steps to reproduce, a working proof of concept, and how the issue impacts Kaseya)
* If you have any questions regarding this policy, scope, or how to work with us, you can contact us at [email protected]
Systems in Scope
This policy applies to any services, products, or web properties that are owned or operated by Kaseya, including the following domains:
Out of Scope
This policy does not give authorization to test Kaseya software hosted by third parties without explicit authorization by the third party. Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.
- Clickjacking on pages with no sensitive actions
- Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
- Attacks requiring MITM or physical access to a user’s device
- Previously known vulnerable libraries without a working Proof of Concept
- Comma Separated Values (CSV) injection without demonstrating a vulnerability
- Missing best practices in SSL/TLS configuration
- Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
- Any activity that could lead to the disruption of our service (DoS), including but not limited to, inundating support services with invalid requests.
- Bruteforce oracle attacks against unauthenticated endpoints
- Missing best practices in Content Security Policy
- Missing HttpOnly or Secure flags on cookies
- Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
- Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
- Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g., stack traces, application or server errors)
- Issues that require unlikely user interaction by the victim