Vigicap
Connector
Elastic Security
API credential, entered client by client.
Reads Elastic Security detection rules (how many exist, how many are enabled) and the log data streams actually being fed, to assess incident detection and centralised logging. Elastic installs its prebuilt rules DISABLED: only enabled rules are counted, because an installed catalogue detects nothing. Needs both addresses — Kibana holds the rules, Elasticsearch holds the data — and swapping them produces confusing 404s.
01
What to create in the tool
The access is created in Elastic Security, 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 Kibana : Stack Management > API keys > Create API key, puis collez la valeur ENCODÉE. L'URL principale est celle de Kibana (souvent :5601) et la seconde celle d'Elasticsearch (souvent :9200) — les inverser produit des 404 déroutants.
Minimum role
Clé API Elasticsearch avec le privilège cluster `monitor` et, côté Kibana, l'accès en lecture à la fonctionnalité Security (rôle intégré « viewer » suffisant). Aucune écriture n'est effectuée.
Taken from the vendor's own role model, and checked before publication.
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.
- Clé API (encodée)secret
Le champ `encoded` renvoyé à la création, pas l'identifiant seul.
- URL ElasticsearchURL
Par exemple https://elastic.exemple.fr:9200. L'URL principale ci-dessus est celle de Kibana.
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.
- #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.