Getting started with Kaseya MDR

The Getting started with Kaseya MDR section explains how to access the platform, complete onboarding, and verify that your environment is ready for use.

It focuses on:

  • Activation and sign-in

  • Identity association and authentication

  • Initial access validation

This section supports different onboarding contexts, including:

  • Organizations accessing Kaseya MDR through RocketCyber

  • Kaseya 365 customers

  • Organizations activating Kaseya MDR directly, including those who may link to an existing tenant associated with SaaS Alerts or Kaseya SIEM

While the onboarding experience may differ, the goal is the same: confirm that access is established, authentication is working as expected, and the platform is ready for use.

What “getting started” covers

Getting started focuses on early access and validation after first login. Depending on your environment, onboarding may include:

  • Understanding how you access Kaseya MDR

  • Confirming how authentication works in your environment

  • Completing required security setup (such as two-factor authentication)

  • Verifying that the platform is accessible and that expected data and entities are visible

IMPORTANT  Data, events, or alerts may not appear immediately after first access. Use the validation steps in this section before assuming a configuration or access issue.

Accessing Kaseya MDR

Kaseya MDR supports different onboarding experiences depending on your subscription and existing products.

Direct activation

Some organizations activate Kaseya MDR using an activation email. During onboarding, you may be prompted to link Kaseya MDR to an existing tenant associated with SaaS Alerts or Kaseya SIEM, or create a new tenant. See Getting started with Kaseya MDR as a SaaS Alerts, Kaseya SIEM, or MDR-only user.

Kaseya 365

When Kaseya MDR is included in a Kaseya 365 subscription, access is provided through KaseyaOne after provisioning is complete.

RocketCyber

If you are an existing RocketCyber user, access to Kaseya MDR is initiated from the RocketCyber platform.

During the transition period:

  • You do not need to re‑sign up for Kaseya MDR.

  • Access to Kaseya MDR is initiated from the RocketCyber platform.

  • Your existing RocketCyber monitoring and protections continue to run.

  • RocketCyber and Kaseya MDR remain available as separate platforms, each accessed independently.

To understand how this access process works and what to expect during first login, see Getting started with Kaseya MDR as a RocketCyber user.

About access, authentication, and security readiness

Before using Kaseya MDR, you must be able to:

  • Sign in successfully

  • Understand how authentication is handled

  • Complete required security setup

Depending on your environment, authentication may be handled:

Unified Login with KaseyaOne

If your organization uses Unified Login, authentication may be handled through KaseyaOne rather than directly in Kaseya MDR. This affects how sign‑in and security enforcement behave, but not how detection, investigation, or response works in the platform.

Refer to Unified Login with KaseyaOne to understand how Unified Login impacts access and security requirements.

Securing your account with two‑factor authentication (2FA)

If your organization uses direct sign‑in to Kaseya MDR, enabling two‑factor authentication (2FA) is strongly recommended and required for certain response and automation capabilities.

Completing security setup early helps ensure:

  • Reliable access to the platform

  • Proper enforcement of security controls

  • Full availability of investigation and response features

NOTE  If your organization uses Unified Login, MFA may already be enforced during KaseyaOne sign‑in. Review Securing your account with two‑factor authentication (2FA) to understand whether additional action is required.

What happens after initial access

Once access and authentication are confirmed, getting started continues with validation:

  • Confirming that expected data is visible after access is established

  • Confirming that expected devices appear (This validates agent presence and visibility. It is not a deployment step.)

  • Verifying that events and alerts are visible

  • Understanding where investigation workflows are introduced in the platform

Professional Services project setup and related communications are handled separately and are not part of the Getting started scope.

These steps are covered in the child articles within this section.

Articles in this section

The Getting started with Kaseya MDR section includes the following articles: