Skip to main content
Vigicap
Try it
Back to the connector catalogue

Connector

OpenSearch

API credential, entered client by client.

Self-hosted search/analytics engine (open-source fork of Elasticsearch), used as the storage backend of a centralised logging stack (Fluentd/Logstash/Beats into OpenSearch). Vigicap reads the number of log indices (excluding system indices) and the cluster health status to evaluate the ReCyF objective « Journalisation centralisée ». Indices present on a degraded (red) cluster are a weaker signal than a fully healthy (green) cluster. Objective 20 is reserved for essential entities: for a client classified as an important entity this reading is recorded in the history but changes no level, the referential not applying that objective to them.

01

What to create in the tool

The access is created in OpenSearch, 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

Use an OpenSearch security-plugin account (username + password) with at least read permissions on `_cluster/health` and `_cat/indices`.

Minimum role

Compte du plugin de sécurité disposant au minimum de la lecture sur _cluster/health et _cat/indices.

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.

  • Usernamesecret

    OpenSearch security-plugin account used for HTTP Basic authentication.

    Nom d'utilisateur OpenSearch

  • Passwordsecret

    Password for the account above.

    Mot de passe OpenSearch

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 one objective of the ANSSI ReCyF framework. It PROPOSES it: the level only counts once a consultant has confirmed it.

  • #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.