Kaseya MDR (RocketCyber): connect, sync incidents and Microsoft 365 events
Connect RocketCyber for each customer's managed-SOC posture, add an optional Kaseya API key for Microsoft 365 events and automatic responses.
On this page · 9 sections
Connect RocketCyber, and add a Kaseya API key if you use Kaseya MDR, and the company page, the service desk and business reviews show how many of a customer's endpoints the SOC watches, what it caught, and the Microsoft 365 events and automatic responses waiting on you, so a response that needs your approval does not sit unanswered.
What it does for you
| Where in Current | What you get |
|---|---|
| Service desk tickets | The Machine and tools card counts the customer's open RocketCyber incidents. With a Kaseya key, the Person panel shows the requester's recent critical and medium Microsoft 365 events and the customer's automatic responses waiting for approval, and account actions can be turned on (see below). |
| Company page | The Security section's Open criticals and Incidents 90d include RocketCyber. With a Kaseya key, a card counts critical Microsoft 365 events in the last 7 days and automatic responses waiting. |
| Alerts | Open SOC criticals, and with a Kaseya key critical Microsoft 365 events from the last 24 hours, raise the critical security alert. An automatic response waiting more than 2 hours raises its own alert. |
| Reports and dashboards | The SOC incidents (last 90 days) tile. |
| Business reviews | Managed SOC numbers for the review: endpoints watched and the incidents raised and resolved in the last 90 days. |
| Ask Current | Ask whether any Kaseya MDR responses are waiting, or which customers have security incidents open, and the answer lists them by company. |
RocketCyber is your managed-SOC layer, the 24/7 watch on your customers' endpoints and the incidents it catches. This connector reads that story out of RocketCyber and hangs it off the matching Current company: how many endpoints are under watch, how many security apps are enabled, and the incident posture per customer. It is read-only in the strictest sense: Current reads RocketCyber and can never change anything in it. The Customer API has no write endpoints at all.
Generate a Customer API token in RocketCyber (one time)
RocketCyber's Customer API uses a single Bearer token that is scoped to the account tree it belongs to. The data Current pulls is exactly the data that token can see. Generating it is an admin action inside the RocketCyber web app.
- 11 · Open the RocketCyber app as an administratorSign in to RocketCyber. Generating an access token is a customer/administrator action, follow Kaseya's helpdesk article "Customer API - Finding Access Token" for the exact screen, which Kaseya keeps current as the UI changes.
- 22 · Generate the access tokenCreate (or copy) the Customer API access token. It is long-lived and does not expire on a timer. You regenerate it in-app if you ever need to rotate it. A single token carries its own account scope, so pick the token whose tree covers the customers you want in Current.
- 33 · Copy the token nowCopy the token before you leave the page. Current stores it server-side only and never shows it back, so keep your own copy until the connection tests green.
- 44 · Note your regionRocketCyber runs on regional hosts, Production-US and Production-EU. It must match where your RocketCyber account lives; the wrong region can't see your data.
Connect it in Current
- 1Open the Kaseya MDR (RocketCyber) cardIn Current, open Settings › Integrations (Tenant Admins only), find Kaseya MDR (RocketCyber) under Security.
- 2Pick the region, paste the tokenChoose Production-US or Production-EU, then paste your Customer API token into the RocketCyber API token field. If you use Kaseya MDR, paste the Kaseya API key too (see the next section); it is optional.
- 3Press Test connectionCurrent makes one live read of your account roster to prove the token works before storing anything. A bad token or the wrong region is rejected on the spot with the real reason. On success the token is stored server-side only (the browser never sees it again), and the card shows how many accounts it found.
What Current syncs, and how often
The sync runs every 6 hours on its own, and Sync now covers the impatient path. Each run walks your account roster, agent list, enabled security apps, and incident counts, then writes value-signals, never a raw incident firehose.
| Data set | What Current stores | Where it lands |
|---|---|---|
| Accounts (customers) | Each RocketCyber account by its accountId and name, its status, the count of managed agents/endpoints, and how many security apps are enabled | The mapped Current company + SBR / CIO packs |
| Incident posture | A per-account SUMMARY: how many incidents are open right now, broken down by severity (critical / high / medium / low) | The mapped Current company + SBR / CIO packs |
| Kaseya organizations (with a Kaseya key) | Every organization in your Kaseya MDR console: its name, and whether its Microsoft 365 connection is connected, needs attention, or not connected | The mapping panel and the card's What we found |
| Kaseya MDR events (with a Kaseya key) | Critical and medium Microsoft 365 events of the last 30 days: what happened, when, to which account, and from which country. Never the raw event. | The company's Kaseya MDR counts, the service desk ticket's Person panel, and the security alert |
| Automatic responses (with a Kaseya key) | The responses Kaseya holds for an approval, and those decided in the last week: the rule, the account and when it fired | The company's security counts and an alert when one waits more than 2 hours |
| 90-day activity | Per account: incidents raised in the last 90 days, incidents resolved in the last 90 days, and the most recent incident timestamp | The mapped Current company + SBR / CIO packs |
The read-only guarantee
RocketCyber's Customer API is inherently view-only. The published collection is entirely GET, with no create, update, or delete endpoints anywhere. On top of that, every request Current makes passes through a read-only guard that only permits the four specific reads it needs: the account roster, the agent list, the enabled-apps list, and the incident list. Nothing else is reachable, even by a code bug. Current cannot write to RocketCyber. The Kaseya key works the same way for reading: the sync may only sign in, read events, read automatic responses and read a job's result.
Add Kaseya MDR (optional)
Kaseya MDR runs on RocketCyber, and its newer API adds two things the Customer API cannot give you: Microsoft 365 security events per customer, and the automatic responses Kaseya holds until someone approves them. To read them, paste a Kaseya API key on the same card.
- 11 · Copy the key in Kaseya MDRIn the Kaseya MDR console open Settings, then API, and press Show API Key. Copy the key.
- 22 · Paste it on the cardOpen the Kaseya MDR (RocketCyber) card, paste the key into Kaseya API key, and press Test connection. Current checks the key with one call to Kaseya and stores it server-side only. A wrong key is refused with the reason, and RocketCyber keeps working either way.
- 33 · Read What we foundAfter the next sync (or Sync now) the card lists what Current found: whether each key works, how many organizations Kaseya lists and how many still need a company, how many have Microsoft 365 connected, need permissions upgraded or reconnecting, or are not connected, how many critical or medium events arrived in the last 30 days, and how many automatic responses are waiting.
- Saving the card again with the Kaseya field empty keeps the key you saved before. To take it away, press Remove Kaseya key.
- Current checks Kaseya for automatic responses every 10 minutes, so a response waiting for approval shows up quickly. The card says "Instant alerts not available; checking every 10 minutes" until Kaseya can deliver to Current directly.
- Current reads every organization in your Kaseya MDR console, not only the ones with recent events, and matches each to one of your companies by name, like RocketCyber accounts. Anything unmatched appears in the same mapping panel.
- Kaseya can only read events for an organization whose Microsoft 365 connection is healthy. If the card shows many organizations that need permissions upgraded or reconnecting, fix them in the Kaseya MDR console (Microsoft 365 connections), then press Sync now.
Account actions on a service desk ticket
With a Kaseya API key saved and the service desk on, a technician can act on the requester's Microsoft 365 account from the ticket: Sign out everywhere, Block sign-in, and Force password change at next sign-in. The same section can approve or reject an automatic response Kaseya is holding for that company. These act on real Microsoft 365 accounts, so they are off until a tenant admin turns them on: open Settings › Integrations, press the Kaseya MDR (RocketCyber) row, then Manage, and use Turn actions on under Actions on service desk tickets.
- Engineers, project managers, service managers and tenant admins can use them, on a ticket assigned to them or that they opened (tenant admins and service managers on any ticket). Anyone else sees the events and waiting responses without the buttons.
- The account must be the ticket's requester or an address on that company's Kaseya events or automatic responses from the last 30 days. You never type an address in.
- They work only for an organization whose Microsoft 365 connection is healthy in Kaseya.
- Every action asks first and names the person and the company. Each one is sent once and never retried; if Kaseya does not answer, Current says it can't tell whether Kaseya ran it, so check the Kaseya console before trying again.
- A workspace can run at most 10 account actions an hour, and every press is recorded on the ticket's activity. Reset password and Delete user are not offered.
- The company page never offers these actions. It keeps two read-only counts.
Mapping RocketCyber customers to your companies
In RocketCyber a customer is an Account, identified by its accountId (with a hierarchy path like 2.4.123 from the MSP root down to the customer). Current matches each account to one of your Current companies automatically by normalized name (lowercased, with punctuation and Inc/LLC/Ltd-style suffixes stripped), and links it when exactly one company matches. When two or more of your companies share that name and the names differ only by a suffix like Inc or LLC, Current links the one that is an active customer, or, if none of them is, the one linked to your PSA. Anything still tied or unmatched is left for you.
- Unmatched accounts appear on the RocketCyber card's mapping panel, press Map to pick the right Current company by hand.
- A manual mapping is never overwritten by the auto-matcher on a later sync, and neither is a manual unlink.
- Unmapped accounts still sync (their agent and incident counts are stored), but the data only appears on a company once the account is mapped to it.
When something looks wrong
| What you see | What it means |
|---|---|
| Test connection fails immediately | Usually the token was mistyped or regenerated, or the region is wrong (a US token can't read the EU host and vice-versa). The message names the real reason. |
| Card shows Error mentioning 401 or 403 after it was working | The stored token was rejected. It was regenerated or revoked in RocketCyber. Generate a fresh Customer API token and reconnect. |
| A company shows no RocketCyber data | Its RocketCyber account isn't mapped yet, or that account genuinely has no agents or incidents. Check the mapping panel's Unmatched list. |
| Incident counts look low on a first sync of a huge estate | A very large incident history is paged with a wall-clock budget, so an unusually big first run can be capped; it fills in on the next 6-hour sync. Open counts and coverage are unaffected. |
| Rate-limited | Current paces itself and backs off when RocketCyber asks (Retry-After). Nothing to do, the sync resumes on its own. |
