Connector

Bitdefender GravityZone

API credential, entered client by client.

Connects to the Bitdefender GravityZone console (JSON-RPC API) to automatically check how many of the client's workstations are actually managed by GravityZone, whether the antimalware module is active, and whether any workstations are reported infected. Feeds the ReCyF objectives « protection contre les codes malveillants » and « inventaire du parc ».

Beta

What to create in the tool

The access is created in Bitdefender GravityZone, 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 GravityZone, sign in with an account that has "Manage Networks" rights, then go to My Account > API Keys > Add, and check at least the "Network" API. Instance address: your console's URL (e.g. https://cloud.gravityzone.bitdefender.com or your on-premise GravityZone).

Minimum role

À la génération de la clé (My Account > API keys), n'activez que l'API « Network » — la seule appelée ici ; Control Center répond 403 pour toute autre. Bitdefender exige en revanche que le compte qui GÉNÈRE la clé détienne les droits Manage Networks, Manage Users, Manage Company et Manage Reports : aucun compte en lecture seule ne peut créer cette clé.

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.

GravityZone API keysecret
Generated in GravityZone > My Account > API Keys, with the "Network" API enabled.

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

#1 Recensement des systèmes d'informationInventory of information systems
#9 Protection des systèmes d'information contre les codes malveillantsProtection of the information systems against malicious code

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.