vigolium server is also the local backend for the Vigolium Burp extension. The extension connects to your running server, ingests traffic through /api/ingest-http, and triggers scans through the server scan APIs. Findings then appear in both Burp and the Web UI because they are stored in the same Vigolium database.
What you get inside Burp
- A Findings table fed live by Vigolium as it scans.
- The full Request / Response pair for the selected finding.
- A scan stream showing each module as it runs against the ingested request.
- Context-menu actions for Send to Vigolium, Send to Native Scan, and Send to Agentic Scan.
Configure the extension
Open the Settings tab in the Vigolium panel and point the extension at your local server.
| Section | What it controls |
|---|---|
| Server Connection | Vigolium API endpoint, such as http://localhost:9002, and the API key from VIGOLIUM_API_KEY. Click Test Connection before ingesting. |
| Scan Options | Optional parameters sent with every ingested request, such as timeout, scan ID, or module overrides. Leave blank for server defaults. |
| Keyboard Shortcuts | Bindings for Send to Vigolium, Send to Native Scan, and Send to Agentic Scan. |
| Proxy Interception | Forward requests flowing through Burp Proxy to Vigolium. Combine with Only in-scope requests to limit ingestion to your Burp target scope. |
| Request Statistics | Live counters for forwarded, succeeded, failed, queued, and in-flight scan counts. |
| Proxy Filter Rules | Allow or deny traffic by file extension, HTTP method, or host so static assets and out-of-scope hosts do not pollute the database. |