Vigicap
Connector
CrowdStrike Falcon
API credential, entered client by client.
Connects the CrowdStrike Falcon API to read how many EDR sensors are registered and how many actually reported in over the last seven days — a machine whose sensor has gone quiet is no longer protected. Where the tenant licenses Spotlight, the open vulnerability count is read too. Machines with NO sensor stay invisible from this source: real estate coverage has to be cross-checked.
01
What to create in the tool
The access is created in CrowdStrike Falcon, not in Vigicap. Vigicap never asks for an administrator's password: it expects an API credential that you create, that you can see, and that you can revoke without us.
Where to generate it
Dans la console Falcon : Support and resources > API clients and keys > Create API client, avec les portées Hosts (Read) et, si vous l'avez, Spotlight vulnerabilities (Read). Le secret n'est affiché qu'une fois. Adresse de l'instance : l'URL d'API de VOTRE cloud (ex : https://api.eu-1.crowdstrike.com) — une clé émise sur un cloud est refusée par les autres.
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
The exact fields of the connection form, in the order they appear. Values marked “secret” never travel back to the browser: they are encrypted at rest and deleted on disconnection.
The form starts with the instance address, entered separately from the fields below. The public catalogue does not yet publish whether this connector needs one, or what it looks like — so this list is exact about everything else, and silent about that first field.
- Client ID
Identifiant du client d'API créé dans la console Falcon.
- Client Secretsecret
Secret affiché une seule fois à la création du client d'API.
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
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.
- #5 Maîtrise des systèmes d'informationControl of the information systems
- #9 Protection des systèmes d'information contre les codes malveillantsProtection of the information systems against malicious code
Read-only
The reads are read-only: Vigicap writes nothing into the tool while reading it.
What is read, what is kept, for how long and with which rights: the same register, connector by connector, in the data inventory.
Verification
The API is public and documented, but it can only be reached with a paid subscription the vendor issues no trial for: there is no instance we can obtain to run it against. This is not “not yet done” — it would take a customer lending us their tenant.
The trademarks and logos mentioned belong to their respective owners and identify the tools Vigicap is compatible with — see the legal notice.