Connector

WithSecure Elements

API credential, entered client by client.

Endpoint and server protection (formerly F-Secure). Vigicap reads each device's protection state and patch state, to assess the ReCyF objectives on antivirus and patch management. Agents that have stopped reporting are counted apart and excluded from the calculation: this source knows nothing about those machines. Devices with patch management disabled are excluded from the patch calculation.

What to create in the tool

The access is created in WithSecure Elements, 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 Elements Security Center : Management > API clients (ou Identifiants d'API) > créez un client en lecture seule, avec la portée « connect.api.read ». Relevez le Client ID et le Client Secret ; le secret n'est affiché qu'une fois. Aucune URL n'est à saisir.

Minimum role

Dans WithSecure Elements Security Center, créez des identifiants d'API (Management API credentials) en lecture seule et n'accordez que la portée « connect.api.read ». Ce connecteur n'appelle que POST /as/token.oauth2 et GET /devices/v1/devices : il ne lit ni les événements de sécurité, ni les détails des menaces, et n'exécute aucune action sur les appareils.

Taken from the vendor's own role model, and checked before publication.

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 Elements Security Center.
Client Secretsecret
Affiché une seule fois à la création du client d'API.

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.

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.