Connector

Splunk

API credential, entered client by client.

Reads Splunk indexes (how many actually receive events, and how recently) and enabled scheduled searches that have an action, to assess centralised logging and incident detection. Splunk's internal indexes are excluded: a fresh installation receiving only its own logs must not count as centralised logging. A scheduled search with no action is not counted as an alert — it fires without telling anyone. The URL expected is the management port (8089), not the web interface.

What to create in the tool

The access is created in Splunk, 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 Splunk : Paramètres > Jetons > Nouveau jeton, sur un compte de service. L'URL est celle du PORT DE GESTION — https://splunk.exemple.fr:8089 — et non celle de l'interface web (8000).

Minimum role

Rôle disposant des capacités list_indexes et list_search (le rôle intégré « power » suffit ; « admin » n'est pas nécessaire), porté par un compte de service dédié avec un jeton d'authentification révocable. Aucune écriture n'est effectuée.

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.

Jeton d'authentificationsecret
Paramètres > Jetons. Révocable, contrairement à un mot de passe.

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.

#12 Identification et réaction aux incidents de sécuritéIdentification of and response to security incidents
#20 Supervision de la sécurité des systèmes d'informationSecurity monitoring of the information systems

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

This connector has been run end to end against a real instance of the tool, not merely tested against a mock.

The trademarks and logos mentioned belong to their respective owners and identify the tools Vigicap is compatible with — see the legal notice.