Workflow Systems

From reported finding to returned verdict

RiftX fits into the tools security teams already use. A reported issue comes in, the agent retests it, and the evidence bundle flows back into the same operational system.

See the workflow map

Vulnerability Reported

Jira / Burp Suite / API

RiftX Receives

Goal setting & planning

Browser Executes

Real Playwright verification

Verdict Returned

Evidence → back to your tools

System View

Works where your team already works

The point is not to replace your tracker, scanner, or messaging system. The point is to put a verification loop between them and the pentester.

Incoming

Jira / Bug bounty / API

Reported finding enters the queue with steps-to-reproduce.

Verification Layer

RiftX

Replays the report in a browser, captures signals, and builds evidence.

Outgoing

Verdict + artifacts

HAR, GIF, and the final state move back into the workflow.

API Surface

API-first, with integrations layered on top

Native integrations are convenience. The core system is already accessible programmatically from submission to callback.

curl — submit retest

curl -X POST https://api.riftx.io/jobs \
  -H "Cookie: token=vt_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "target_url": "https://example.com/search",
    "vulnerability_type": "reflected_xss",
    "steps_to_reproduce": [
      "Navigate to /search",
      "Enter payload in the q parameter",
      "Observe alert box fires"
    ],
    "callback_url": "https://your-app.com/webhook"
  }'

Operational Notes

Retests can be submitted from your own systems and returned through webhooks.

Evidence URLs, verdict, confidence, and manifest details are shaped for downstream automation.

Webhook bundle

verdict + evidence URLs + sha256 manifest

Connectors

Available now and most requested by beta teams

REST API and webhooks are live today. Jira, Slack, Burp Suite, and ServiceNow are the integrations beta teams ask for most.

available

REST API

Submit retests, poll results, and retrieve evidence programmatically. JSON in, JSON out.

available

Webhooks

Get notified in real time when a verdict is ready. Push results to any endpoint.

available

Jira

Auto-create verified finding tickets with HAR, GIF, and confidence score attached.

available

Slack

Team notifications when verifications complete. Verdict, confidence, and link to evidence.

available

Burp Suite

Right-click a finding in Burp and send it to RiftX for autonomous verification.

available

ServiceNow

Enterprise ITSM ticket creation with full evidence chain for compliance workflows.

Typical scanner flow

Push findings and stop there

Discovery tools create issues and move them into your tracker. The pentester still has to verify and package evidence manually.

RiftX model

Receive tickets and return verified artifacts

A reported finding enters the workflow, RiftX retests it, and the verdict comes back with the evidence bundle attached.

Request a Connector

Need a different integration path?

We prioritize integrations based on real workflows. Tell us what your team already uses and we’ll evaluate the best route in.

Request an Integration