Integration Guides Overview
BreachSpider integrates with the tools your security team already uses.
Notification Channels
| Integration | Type | What it sends |
|---|---|---|
| Microsoft Teams | Chat | Connection can be tested; alerts not currently sent |
| Slack | Chat | Connection can be tested; alerts not currently sent |
| Summary email per alert run | ||
| PagerDuty | Alerting | Connection can be tested; alerts not currently sent |
Ticketing Systems
| Integration | Type | What it creates |
|---|---|---|
| Jira | Tickets | Issues with CVE detail, AI analysis, affected assets |
| ServiceNow | Incidents | Incidents mapped to ServiceNow urgency/impact fields |
| Linear | Tickets | Issues in your security project |
Developer
| Guide | Description |
|---|---|
| Python SDK | Official Python SDK (v0.2.0: correlation, Windows patch level, pagination, retry) and plain requests examples |
| JavaScript SDK | TypeScript/JavaScript client with React hooks |
| Webhooks | Signed HTTP POST for each alert (cve.alert) |
| SIEM Integration | Splunk, Elastic, and generic SIEM ingestion patterns |
Getting Started
All integrations require Standard tier or above. Configure them at Integrations in the left sidebar of the BreachSpider dashboard.
For API-based configuration see the Integrations API reference.