Security
RocketCyber (Kaseya) integration
Reads which of your RocketCyber-managed agents are offline or not reporting. Read-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, and checked
A write-capable credential is refused, not warned about
We test the key you give us the moment you submit it. If it can write to RocketCyber (Kaseya), we reject it and tell you which step to change — there is no override. It is encrypted at rest, held in one vault in one application, and nothing is ever written back to RocketCyber (Kaseya).
RocketCyber (Kaseya) integration — common questions
- What does the RocketCyber (Kaseya) integration read?
- Reads which of your RocketCyber-managed agents are offline or not reporting. Read-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. The credential is checked live when you submit it and a write-capable one is refused, with no override — and every connector we ship is checked, at every commit, by an automated build rule that fails if it contains anything other than a GET call. The credential itself is wrapped by a key that lives in Azure Key Vault's hardware security module and never leaves it — our application can ask the vault to wrap or unwrap it, but cannot read the wrapping key. See our security page for the full picture.