Skip to main content
Antivirus & security

SentinelOne Protection

Use the local SentinelOne agent to verify that the agent, real-time protection and console connection work and whether a threat is unmitigated.

The SentinelOne Protection check runs on the device and queries the local SentinelOne agent through sentinelctl. It reports whether the agent is running, whether real-time protection is active, whether the agent is connected to the SentinelOne management console, and whether the agent reports a threat it has not mitigated. It runs on Windows, Linux, and macOS (each as an x64 and an Arm64 build) every 5 minutes by default. octoja does not need a connection to the SentinelOne console for this. The check therefore reports only what the local agent itself knows; triage done in the SentinelOne console (Analyst Verdict, Incident Status) is not visible here.

Steps

  1. Open the device under Devices and switch to the Checks tab.
  2. Click Add Check → SentinelOne Protection.
  3. Adjust the settings if needed.
  4. Click Add Check.

To roll the check out to many devices at once, add it to a config package — see Assign checks with config packages.

Settings

FieldTypeRequiredDefaultDescription
Treat a disconnected console as criticalYes/NoNoOffWhen off, a lost management-console connection is a warning. When on, it is critical.

Advanced options (visible after enabling Show advanced options)

FieldTypeRequiredDefaultDescription
Query timeout (seconds)IntegerNo60Maximum time to wait for each sentinelctl invocation. The check replaces values of 0 or less with 60.

Results

The check reports the worst status of all problems it finds.

SituationStatus
sentinelctl was not found (SentinelOne is not installed)Critical
The agent is not runningCritical
The agent has been disabled (Windows only)Critical
Real-time protection is offCritical
No connection to the management consoleWarning, Critical with Treat a disconnected console as critical
The agent reports an unmitigated threat (Windows and macOS)Critical
The SentinelOne helper does not answer, so console connectivity and threat status cannot be determined (Windows only)Warning
None of the aboveOK

If the agent is not running or is disabled, the check reports only that root cause and does not additionally evaluate real-time protection and console connectivity. A reported threat is always included.

Differences by platform

PlatformAgent runningReal-time protectionConsole connectivityThreats
Windowssentinelctl status reports the agent as loaded or runningDerived: agent is running and not disabledLast console contact was no more than 10 minutes ago (via the SentinelOne helper)Active threats according to the SentinelOne helper
macOSAgent Operational State is enabledProtection is enabledConnected is yesInfected is not no
LinuxAgent state is EnabledDFI and Dynamic engines are enabledConnectivity is OnNot evaluated

The check looks for sentinelctl below C:\Program Files\SentinelOne on Windows, in /usr/local/bin/sentinelctl or the bundle under /Library/Sentinel/sentinel-agent.bundle on macOS, and in /opt/sentinelone/bin/sentinelctl on Linux.

See also: Set up alerts for a check