Synchronization and parallel operation FAQ

This article answers common questions about how Kaseya MDR operates alongside RocketCyber, what parallel operation means in practice, and what customers can expect during adoption.

Q. What does parallel operation mean?

A. Parallel operation means that Kaseya MDR is designed to run alongside the existing RocketCyber platform. Both experiences are available at the same time, and RocketCyber continues to operate normally. Customers can access and evaluate Kaseya MDR without disrupting existing security workflows, investigations, or response processes. There is no forced cutover.

Q. Is Kaseya MDR a new product I need to purchase?

A. No. Kaseya MDR is introduced as a platform update during the transition period. Availability and licensing depend on your agreement and enabled products.

Q. Will the existing RocketCyber platform stop working?

A. No. The existing RocketCyber platform remains available while customers evaluate and adopt Kaseya MDR. There is no immediate decommissioning when Kaseya MDR reaches general availability.

Q. Do I have to move to Kaseya MDR immediately?

A. No. Adoption is optional and self‑paced.

Customers can:

  • Continue using the existing RocketCyber platform

  • Test Kaseya MDR alongside it

  • Transition when ready

This approach is designed to avoid operational disruption.

Q. How do I access Kaseya MDR?

A. Kaseya MDR is accessed via a separate subdomain from RocketCyber.

Once access is enabled:

  • A Kaseya MDR environment is established.

  • User access is designed to remain aligned across experiences.

  • Configuration and settings are intended to remain aligned, where applicable, during the transition period.

Specific access steps are covered in Getting started with Kaseya MDR.

Q. Is this a migration or a synchronization?

A. The adoption model is best described as a synchronization, not a one‑time migration.

  • Core data and configuration are designed to remain aligned between experiences during the transition period.

  • There is no single "cutover" event.

  • Both environments remain operational.

NOTE  While the term migration may still appear in some workflows or tooling, Kaseya MDR adoption is intended to support continued parallel operation with RocketCyber.

Q. Will I have one tenant or multiple tenants across RocketCyber, Kaseya MDR, and SaaS Alerts?

A. Kaseya MDR is designed to avoid unnecessary duplication.

In most standard partner environments, a shared logical tenant is used so that organizations, users, and shared settings (such as ticketing integrations) remain aligned across experiences. This helps reduce duplicate configuration and operational overhead.

Q. Can alert or ticket duplication occur during parallel operation or synchronization?

A. Yes. During parallel operation or synchronization between RocketCyber and Kaseya MDR, alert duplication may occur in some environments.

This is most commonly observed through PSA ticketing when both platforms are actively integrated or mapped to the same organizations. There is currently no automated deduplication mechanism during this transition period.

To prevent duplicate tickets, partners may temporarily:

  • Disconnect PSA integrations

  • Unmap affected organizations from one of the platforms

This duplication can occur only during the transition and does not reflect steady‑state Kaseya MDR behavior.

Q. Do RocketCyber and Kaseya MDR use the same login?

A. RocketCyber and Kaseya MDR are accessed through separate URLs and require separate sign‑in sessions.

In some cases, the same underlying user identity may be reused, but authentication sessions are independent. You may be signed in to one platform without being signed in to the other.

Q. Can I continue using RocketCyber after enabling Kaseya MDR?

A. Yes. RocketCyber remains available during the transition period.

You can move between platforms as needed by accessing each platform directly.

Q. Do I need to reinstall or redeploy agents?

A. No. Kaseya MDR uses the same RocketCyber agent.

  • No uninstall is required

  • No redeployment is required

  • Existing telemetry is designed to continue flowing without change

Q. Will my existing configurations and settings carry over?

A. Yes. Existing configurations and alerting behavior are generally preserved by design to support testing and evaluation of Kaseya MDR without re-creating core settings.

Q. Will integrations need to be reconfigured?

A. Kaseya MDR is designed to minimize reconfiguration.

Some integrations may require updates depending on the integration type, but there is no requirement to reconnect everything immediately. Customers can transition integrations at their own pace.

In particular, some integrations (such as Microsoft) may benefit from reconnecting to enable expanded data access, but this is not mandatory.

Specific integration requirements are documented per integration type and may vary by environment.

Q. Can I choose which organizations are synchronized?

A. Synchronization occurs at the provider level, which means all organizations are included.

This does not force usage of Kaseya MDR. Organizations can continue operating in RocketCyber until adoption is desired.

Q. Does enabling Kaseya MDR change how the SOC monitors my environment?

A. No. The SOC engagement model remains unchanged.

  • The SOC continues to monitor SOC‑managed detections

  • Customer‑created rules notify your organization by default

  • SOC monitoring of custom rules can be requested and is evaluated on a case‑by‑case basis

This approach maintains service expectations while allowing flexibility.

Q. Does Kaseya MDR replace SaaS Alerts or Kaseya SIEM?

A. No. These are separate products with distinct roles.

  • Kaseya MDR focuses on SOC‑led managed detection and response for endpoints and infrastructure.

  • SaaS Alerts focuses on SaaS application activity.

  • Kaseya SIEM provides unified investigation and correlation across environments.

Each product has its own login and SKU.

Q. How long will the existing RocketCyber platform remain available?

A. The existing RocketCyber platform will remain available throughout the transition period.

Any future retirement would occur only after:

  • Sufficient capability coverage is determined to be available in Kaseya MDR

  • Customers have had adequate time to adopt the new experience

There is no announced end‑of‑life date associated with the Kaseya MDR release.

Q. What is the benefit of testing Kaseya MDR early?

Testing Kaseya MDR early allows customers to:

  • Explore the redesigned interface

  • Evaluate updated investigation and response workflows

  • Prepare internal processes at their own pace

Summary

Kaseya MDR adoption is designed to be:

  • Low risk

  • Non‑disruptive

  • Optional and flexible

While Kaseya MDR introduces a redesigned experience and updated investigation workflows, the underlying MDR service, agent deployment model, and SOC engagement remain consistent.

Related articles