Integrations
Integrations
Route verified findings and reports into Slack, Jira, and any system via webhooks — with setup steps and payload examples.
Integrations put RedStrike findings where your team already works. Send verified findings to Slack, open Jira tickets automatically, or stream events to any endpoint with webhooks.
TL;DR
Connect Slack for alerts, Jira for ticketing, and webhooks for everything else. Filter by severity and verification status so only the findings you care about create noise. All integrations are configured per organization.
Slack
Get notified when new verified findings appear.
- Go to Settings → Integrations → Slack and click Connect.
- Authorize the RedStrike app and pick a channel.
- Set a filter — for example, Verified + High/Critical only.
A message looks like:
🔴 New Verified Critical — app.example.com
SQL injection in /api/search (parameter: q)
Scan: Standard · Finding fnd_88a2 · View in RedStrike ↗
Jira
Turn findings into tracked work automatically.
- Connect your Jira site under Settings → Integrations → Jira.
- Map a project and issue type (e.g. project
SEC, typeBug). - Choose a trigger — for example, create a ticket for every Verified High+.
RedStrike keeps the ticket in sync: when a re-scan marks the finding Fixed, it can transition or comment on the linked issue.
| Finding field | Jira field |
|---|---|
| Title | Summary |
| Severity | Priority |
| Evidence + remediation | Description |
| Finding URL | Linked remote link |
Webhooks
For anything else — SIEM, PagerDuty, custom automation — use webhooks. Add an endpoint under Settings → Integrations → Webhooks and select events.
POST https://hooks.example.com/redstrike
{
"event": "finding.verified",
"org_id": "org_1",
"finding": {
"id": "fnd_88a2",
"severity": "critical",
"status": "verified",
"target": "app.example.com",
"title": "SQL injection in /api/search",
"url": "https://app.redstrike.io/findings/fnd_88a2"
}
}
Each delivery is signed so you can verify authenticity:
X-RedStrike-Signature: sha256=HMAC(secret, body)
Filter aggressively. Sending only Verified + High/Critical to Slack keeps signal high; route the full firehose to a webhook/SIEM for record-keeping.
Available events
| Event | Fires when |
|---|---|
scan.completed | A scan finishes |
finding.created | A new finding is recorded |
finding.verified | A finding is confirmed exploitable |
finding.fixed | A re-scan confirms a fix |
report.generated | A report is ready to download |
Next
- Findings & Verification — what triggers alerts.
- API Reference — manage integrations programmatically.