
Connector
SentinelOne
API credential, entered client by client.
Connects to the SentinelOne console (Singularity) to automatically check how many agents are deployed, how many are actually connected and active, and how many threats the console has detected. Feeds the ReCyF objectives « protection contre les codes malveillants » and « détection des incidents ».
01
What to create in the tool
The access is created in SentinelOne, not in Vigicap.
Where to generate it
In the SentinelOne console: Settings > Users > your service account > Generate API token (the token is shown only once and inherits the account's rights — prefer a read-only service account). Instance address: your console's URL (e.g. https://your-tenant.sentinelone.net).
Minimum role
The minimum role this connector needs is not documented to date. We would rather write that than guess it: an unverified claim about access rights ends up in front of a client's data protection officer, who is precisely the person who will check it. Refer to the vendor's documentation, which alone is authoritative on its role model.
02
What to enter in Vigicap
- API token (ApiToken)secret
Generated from Settings > Users > Generate API token in the SentinelOne console.
03
Per-client routing
The connection is made client by client: one credential per client, entered on that client's record. Nothing is shared between two clients, and disconnecting one leaves the other untouched.
04
What it does, and what it does not do
ISO 27001 controls covered
This connector's readings feed ${n} Annex A controls — derived from the ReCyF objectives above, not entered by hand.
- 5.7 Threat intelligence
- 5.14 Information transfer
- 8.7 Protection against malware
- 8.16 Monitoring activities
- 8.23 Web filtering
ReCyF objectives it pre-fills
A reading feeds 2 objectives of the ANSSI ReCyF framework. It PROPOSES them: a level only counts once a consultant has confirmed it.
- #9 Protection des systèmes d'information contre les codes malveillantsProtection of the information systems against malicious code
- #12 Identification et réaction aux incidents de sécuritéIdentification of and response to security incidents
Read-only
Vigicap writes nothing to the tool while reading.
How Vigicap handles your credentials.
Verification
This connector was written from the vendor's documented API and has not yet been run against a real instance.
What this connector reads, exactly
- How many agents are deployed in the Singularity console.
- How many are actually connected and active — the second figure is the one that counts, and it is read separately from the first.
- How many threats the console has detected. Two ReCyF objectives: protection against malicious code, and incident detection.
What it does not read
The content of the detections, and what was done about them. The connector counts threats; it reads neither their triage, nor their handling, nor the exclusions configured in the console. One field is requested — apiToken — and it is a read token.
What these signals do not prove
- The gap between agents deployed and agents active is this connector's most useful piece of information, and the easiest to read too quickly: an agent deployed but disconnected protects exactly as much as an absent one.
- A count of detected threats proves a detection chain is running. It does not prove anyone looked at them — the same ambiguity as for any detection console.
- Zero threats detected — is that a good sign?
- It is ambiguous, and should be read together with the share of active agents: a quiet estate and an estate with no connected agent give the same zero.
- Can the connector isolate a machine or trigger remediation?
- No. The read is read-only, and no action call is implemented.