Connector

HashiCorp Vault

API credential, entered client by client.

Self-hosted, centralised secrets manager (HashiCorp Vault OSS/Enterprise), used by MSPs to store and distribute a client's credentials, API keys and certificates rather than scattering them across scripts or configuration files. Vigicap reads the seal status (sealed/unsealed) and the list of mounted secrets engines to evaluate the ReCyF objective « Gestion des identités et des accès ». An unsealed Vault with configured secrets engines is a signal of centralised management, but guarantees neither least privilege nor the actual rotation of secrets.

What to create in the tool

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

Generate or use a Vault token whose policy allows reading sys/health and sys/mounts (e.g. "read" capability on sys/mounts). On Vault Enterprise namespaces, also enter the namespace (e.g. "ns1").

Minimum role

Vault n'exprime pas le moindre privilège par un rôle mais par une policy. La policy minimale de ce connecteur tient en deux chemins en lecture : path "sys/health" { capabilities = ["read"] } et path "sys/mounts" { capabilities = ["read"] } — aucun accès aux moteurs de secrets eux-mêmes, et pas de capability sudo.

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.

Vault tokensecret
Vault token with a policy allowing reads on sys/health and sys/mounts.
hvs.xxxxxxxxxxxxxxxxxxxx
Namespace (Vault Enterprise)optional
Optional — only for Vault Enterprise with namespaces. Leave blank on Vault OSS or the root namespace.
ns1

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

#10 Gestion des identités et des accès des utilisateurs aux systèmes d'informationManagement of user identities and of user access to 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.