Skip to main content
Back to the connector catalogue

Connector

Proxmox Backup Server

API credential, entered client by client.

Connects to Proxmox Backup Server (PBS), a free and open-source backup server, an alternative to Veeam for Linux/mixed fleets. Vigicap reads the configured datastores and the backups (snapshots) they contain to evaluate the ReCyF objective « Sauvegardes et restauration ». The presence of recent, frequent backups is a signal, but restore tests are not automatically verified.

01

What to create in the tool

The access is created in Proxmox Backup Server, 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

In Proxmox Backup Server: Configuration > Access Control > API Token > Add. Note the token ID (e.g. myuser@pbs!vigicap) and the secret, shown only once at creation.

Minimum role

Jeton d'API dédié dont l'entrée d'ACL porte le rôle DatastoreAudit sur /datastore — lecture des métadonnées et de la liste des sauvegardes, sans accès aux données sauvegardées. Le jeton a besoin de sa propre entrée d'ACL : le rôle donné à l'utilisateur ne suffit pas.

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.

  • Token IDsecret

    Access Control > API Token — full token identifier (user@realm!name).

    monuser@pbs!vigicap

  • Token secretsecret

    Access Control > API Token > Add — secret shown only once when the token is created.

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.