Skip to main content
Back to the connector catalogue

Connector

Veeam

API credential, entered client by client.

Connects to Veeam Backup & Replication (Community Edition or above) to automatically check that backup jobs are configured and that they run successfully, for the ReCyF objective « Sauvegardes et restauration ».

01

What to create in the tool

The access is created in Veeam, not in Vigicap.

Where to generate it

Create a dedicated account (ideally with restricted rights) on the Veeam Backup & Replication server. The REST API listens on port 9419 by default (e.g. https://veeam.example.com:9419).

Minimum role

Compte dédié portant le seul rôle Backup Viewer — accès en lecture seule, suffisant pour lister les tâches et leur dernier résultat.

Taken from the vendor's own role model, and checked before publication.

02

What to enter in Vigicap

  • Veeam usersecret

    Windows/local account allowed to authenticate against the Veeam Backup & Replication REST API.

    DOMAINE\utilisateur ou utilisateur

  • Passwordsecret
  • API version (x-api-version)optional

    Optional — leave blank to use the default value. Only fill this in if your version of Veeam Backup & Replication requires a different documented value (e.g. 1.2-rev0).

    1.1-rev1

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

ISO 27001 controls covered

This connector's readings feed ${n} Annex A controls — derived from the ReCyF objectives above, not entered by hand.

  • 5.29 Information security during disruption
  • 5.30 ICT readiness for business continuity
  • 5.33 Protection of records
  • 8.6 Capacity management
  • 8.13 Information backup
  • 8.14 Redundancy of information processing facilities

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

Vigicap writes nothing to the tool while reading.

How Vigicap handles your credentials.

Verification

This connector was written from the vendor's documented API and has not yet been run against a real instance.

What this connector reads, exactly

  • That backup jobs are configured on the Veeam Backup & Replication instance.
  • That they run successfully — that is the second half, and the two count separately.
  • One ReCyF objective: backup and restoration.

What it does not read

No restoration at all. This connector reads jobs and their outcome, never a restore test — and that is the distinction every insurance questionnaire eventually asks about. A backup that succeeds every night and has never been restored is still an unverified backup.

What these signals do not prove

  • A successful job proves data was written somewhere. It proves neither that the scope backed up is the right one, nor that the copy is readable, nor that it is out of a ransomware's reach.
  • The connector works from the Community Edition upwards. That edition also exists in deployments where it covers only part of the estate: a count of jobs does not say what they encompass.
Can the connector attest to a tested restore?
No, and no connector in this list can. A restore test is proven by a dated report — that is consultant work.
Why an **apiVersion** field?
Because Veeam's API changes between major versions, and the connector would rather ask you than guess.