NetLock RMMNetLock RMM Docs
IV — Administration

Bitdefender GravityZone

Connect NetLock RMM to Bitdefender GravityZone: incidents and quarantine findings become alerts of the matching device or tenant.

Bitdefender GravityZone

Requirements

  • An API key, created in the GravityZone console under My Account, with the APIs Companies, Network, Incidents and Quarantine. The test of the connection lists the APIs the key is missing.
  • The Access URL from the same page, for example https://cloudgz.gravityzone.bitdefender.com/api. Only addresses below gravityzone.bitdefender.com are accepted, so a stored key cannot go anywhere else. An on-premises console cannot be connected.
  • For incidents, a license that includes them. Without one, switch Read incidents off.

Setup

  1. In Settings → Integrations, open the GravityZone tile and choose Connect.
  2. Enter the Instance address and the API key.
  3. Under options, choose what to read: Read incidents, Read the quarantine, and whether a report for an unmatched device goes to the tenant.
  4. Map each tenant to a company, or import the companies. A partner key lists its companies, including those in folders. Companies without a mapping are not included.
  5. Activate the connection.

The token of the connection needs the scopes devices:read, alerts:ingest and external-refs:read.

What arrives in NetLock

Every five minutes NetLock queries GravityZone and reports through POST /v1/alerts/ingest with the token of the connection. Synchronize now starts a pull immediately. Nothing is written in GravityZone.

The first pull only records the current state: existing problems open no alert and no ticket until they change. The Overview tab shows how many there are. Everything after that is reported.

  • Incidents: every pull reads the open incidents and those closed since the last pull. The priority of an incident sets the severity: critical is critical, high is high, medium is moderate, low is low. An unknown priority falls back to the severity score (from 80 critical, from 60 high, from 30 moderate). A closed incident, a false positive or an incident closed after review ends the alert. An organization incident does not name a single endpoint and is reported for the tenant.
  • Quarantine: the findings of the last 14 days of an endpoint become one alert with moderate severity. It ends when the endpoint has no finding left in that time.

The Overview tab shows the time and the counts of the last pull, including skipped items. A pull that changes nothing leaves no line in the History tab. If no pull succeeds for a day, the connection stays active and shows a note.

When a mapping changes, open alerts end at the old tenant and open at the new one; if the mapping is removed, they end. Switching off Read incidents or Read the quarantine ends the alerts that part left open.

How an endpoint finds its device

NetLock tries these in order, always within the tenant of the company:

  1. An external reference of the device for the system bitdefender-gravityzone, set through the public API with the endpoint id of GravityZone.
  2. The match of an earlier pull.
  3. The host name, if exactly one device of the tenant has it. Case and domain are ignored.

Without a match the report goes to the tenant. If Report unmatched devices for the tenant is off, it is skipped and counted. GravityZone does not include serial numbers in these lists, so if two devices share a host name, they need a reference. The External systems tab of the device shows its endpoint, open reports and links to incidents.

Known limits

  • A condition that stays the same is reported again once a day, so its alert does not run into the time limit for open alerts.
  • The malware status of single endpoints is not read; threats arrive through incidents and the quarantine.
  • If the quarantine holds more than 10000 findings in 14 days, it is read only in part. No quarantine alert is then treated as ended until a full read succeeds, and the overview shows a note.
  • If the test of the connection reports that no customer company is visible, connect each company with its own key.
  • GravityZone allows 10 requests a second per key and 5 a second for the company list. NetLock waits when GravityZone reports the limit.