| 1 | --- |
| 2 | title: Carbon Black Cloud |
| 3 | description: Ingest Carbon Black Cloud alerts into the SOCFortress SIEM stack. |
| 4 | --- |
| 5 | |
| 6 | ## What this integration is |
| 7 | |
| 8 | This integration ingests **VMware Carbon Black Cloud** alert data into your SOCFortress SIEM stack using the Carbon Black Cloud APIs. |
| 9 | |
| 10 | --- |
| 11 | |
| 12 | ## Data path (how it flows) |
| 13 | |
| 14 | 1) Carbon Black Cloud → API polling/collector |
| 15 | 2) Collector → SIEM ingestion (indexing/search) |
| 16 | 3) Optional: alerting + routing into Incident Management |
| 17 | |
| 18 | --- |
| 19 | |
| 20 | ## Prerequisites |
| 21 | |
| 22 | - Carbon Black Cloud console access |
| 23 | - API access enabled |
| 24 | |
| 25 | Vendor reference: |
| 26 | - Alerts API: https://developer.carbonblack.com/reference/carbon-black-cloud/platform/latest/alerts-api/ |
| 27 | |
| 28 | --- |
| 29 | |
| 30 | ## Credentials & permissions you’ll need |
| 31 | |
| 32 | From the Carbon Black Cloud console: |
| 33 | - API ID |
| 34 | - API Secret Key |
| 35 | - ORG Key |
| 36 | - ORG ID |
| 37 | - Base API hostname (e.g., `https://defense.conferdeploy.net`) |
| 38 | |
| 39 | The recommended pattern is to create: |
| 40 | 1) a **custom access level** with **Alerts: READ** |
| 41 | 2) an **API key** bound to that access level |
| 42 | |
| 43 | --- |
| 44 | |
| 45 | ## CoPilot setup (recommended workflow) |
| 46 | |
| 47 | 1) Provision the customer (tenant wiring). |
| 48 | 2) In CoPilot → customer → Integrations → **Add integration** → **Carbon Black**. |
| 49 | 3) Paste the API credentials + org identifiers. |
| 50 | 4) Deploy/start the collector/connector component (if your deployment model uses a containerized collector). |
| 51 | |
| 52 | --- |
| 53 | |
| 54 | ## Success criteria |
| 55 | |
| 56 | - [ ] Carbon Black alerts are arriving |
| 57 | - [ ] Alerts/events are tagged to the correct customer |
| 58 | |
| 59 | --- |
| 60 | |
| 61 | ## Troubleshooting |
| 62 | |
| 63 | - Confirm API key permissions include alerts read access. |
| 64 | - Confirm ORG identifiers match your tenant. |
| 65 | - Validate base URL/region (commercial vs other environments). |
| 66 | - Check collector logs for rate limiting/auth failures. |