Evidence Connector for Burp Suite

Overview

The SecEng Evidence Connector for Burp Suite uses the Montoya API to passively capture HTTP traffic and send AI-related findings to the local SecEng sidecar. It creates native Burp issues for each finding and surfaces them in the Burp UI — no separate tool required. Everything runs locally; no traffic leaves the machine.

Features

1. 01.

   Passive HTTP listener

   Monitors all HTTP/S traffic flowing through Burp Proxy and forwards AI-related requests and responses to the sidecar for analysis.

2. 02.

   Native Burp issue creation

   Findings are reported as first-class Burp issues with severity, confidence, and detail fields — exactly like any other Burp scanner finding.

3. 03.

   Evidence attachment

   Attach scan findings to your SecEng program as structured evidence, linking HTTP evidence to your AI risk inventory.

4. 04.

   Local first — no data exfiltration

   All analysis happens inside the sidecar on 127.0.0.1. Traffic never leaves the pentester's machine.

5. 05.

   Context menu scanning

   Right-click any request in Burp's history to manually trigger a SecEng analysis on a specific payload.