> For the complete documentation index, see [llms.txt](https://docs.cybaops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybaops.com/getting-started/onboarding/connectors/bitdefender.md).

# BitDefender

The BitDefender connector works by syncronising data from your account to the MDR module in your CybaOps account.   

It is one-way, and only takes information from Bitdefender to CybaOps. It does not push data from CybaOps to BitDefender.  

## <mark style="color:$primary;">Guide</mark>

This guide will help you to:&#x20;

* **Give the SOC team access to your Bit Defender**&#x20;
* **To collect**&#x20;
  * **Organisation ID** &#x20;
  * **API Secret** &#x20;

And ensure the correct permissions are enabled:&#x20;

* **Incidents access** &#x20;
* **Event Push Service access**&#x20;

*<mark style="color:$info;">If you do not have BitDefender prior to CybaOps, then set up of the connector will be completed in your onboarding call.</mark>* &#x20;

### <mark style="color:$primary;">Step 1: Create an account in your AD/ EntraID to be used for the creation the API key</mark>&#x20;

Create a dedicated account that you will use to create the API key. This should not be tied to an individual user, so it remains active if the person who set it up leaves the company.&#x20;

### <mark style="color:$primary;">Step 2: Add the account as company administrator in BitDefender</mark>&#x20;

Go to the Bitdefender GravityZone console:&#x20;

[https://cloud.gravityzone.bitdefender.com](https://cloud.gravityzone.bitdefender.com/)&#x20;

Log in with an account that has **administrator access**. &#x20;

Add the account mentioned on the step above under the company you want CybaVerse to monitor.&#x20;

### <mark style="color:$primary;">Step 3: Log into BitDefender Gravity Zone with the account you have created</mark>&#x20;

Go to the Bitdefender GravityZone console:&#x20;

[https://cloud.gravityzone.bitdefender.com](https://cloud.gravityzone.bitdefender.com/)&#x20;

### <mark style="color:$primary;">Step 4: Get Your Organisation</mark> &#x20;

1. In the GravityZone console &#x20;
2. Go to: **Control Center → My Company** &#x20;
3. Locate: **Organisation ID**&#x20;

This is often your account identifier (sometimes an email or company ID depending on setup). Copy this and paste it into the relevant field in CybaOps.&#x20;

### <mark style="color:$primary;">Step 5: Generate API Secret</mark> &#x20;

1. Log in to GravityZone with the account you have just created and added in BitDefender&#x20;
2. In GravityZone, go to: **Settings → API** &#x20;
3. Click: **Add API key** &#x20;
4. Give it a name (e.g. CybaOps Connector) &#x20;
5. Set permissions &#x20;
6. Generate the key

Ensure you enable:&#x20;

1. Incidents (Allows CybaOps to pull security incidents)&#x20;
2. Events Push Services (Allows CybaOps to receive real-time event data)&#x20;

Copy the **API Key / Secret**, paste this into the Secret field in CybaOps.&#x20;

### <mark style="color:$primary;">Step 6: Give CybaVerse SOC access</mark> &#x20;

This will be outlined during your onboarding call.

### <mark style="color:$primary;">Data Synchronisation</mark>

Synchronisation is handled via a webhook from Bitdefender, which sends data to CybaOps whenever new events occur. CybaOps performs a health check every **five minutes** to ensure data is being received correctly.&#x20;

If an issue is detected, the system will automatically switch to checking **every 30 minutes** until the connection is restored.&#x20;

If you believe the issue has been resolved, you can manually trigger a check by selecting the three dots on the Bitdefender schedule and clicking Bump.&#x20;

#### <mark style="color:$primary;">What data is taken from BitDefender?</mark> &#x20;

Data syncronised from BitDefender:

* **Events**&#x20;
* **Incidents**&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cybaops.com/getting-started/onboarding/connectors/bitdefender.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.