Skip to main content
Integrations

Pentest Tool Integrations,
Straight into the Report

31 integrations across C2, phishing, Active Directory, network, vulnerability, web, cloud, mobile, external intelligence, and ticketing. Just test. The timeline writes itself.

How It Connects

Every Tool. One Engagement.

However a tool connects, its results land on the same engagement, next to every command you ran from the recording shell, attributed and timestamped.

Collectors

$ neuron collector mythic

Stream a C2 or phishing server into the engagement for as long as it runs. Every task, callback, capture, and credential lands on the timeline the moment it happens.

Run Through neuron

$ neuron nmap -sV 10.20.0.0/24

Put neuron in front of a tool and it runs exactly as before. When it finishes, the results import and the command lands on the timeline. Add --ssh to run it on a jumpbox.

Imports

$ neuron import *.nessus

Import scanner output from the browser or the CLI. Hosts, ports, and web apps are created, and every reported issue lands in one triage queue, ready to promote into a finding.

Extensions and Ticketing

Send requests straight from Burp Suite, ZAP, and Caido as you test, and push approved findings into ServiceNow and Jira when the report is done.

Web Testing Integrations

Send traffic from your proxy, scan, and fuzz, and every result lands against the web app it belongs to.

Extension

Burp Suite Reporting and Findings Import

Send Burp Suite requests and Scanner issues straight into your engagement, with request and response evidence attached. Burp Suite reporting without copy and paste.

Extension

ZAP Reporting and OWASP ZAP Alert Import

Send OWASP ZAP requests and alerts into your engagement with the Neuron ZAP add-on, or import a HAR export. ZAP reporting with every alert in one triage queue.

Extension

Caido Reporting and HTTP History Import

Send Caido requests and findings into your engagement with the Neuron plugin, or import an HTTP History export. Caido reporting with request evidence already attached.

Import

OpenAPI and Swagger Import for API Pentests

Import an OpenAPI or Swagger spec and every endpoint, method, and parameter lands in your engagement as API pentest scope, mapped before the first request is sent.

Run through neuron

Nuclei Scan Reporting and Import

Run Nuclei through the Neuron CLI and every result lands in your engagement as a scan issue, ready to promote into a finding. Nuclei reporting without a conversion script.

Run through neuron

ffuf Reporting and Content Discovery Logging

Run ffuf through the Neuron CLI and every hit lands in your engagement against the web app it belongs to. Content discovery reporting without copying terminal output.

Import

Nikto Reporting and Output Import

Import Nikto XML or JSON output into Neuron and every finding lands against the host, port, and path it hit, ready to triage. Nikto output to report, no copy and paste.

Import

Acunetix Report Import for Pentest Reports

Import Acunetix XML reports into Neuron and every vulnerability lands with the request and response that prove it, mapped to its endpoint. Acunetix report import.

Import

Invicti and Netsparker Report Import

Invicti report import for current JSON and legacy Netsparker XML exports. Every vulnerability lands with its proof of concept, request, and response, ready to triage.

Integrations FAQ

Which pentest and red team tools does Neuron integrate with?

Neuron integrates with Mythic, Sliver, Metasploit, GoPhish, Evilginx, NetExec, Certipy, BloodHound, Nmap, Masscan, PCAP, Nessus, Qualys, OpenVAS, Nexpose, Burp Suite, ZAP, Caido, OpenAPI, Nuclei, ffuf, Nikto, Acunetix, Invicti, Prowler, ScoutSuite, MobSF, Shodan, Censys, ServiceNow, and Jira. Anything else you run inside the Neuron recording shell is logged to the engagement timeline with its output.

What is the difference between a collector, an import, and running a tool through neuron?

A collector streams a long-running server, such as a C2 framework or phishing platform, into the engagement for as long as it runs. Running a tool through neuron wraps a single command and imports its results when it finishes. An import takes a file a tool already wrote, from the browser or with neuron import.

Where do imported scanner results go?

Hosts, ports, web apps, and endpoints are created or updated on the engagement. Anything a scanner reported as a problem lands in the Scan Issues queue, where a tester triages it and promotes confirmed issues into findings.

Does any of my tool data leave our network?

No. Neuron is self-hosted. The CLI, the extensions, and the importers all send to your own Neuron server, inside your infrastructure, and nothing passes through a third-party cloud.

Can Neuron push findings into our ticketing system?

Yes. Workflow Integrations push approved findings into ServiceNow and Jira with your own field mapping, routing rules, and evidence attachments. Later pushes update the same record instead of creating a duplicate.

What if I use a tool that is not listed here?

Run it inside the Neuron recording shell and every command and its output is logged to the engagement timeline, attributed and timestamped. If it writes a file in a supported format, the shell offers to import it.

Ready to Transform Your Security Practice?

See how Neuron helps security teams replace fragmented tools with a single platform for offensive security, bringing structure, visibility, and consistency to every engagement.

One
Platform
End-to-end engagement management
Full Data Control
On-prem and isolated environments
Built by Practitioners
Designed for real security work