Integration · XDR and EDR
SentinelOne
Disconnects a machine from the network once you approve, and reconnects it with one click.
What Kandaro does with it
Kandaro SOC and SentinelOne.
Your endpoint tools. Kandaro reads their incidents and can isolate a machine once you approve.
- Respond
Proposes these actions, and can run them through it once an admin approves:
- Disconnect a machine
How it connects
Pick the way that fits.
- Vendor API
Kandaro calls the vendor’s API with the access you grant.
What Kandaro needs
What you set up once.
- An API token you create with permission to disconnect endpoints.
Good to know
- Kandaro doesn’t read SentinelOne alerts directly yet. Send them through your SIEM.
When Kandaro acts
A person says yes first.
The AI never closes a case and never acts on its own: every action waits for a person to approve it.
A person approves every action
Only an admin can approve, with a fresh second factor bound to that one action. Never from a chat message or an email link. A second approver can be required.
Proposals, not surprises
By default Kandaro shows the steps and you run them in your own tool. Letting Kandaro run them itself is a switch you turn on, after signing the SOC terms.
Everything can be reversed
Every block, disable and isolation can be reversed, most with one click. Blocks also end by themselves after a set time; a Wazuh block always runs its full 24 hours.
Limits and a pause button
Kandaro caps how many actions can run per hour, never acts on addresses in your allow list, and one switch pauses every action at once.
XDR and EDR
More tools like this.
Connect SentinelOne to Kandaro SOC.
Request early access to Kandaro SOC, or start a 14-day trial of Kandaro Deception today.
Deception trial: card required · cancel before day 14 and pay nothing