Skip to main content
Back to the connector catalogue

Connector

Acronis Cyber Protect

API credential, entered client by client.

Connects to Acronis Cyber Protect Cloud to automatically check that the client's workstations and servers are covered by an Acronis protection plan and that their backups actually run successfully. Feeds the ReCyF objectives « sauvegardes » and « protection contre les codes malveillants ».

Beta

01

What to create in the tool

The access is created in Acronis Cyber Protect, 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 the Acronis console (Settings > API Clients), create an API client: Acronis shows an ID, a secret, and your data centre's URL (e.g. https://eu2-cloud.acronis.com). Enter that URL as the instance address. The secret is shown only once.

Minimum role

Créez le client API depuis un compte d'administrateur ne portant que le rôle « read-only administrator » sur le service Cyber Protection : le client hérite définitivement des rôles du compte qui le crée, et ces rôles ne sont plus modifiables ensuite.

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.

  • API client IDsecret

    Client ID shown when the Acronis API client is created.

    00000000-0000-0000-0000-000000000000

  • API client secretsecret

    Paired client secret — shown only once by Acronis.

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

  • #9 Protection des systèmes d'information contre les codes malveillantsProtection of the information systems against malicious code
  • #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 was written from the vendor's documented API and has not yet been run against a real instance. It is marked “Beta” everywhere it appears.

The trademarks and logos mentioned belong to their respective owners and identify the tools Vigicap is compatible with — see the legal notice.