Bitdefender GravityZone

This document provides the steps required to configure the Bitdefender GravityZone Inspector.

👍

Quick Details:

Recommended Agent: On-Demand
Supported Agents: On-Demand or Self-Managed
Is Auto-Discovered By: N/A
Can Auto-Discover: Bitdefender Child Tenants
Parent/Child Type Inspector: Yes
Inspection via: API
Data Summary: Here

Overview

See it in Action

📘

Business vs. Enterprise

This Inspector will work with both the Business and Enterprise versions of Bitdefender GravityZone.

🚧

API Endpoint Availability

Liongard is able to pull data from both the "Partners" and "Cloud Solutions" product offerings from Bitdefender. However, there are two specific endpoints that are only available from the Partners product, which are the getCompaniesList and getRootContainers endpoints.

If you are using the Cloud Solutions product then your inspector will return an empty value for these two endpoints.

Inspector Setup Preparation

Step 1: Getting your API Key/Hostname

  • Log in to your Bitdefender GravityZone console
  • On the top right-hand side of the navigation header, click on your user name and select My Account in the drop-down

  • Scroll down to find your API URL under the section labeled Control Center API.

Control Center API

  • Next, scroll down to the API keys section and click on the Add button.

  • Apply the permissions listed below for the API key:
    • Companies API
    • Licensing API
    • Packages API
    • Network API
    • Policies API
    • Reports API
    • Accounts API
    • Incidents API
    • Quarantine API

  • Click Save
  • Copy the API key to your clipboard.

Liongard Inspector Setup

Step 1: Parent Inspector Setup

Since Bitdefender GravityZone is a multi-tenant system where a single portal is used to manage many Environments, you will set up a single "Parent" Inspector with the API Key that will then auto-discover "Child" Inspectors for each Environment.

In Liongard, navigate to Admin > Inspectors > Inspector Types > Navigate to the Bitdefender GravityZone Inspector > Select Add System.

Fill in the following information:

  • Type of Inspector: Parent
  • Environment: Select your MSP's Environment
  • Friendly Name: Suggested Naming: [MSP Name] Bitdefender Parent
  • Agent: Select On-Demand Agent
  • Inspector Version: Latest (Auto-Update)
  • API Hostname: The Control Center API Access URL, including the protocol "https://" prefix.
  • API Key: The Client Key copied above. (ensure no whitespace is present)
  • Scheduling: The Inspector will default to run once a day at the time the Inspector is set up. Here you can adjust the schedule

Select Save. The Inspector will now be triggered to run within the minute.

Step 2: Child Inspector Setup

After the first run of the Parent Inspector, your client Bitdefender GravityZone organizations will be Auto-Discovered and surfaced on the Discovered Systems page.

Navigate to the Discovered Systems tab in your Inspectors > Bitdefender GravityZone page

  • Activate your Discovered Systems by ensuring they're mapped to the correct Environment > Select the checkbox to the left of Inspector(s) > Select the Actions drop-down menu > Activate Launchpoints.
  • Users may also Archive Discovered Systems by Selecting the checkbox to the left of the Inspector(s) > Select the Actions drop-down menu > Archive Launchpoints.

Optional: Turn on Flexible Asset/Configuration Auto-Updating

If you would like this Inspector's data to be sent to ConnectWise and/or IT Glue, turn on Flexible Assets/Configurations for this Inspector:

  • ConnectWise: Admin > Integrations > ConnectWise > Configuration Types > Confirm the "Configuration Auto-Updating" toggle is enabled
  • IT Glue: Admin > Integrations > IT Glue > Flexible Assets > Confirm the "Flexible Asset Auto-Updating" toggle is enabled

Common Setup Issues

Invalid value for company ID parameter
Please confirm that the Bitdefender "company" that is being inspected still exists, and that the company ID in the inspector configuration page matches the company ID in your Bitdefender console.

Inspector FAQs