Security
RocketCyber (Kaseya) integration
Reads which RocketCyber agents are offline or not reporting. View-only.
Setup steps are for connected customers — sign in to read them.
What we find in RocketCyber (Kaseya)
Agents that are offline or not reporting on the MDR/SOC fleet — an overlay on the RMM's fleet, not a second one. Which security app modules are switched on per client (the original module-gap lead) is not yet wired — the endpoint's query params are confirmed, its response fields are not.
Every finding lands on your Client Upsell board as a named client with a number beside it — not a report you have to read.
What the RocketCyber (Kaseya) connection does
Read — powers Client Upsell
Read your clients' stack
Who is actually protected: endpoints still onboarding, seats never deployed, sites with no filtering policy.
Read-only
We only ever read — we never change anything in RocketCyber (Kaseya)
You make a view-only key using our setup steps. Our connection has no code that can write to RocketCyber (Kaseya), and your key is encrypted and only used to read.
RocketCyber (Kaseya) integration — common questions
- What does the RocketCyber (Kaseya) integration read?
- Reads which RocketCyber agents are offline or not reporting. View-only.
- What does MSProspector find in RocketCyber (Kaseya)?
- Agents that are offline or not reporting on the MDR/SOC fleet — an overlay on the RMM's fleet, not a second one. Which security app modules are switched on per client (the original module-gap lead) is not yet wired — the endpoint's query params are confirmed, its response fields are not.
- Is the RocketCyber (Kaseya) connection read-only?
- Yes. We only ever read from RocketCyber (Kaseya) — our RocketCyber (Kaseya) connection has no code that can change anything, and an automated check on every change to our code blocks any that could. Please create a view-only key using the setup steps, so the key itself can't make changes either.