> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# RocketCyber

> Let Neo agents read your RocketCyber SOC incidents, events and suppression rules, and advise your technicians

RocketCyber is Kaseya's managed SOC. It watches your customers' devices, firewalls and Microsoft 365 tenants, and raises an incident, usually as a ticket in your PSA, when it sees something suspicious. Connect it, and Neo agents can read the incident behind a ticket, the detections behind it and the device it names, then advise the technician.

Neo reads RocketCyber and changes nothing there. Closing an incident and adding a suppression rule stay in the RocketCyber console.

## What Neo can do with RocketCyber

* Read the incident behind a RocketCyber ticket, with RocketCyber's own remediation advice and the detection events behind it
* Check the device the incident names: online, offline or isolated, its OS and when it last connected
* Find how earlier tickets for the same detection, device or user were resolved
* Check the suppression rules already in place, and draft the rule for the technician to add when earlier tickets show a detection is expected
* Remediate through your RMM or Microsoft 365 tools, under their own approval rules, when earlier tickets show the fix
* Read Microsoft Defender health and risk, and Microsoft 365 secure score, per customer

See [RocketCyber API](https://docs.neoagent.io/agents/tools/security/rocketcyber-api.md) for the permission groups.

## Your accounts are mapped to companies

Neo matches your RocketCyber customer accounts to the companies in your PSA and keeps the mapping on the RocketCyber card's **Organization Mapping** tab, refreshed on each PSA metadata sync.

Matching uses the account name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the long tail.

**A name match, or one you confirm, is handed straight to your agents.** An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it.

Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync.

On a ticket, an agent reads RocketCyber only for the account mapped to the ticket's company. A company with no mapping that agents can use gets no RocketCyber reads until you set or confirm one on the tab.

## Next steps

> **[Connect RocketCyber](https://docs.neoagent.io/integrations/rocketcyber/connecting-to-neo.md)**
>
> Copy your API token and save it in Neo.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.