Our engineers set up and run your first chatbot / LLM security scan. Get in touch →

Findings reach the systems your team already operates.

Webhook, chat, ticketing, and SIEM destinations ship with the platform. Credentials are stored with authenticated public-key cryptography at rest, outbound calls are SSRF-guarded against private and reserved IP ranges, and a bearer-token API covers headless workflows.

HMAC-signed webhooks

Custom HTTP POST to any HTTPS endpoint. Payload is signed with HMAC-SHA256; SSRF guard rejects loopback, link-local, RFC 1918, and multicast targets and re-checks hostname-IP resolution at fire time.

HMAC-SHA256SSRF guardedRetry + DLQ

Slack

OAuth 2.0 install with channel and severity routing. Findings post with severity colour, framework chips, and a deep-link back to the finding detail in the console.

OAuth 2.0Channel routingSeverity filter

Jira

API-token or OAuth authentication. Create an issue on finding; link the issue key back to the finding so closing in either system is reflected in both. Custom field mapping per project.

Issue create + syncCustom fields

Splunk HEC

HTTP Event Collector destination with index and sourcetype routing. Event payload carries the finding identifier, severity, framework references, judge rationale snippet, and timestamps.

HECIndex routingSourcetype

QRadar

Syslog over HTTPS or Log Source API. Common Event Format with Penaxtra custom properties for framework references, evidence snippet, and severity.

CEFSyslog over HTTPSCustom properties

Bearer-token public API

The same data your console reads is available over /api/v2 with per-scope access tokens. Endpoints cover assets, scans, findings, reports, audit log, and gateway events.

/api/v2Per-scope tokensRate-limited

How credentials and delivery are handled

01

At-rest encryption

Every credential (OAuth tokens, API tokens, webhook signing secrets, SIEM tokens) is encrypted at rest with X25519 sealed-box authenticated encryption. The encryption key lives outside the application repository in a restricted-access configuration store.

02

Test before save

Every integration has a Test action that performs a real round-trip against the destination before the secret is persisted. Failed tests surface the upstream error verbatim.

03

Retry and observability

Webhooks retry on 5xx with exponential backoff up to the dead-letter queue. Delivery history is browsable per integration so on-call engineers can audit a missed alert.

Want an integration we have not built yet?

Tell us the destination and the use case; we will scope it against the bearer-token API or a new native connector.

Talk to sales →