VMware Carbon Black

Connect VMware Carbon Black to collect cloud infrastructure evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In VMware Carbon Black:

   1. In the Carbon Black Cloud console, go to Settings › API Access and open the Access Levels tab.
   2. Open the Add Access Level panel, enter a unique name and description.
   3. Scroll down the table until you see the API Service Categories Safeguard reads, and select only the Read permission for each. Save the access level.
   4. Go to the API Keys tab and select Add API Key.
   5. Enter a unique name, choose the Custom access level type and select the access level you just created, then save.
   6. Copy the API ID and API Secret Key. Store the API Secret Key securely: it cannot be retrieved after initial creation.

   Where to find the other values:

   • Org key: Settings › General and Settings › API Access show the Org Key.
   • API ID: On the API Keys tab, open the key's Actions dropdown and select API Credentials.
   • Environment: The web address of your Carbon Black Cloud console; match it to the hostname table in Carbon Black's authentication guide (for example Prod 02 is https://defense.conferdeploy.net).

   VMware Carbon Black shows the secret only once, so copy it before you leave the page.

   VMware Carbon Black's public documentation does not cover every step.

   The fetched authentication guide does not name the API service categories to grant Read on; the earlier draft named device and org.alerts, which the page does not confirm. Viewing an existing key's API Credentials reveals the API ID but not the API Secret Key.

   Source: developer.carbonblack.com, checked 2026-10-07.

   The permissions Safeguard needs: device: READ, org.alerts: READ.

2. On Compliance › Connectors, open VMware Carbon Black, click Connect, choose API token and fill in:

   Field	What to enter
   Environment	Required. For example: prod05
   Org key	Required.
   API ID	Required.
   API secret	Required. Stored encrypted and never shown again.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read VMware Carbon Black and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Cloud Infrastructure connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks