| 1 | --- |
| 2 | title: Huntress |
| 3 | description: Ingest Huntress telemetry and operationalize it inside CoPilot. |
| 4 | --- |
| 5 | |
| 6 | ## What this integration is |
| 7 | |
| 8 | Huntress provides managed detection/response-style telemetry that can complement endpoint and identity sources. |
| 9 | |
| 10 | ## Data path (how it flows) |
| 11 | |
| 12 | **Typical flow:** |
| 13 | |
| 14 | 1. Huntress → **External Service integration** (API collector or export) |
| 15 | 2. Events → **SIEM storage** (Wazuh Indexer / OpenSearch-backed) |
| 16 | 3. Optional: events → **Graylog** alert definitions |
| 17 | 4. Alerts → `gl-events*` → **CoPilot Incident Management → Alerts** |
| 18 | 5. Operator workflow → **Cases** |
| 19 | |
| 20 | ## What data you get (high level) |
| 21 | |
| 22 | - Alerts/detections (depending on enabled exports) |
| 23 | - Host/agent context (depending on integration design) |
| 24 | |
| 25 | ## Setup (wireframe) |
| 26 | |
| 27 | - Configure Huntress under **External Services / 3rd Party Integrations**. |
| 28 | - Ensure events are tenant-aware. |
| 29 | |
| 30 | ## Success criteria |
| 31 | |
| 32 | - [ ] You can find at least one recent Huntress event/detection |
| 33 | - [ ] It is associated with the expected customer |
| 34 | |
| 35 | ## Dashboards |
| 36 | |
| 37 | - [ ] Confirm dashboards populate (after provisioning) |
| 38 | |
| 39 | ## Alerts (starter set) |
| 40 | |
| 41 | - High-confidence Huntress detections promoted into SOC alerting |
| 42 | - Repeated detections on the same host |
| 43 | - New persistence indicators (if present in telemetry) |
| 44 | |
| 45 | ## Troubleshooting |
| 46 | |
| 47 | - Verify external service status |
| 48 | - Confirm export mechanism (API/webhook) and permissions |
| 49 | - Confirm routing |