> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/siem-integrations/endpoint-protection/carbon-black.md).

# VMware Carbon Black

ThreatDefence integrates with **VMware Carbon Black Cloud** to collect alerts and endpoint telemetry for continuous monitoring and threat detection.

***

## Integration Steps

### Step 1 — Create a Custom Access Level

1. Sign in to the **VMware Carbon Black Cloud Console**.
2. Navigate to **Settings → API Access**.
3. On the **Access Levels** tab, click **Add Access Level**.
4. Configure:
   * **Name**: e.g., `ThreatDefence Carbon Black`
   * **Description**: e.g., `Access level for ThreatDefence SIEM integration`
   * **Permissions**:
     * In the **Alerts** row → **General Information** → set **READ**

> Note: Selecting this automatically sets the "Copy permissions from" field to **Custom**.

5. Click **Save**.

***

### Step 2 — Create an API Key

1. Go to **Settings → API Access → API Keys tab**.
2. Click **Add API Key**.
3. Configure:
   * **Name**: e.g., `ThreatDefence API`
   * **Access Level type**: `Custom`
   * **Custom Access Level**: select the one created in **Step 1**
4. Save the key and record the following securely:
   * **API ID**
   * **API Secret Key**
   * **ORG Key**
   * **ORG ID**
   * **Hostname / Base API URL**

> These credentials will be used by ThreatDefence to establish secure API-based collection.

***

### Step 3 — Provide Credentials to ThreatDefence

Open a support request via the **ThreatDefence Service Desk** and include:

* API ID
* API Secret Key
* ORG Key
* ORG ID
* Hostname (API URL)

Once provided, ThreatDefence will:

* Validate API connectivity.
* Onboard Carbon Black telemetry into your SIEM view.
* Confirm ingestion of alerts and endpoint activity logs.

***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.threatdefence.com/siem-integrations/endpoint-protection/carbon-black.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.