How RocketCyber features map to Kaseya MDR

If you’ve used RocketCyber before, Kaseya MDR may look different at first glance. This article helps you quickly orient yourself by showing where familiar RocketCyber features live in Kaseya MDR and explaining what has changed—and what has not.

This is not a migration guide or a setup checklist. Its purpose is to help you recognize familiar capabilities, understand how the platform is now organized, and build confidence that core functionality has not been lost or removed.

What changed—and why

Kaseya MDR introduces an alert‑centric experience designed to reduce noise, centralize investigations, and make response actions clearer and faster.

Instead of spreading activity across multiple app‑specific pages and views, Kaseya MDR consolidates detection, investigation, and response into a smaller number of focused areas. As a result, some familiar RocketCyber features have been renamed, relocated, or consolidated into shared workflows.

These changes are primarily about how information is presented and acted on, not about removing detection capabilities or reducing coverage.

Where familiar RocketCyber features are now

The table below maps common RocketCyber concepts to where those same capabilities are surfaced in Kaseya MDR.

If you used RocketCyber before...

 In Kaseya MDR
App Store The App Store has been removed. Detection and integrations for Kaseya MDR–licensed organizations are managed through centralized settings.
App configuration pop‑up with per‑app toggles Settings > Application Configurations, with alert‑severity‑related controls located under Settings > Customize Alert Severity.
Incidents Alerts
Per-app event or telemetry pages Analysis (unified investigation experience)
Raw event review across multiple views Analysis (single, searchable, correlated view)
Agent status pages as the primary health indicator Alerts, investigations, and response outcomes are the primary indicators of activity, with agent status used as supporting context.
SOC Settings Settings > SOC Settings
Agent Settings Settings > Advanced Settings

This table is intended to describe where users now go to achieve the same outcomes, not to imply a strict one‑to‑one replacement of individual pages or toggles.

What did not change

While the interface and workflows have been modernized, several core elements remain the same:

  • The RocketCyber agent is unchanged; no reinstall or redeployment is required.

  • The Managed SOC continues to monitor, investigate, and respond to threats.

  • Existing organizations and users remain aligned, with configurations carried over where applicable.

  • Detection coverage across endpoints, firewalls, and supported integrations continues to function as before.

The goal of Kaseya MDR is not to replace protections you rely on, but to make those protections easier to understand, investigate, and act on.

How to think about the new experience

A helpful mental shift when using Kaseya MDR is:

  • Alerts are the primary unit of attention, not individual events or data sources.

  • Investigations provide context, correlating related activity rather than presenting isolated logs.

  • Response actions appear when appropriate, instead of being scattered across multiple app‑specific pages.

If you’re looking for something you used before and don’t immediately see it, it has likely been consolidated into a more central workflow, most often within Analysis or Settings.

What to expect during the transition

Kaseya MDR is introduced as a synchronized experience, not a forced migration. In most cases, no immediate action is required.

During the transition period:

  • Kaseya MDR runs alongside RocketCyber.

  • You can explore the new interface at your own pace.

  • Alerts and investigations appear in the new alert‑centric workflow.

  • Some historical views may remain available only in the existing RocketCyber experience.

  • Parallel operation (for example, with shared integrations such as PSA connections) may temporarily result in duplicated alerts or tickets in some scenarios until transition steps are completed.

Related articles