
Connector
Kopia
API credential, entered client by client.
Self-hosted open-source backup tool, run in server mode. Vigicap reads the sources it watches and, for each one, the date of the last completed backup and the number of file errors it hit, to evaluate the ReCyF objective « Sauvegardes et restauration ». A configured source is not an executed backup: the two are counted separately. Restore tests cannot be verified — Kopia's API keeps no history of them — so this connector never proposes the top level.
01
What to create in the tool
The access is created in Kopia, 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
Démarrez le serveur Kopia avec --server-username et --server-password, et donnez ici ce couple (pas le compte --server-control-*). Important : l'instance doit présenter un certificat TLS valide et reconnu — le certificat auto-signé généré par Kopia sera refusé par Vigicap (aucune option pour désactiver la vérification TLS, par sécurité).
Minimum role
Le serveur Kopia n'expose qu'un seul couple identifiant/mot de passe HTTP (--server-username / --server-password) : il n'existe pas de rôle « lecture seule » distinct. Utilisez ce couple, et non le compte de contrôle (--server-control-username), qui autorise en plus le pilotage du serveur.
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.
- Nom d'utilisateur du serveursecret
La valeur passée à --server-username au démarrage de `kopia server start`.
vigicap
- Mot de passe du serveursecret
La valeur passée à --server-password. Ce n'est pas le mot de passe du dépôt.
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.
- #13 Continuité et reprise d'activitéBusiness continuity and recovery
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.