RocketCyber Terms of Use

August 1, 2025

These RocketCyber Terms of Use (“Terms“) govern your organization’s (“you,” “your” or “Customer”) use of Kaseya’s RocketCyber services (“RocketCyber” or “Services”). By purchasing or using RocketCyber, you agree to be bound by these Terms, which are incorporated into the Kaseya Master Agreement accessible here or such other master agreement (the “Agreement”) between you and the Kaseya entity from which you purchase Products (“Kaseya”). Capitalized terms not defined in these Terms have the meaning given to them in the Agreement. In the event of a conflict between the Agreement and these Terms, these Terms will take precedence with respect to RocketCyber.

  1. Definitions

In addition to the definitions set forth in the Master Agreement, the following definitions shall apply.

Alerts” means information generated through the RocketCyber platform and related to indicators of compromise.  RocketCyber documentation sometimes refers to Alerts as “Incidents.”

Alert Contact(s)” means personnel whom you have listed in the RocketCyber platform to be contacted in the event of an Alert.

Covered Endpoints” means a Supported Endpoint to which you have assigned an active RocketCyber License.

Covered M365 Account” means an active, licensed Microsoft 365 user account belonging to a Microsoft 365 tenant that is connected to the RocketCyber platform.

Endpoint” means a desktop, laptop, firewall or server.

Event” means a time-stamped occurrence generated by the RocketCyber platform and/or Microsoft 365, and that signifies a specific action or state of change.

Incoming Communication” means telephone calls or emails placed by your organization to the RocketCyber SOC.

Outgoing Communication” means telephone calls, emails or text messages placed by the RocketCyber SOC to your Alert Contact(s).

SOC” means Security Operations Center.

Supported Applications” are applications that are a type for which Kaseya provides RocketCyber. A list of RocketCyber Supported Applications can be found by clicking here: RocketCyber Integrations Guide

Supported Firewalls” are firewalls of a type and version number which RocketCyber integrates with, and for which Kaseya provides RocketCyber Services.  A list or Supported Firewalls can be found by clicking here: RocketCyber Integrations Guide.

Supported Operating Systems” are operating systems of a type and version number which integrates with RocketCyber, and for which Kaseya provides RocketCyber Services. A list of Supported Operating Systems can be found by clicking here: RocketCyber Integrations Guide.

  1. Licensing and Services
    1. Licensing.  RocketCyber is a SOC platform with related management Services designed to detect malicious activity across Endpoints and Cloud attack vectors.  RocketCyber is provided in exchange for License fees as set forth on the applicable Order.  Onboarding and implementation fees may also apply and shall also be set forth on the applicable Order. Fees are based on the number of Covered Endpoints and Covered M365 Accounts that are to receive RocketCyber Services (“License Units”).  RocketCyber is subject to a Committed Service Term as set forth on the Order, and License fees are typically paid monthly in advance unless otherwise agreed to by you and Kaseya.
    2. Proper Licensing.  RocketCyber will only be provided with respect to Covered Endpoints and Covered M365 Accounts.  A RocketCyber License must be purchased for those Endpoints and M365 Accounts that you wish to have Covered as follows:
      • For Endpoints: One (1) RocketCyber License is required to cover each one (1) Endpoint, and;
      • For M365 Accounts: One (1) RocketCyber License for required to cover up to 1.3 M365 Accounts.
    3. Transfer of Licenses.  Should you uninstall a RocketCyber License from a Covered Endpoint or Covered M365 Account, and transfer/install the License on another, coverage on the newly installed Covered Endpoint or Covered M365 Account may take a number of minutes before becoming active.  RocketCyber can only Alert with respect to Endpoints and M365 Accounts on which the RocktCyber is active at the time of the compromise.
    4. Audit of Licensing.  Kaseya may, in its discretion, audit use of RocketCyber and License levels at any time, and you hereby agree to cooperate with such audit and promptly provide information as reasonable requested by Kaseya to perform the audit. If such audit reveals that the number of License Units purchased by your organization is below that which is used, Kaseya may automatically increase the number of License Units on your account to the required level, and you hereby agree to pay for such higher number of License Units as well as any true-up charges that Kaseya imposes for past periods during which License Fees paid were below the appropriate level, given actual use.
    5. License Pools and Onboarding.  MSPs may purchase RocketCyber Licenses in pools, and deploy such licenses to various different Clients from the same pool.  Please note that RocketCyber coverage will not commence for a Client until that Client has been onboarded with the RocketCyber SOC team.
  2. Alerts and Calls with the RocketCyber SOC
    1. Alert Contacts.  You must properly input and update the name, telephone number and email address of Alert Contacts in the RocketCyber platform.  It is your responsibility to ensure that such contacts are correct and up to date.
    2. Communications with the SOC.  The RocketCyber SOC will accept communications regarding Alerts and similar security issues.  The RocketCyber SOC will not answer communications regarding the proper functioning or configuration of the RocketCyber platform, or any other Kaseya products or services; such product calls should be directed to Kaseya technical support, which can be contacted as described here: Kaseya Helpdesk.  For example:
      • Proper Calls to RocketCyber SOC: calls requesting the suppression of certain types of Alerts, or calls asking for more information about suspicious activity.
      • Improper Calls to RocketCyber SOC: calls regarding how to configure RocketCyber, or how to run a particular report within RocketCyber.
  3. Your Cooperation and Scope of Services
    The activity that is in scope for RocketCyber is described in our RocketCyber Incident Response Guide which is accessible by clicking here (the “Response Guide”).  Even if listed as in scope, we do not guarantee that all such activity will be detected.  Details regarding the division of responsibility between you and Kaseya, is also set forth in the Response Guide.   Delays in your response can cause risk, and the inability of Kaseya to perform the RocketCyber Services.   You and your organization agree to promptly provide the cooperation and information to Kaseya described in the Response Guide.   Kaseya is not responsible for any delay or failure to provide RocketCyber where your organization does not meet the obligations described in the Readiness Guide.
  4. General Terms
    1. Change in Support Status.  In Kaseya’s discretion, Kaseya may modify the list of Supported Applications, Supported Operating Systems or Supported Firewalls based on reasonable grounds such as, for example and not limitation: (i) a manufacturer’s end-of-support, or; (ii) known issues, bugs, malicious code or vulnerabilities that render support problematic or potentially damaging.
    2. Data Retention.  RocketCyber will retain data related to your RocketCyber Subscription as described in the article accessible by clicking here:  RocketCyber Data Retention.
    3. Non-Solicitation. During any RocketCyber Subscription, and for one (1) year thereafter, you shall not, directly or indirectly, solicit to employ in any capacity (including, as employee or contractor) any Kaseya personnel with whom you interacted with respect to your RocketCyber Services (“Restricted Personnel”). Further, you shall not, directly or indirectly, influence or induce Restricted Personnel to discontinue or reduce the scope of the relationship with Kaseya.  Breach of this section shall entitle Kaseya damages including, in its discretion, the right to terminate the RocketCyber Services based on your breach.