Skip to main content
Back to the connector catalogue

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 ».

01

What to create in the tool

The access is created in Bitdefender GravityZone, not in Vigicap.

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.

02

What to enter in Vigicap

  • GravityZone API keysecret

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

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.9 Inventory of information and other associated assets
  • 5.10 Acceptable use of information and other associated assets
  • 5.11 Return of assets
  • 5.12 Classification of information
  • 5.14 Information transfer
  • 8.1 User endpoint devices
  • 8.7 Protection against malware
  • 8.23 Web filtering

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

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

  • How many of the client's machines are actually managed by GravityZone — not how many licences exist.
  • Whether the antimalware module is active on them, and whether any are reported infected.
  • Two ReCyF objectives: protection against malicious code, and estate inventory.

What it does not read

The machines GravityZone does not manage — by construction, a console knows only its own perimeter. Access is through the JSON-RPC API with a single key (apiKey), read-only.

What these signals do not prove

  • "Managed machines" is a denominator, not a coverage. Set against the client's real estate — which this source does not know — it may be excellent or very partial without the figure changing.
  • A machine reported infected is a report, not a triaged incident. The connector surfaces the counter; the triage remains a human act.
Why estate inventory and not just antimalware?
Because the number of managed machines is an inventory measurement in itself — provided it is read for what it is: the perimeter of one console.
Is a single API key enough?
Yes, and it is read-only. It is created and revoked inside GravityZone, without going through us.