Skip to main content
You connect RocketCyber once at the MSP level. The token reads every customer account under your provider account.

​
1. Copy the API token

1

Open Provider Settings

Sign in to the RocketCyber console as a provider administrator and open Provider Settings.
2

Copy the Customer API token

Copy the API token shown there. RocketCyber’s Customer API documentation links Kaseya’s help on where to find it.
3

Note your region

RocketCyber hosts each provider in one region. The token works only in that region: United States (api-us.rocketcyber.com) or Europe and UK (api-eu.rocketcyber.com).

​
2. Add the token in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the RocketCyber card, under Endpoint Security.
2

Save the region and token

Pick your region, paste the API token and click Save. Neo checks the token against RocketCyber before saving, so a wrong token or region is rejected straight away.

​
3. Turn RocketCyber on per agent

Open the agent, go to the Tools & Settings tab, and configure the RocketCyber block under Tools & Integrations. The Read Only profile turns on every area. To leave an area out, set it to Disabled: Events and incidents name devices, users and IP addresses. To let the agent remediate what it finds, also give it your RMM’s tools or Microsoft 365 permissions; those keep their own approval rules. See RocketCyber API for what the agent can read.

​
Set up an agent

Ask your Neo Support Agent for a triggered agent on your RocketCyber tickets, for example: “Set up an agent that analyses each new RocketCyber ticket, checks earlier tickets for the same detection, and writes the technician an internal note with the evidence, the next steps and any suppression rule to add.”