Sections in this category

Carbon Black Cloud

  • Updated

Carbon Black Cloud + JupiterOne Integration Benefits

  • Visualize Carbon Black endpoint agents and findings on corresponding devices in the JupiterOne graph.
  • Map Carbon Black endpoint agents to devices and devices to the employee who is the owner.
  • Monitor Carbon Black findings within the alerts app.
  • Monitor changes to Carbon Black endpoints using JupiterOne alerts.

How it Works

  • JupiterOne periodically fetches new findings from Carbon Black to update the graph.
  • Configure alerts to reduce the noise of findings.


  • JupiterOne requires the deployment site and org key of your account as well as a configured API key and id with the proper permissions.
  • You must have permission in JupiterOne to install new integrations.


If you need help with this integration, please contact JupiterOne Support.

Integration Walkthrough

JupiterOne provides a managed integration for Carbon Black Cloud Platform (formerly the Predictive Security Cloud, or PSC). The integration connects directly to Carbon Black APIs to obtain details about device sensors/agents and active alerts. Customers authorize access by creating a Connector and an API Key in their target PSC account and providing that credential to JupiterOne.

In Carbon Black

You must set up an Access Level and API Key in the Carbon Black Cloud Console to allow access to the Devices and Alerts APIs.

  1. Settings > API Access > Access Levels: Add Access Level: Name "JupiterOne Read Only" (or match your naming patterns), permissions device: READ, org.alerts: READ, org.retention: READ,
  2. Settings > API Access > API Keys: Add API Key: Name "JupiterOne" (or match your naming patterns), Access Level Type "Custom", "JupiterOne Read Only". Capture the API Secret Key and API ID.

With the Access Level and API Key now configured, you'll need to provide these parameters to the integration instance configuration:

  • Deployment Site/Environment (site): The part immediately following defense- in your Carbon Black Cloud account URL. For example, if you access your account at, the site is prod05.
  • Org Key (orgKey): From Settings > API Access, capture the Org Key.
  • API ID (connectorId): Captured during API Key creation.
  • API Key (apiKey): Captured during API Key creation.

In JupiterOne

  1. From the configuration Gear Icon, select Integrations.
  2. Scroll to the Carbon Black PSC integration tile and click it.
  3. Click the Add Configuration button and configure the following settings:
  • Enter the Account Name by which you'd like to identify this Carbon Black account in JupiterOne. Ingested entities will have this value stored in tag.AccountName when Tag with Account Name is checked.
  • Enter a Description that will further assist your team when identifying the integration instance.
  • Select a Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as DISABLED and manually execute the integration.
  • Enter the Deployent Site from the URL in the Carbon Black Cloud Console.
  • Enter the Org Key from the Carbon Black Cloud Console.
  • Enter the API ID configured for JupiterOne.
  • Enter the API Key configured for JupiterOne.
  1. Click Create Configuration once all values are provided.

How to Uninstall

  1. From the configuration Gear Icon, select Integrations.
  2. Scroll to the Carbon Black PSC integration tile and click it.
  3. Identify and click the integration to delete.
  4. Click the trash can icon.
  5. Click the Remove button to delete the integration.

Data Model


The following entities are created:

Resources Entity _type Entity _class
Account carbonblack_psc_account Account
Alert cbdefense_alert Finding
Device Sensor Agent cbdefense_sensor HostAgent
Service cb_endpoint_protection Service


The following relationships are created/mapped:

Source Entity _type Relationship _class Target Entity _type
carbonblack_psc_account HAS cb_endpoint_protection
carbonblack_psc_account HAS cbdefense_sensor
cbdefense_sensor IDENTIFIED cbdefense_alert

Mapped Relationships

The following mapped relationships are created:

Source Entity _type Relationship _class Target Entity _type Direction
cbdefense_sensor PROTECTS *user_endpoint* FORWARD


Was this article helpful?

0 out of 0 found this helpful