October 2026: Neuron Goes Where the Testing Happens
Testing happens in a proxy, a terminal and a C2. The proxy and the team server keep their own records, the terminal keeps one only if someone remembered to start logging, and the screenshots sit in a folder. None of it sits with the engagement, so writing the report starts with pulling them back together. Our October releases went after that distance.
Your proxy, paired with the engagement
For web testing, we rebuilt the Burp Suite extension and gave it two siblings, a ZAP add-on and a Caido plugin. Each one pairs with a single Neuron engagement, and the connection runs both ways.
Requests go in with cookies, tokens and authorization headers stripped before they are stored. Scanner issues land in the engagement’s triage queue, and sending them a second time never undoes a decision someone already made. Scope set in Neuron syncs into the proxy, with a preview before anything changes. In the other direction, any stored request opens in Burp Repeater, ZAP’s Requester or Caido’s Replay. The story is at Burp Suite, ZAP and Caido, paired with the engagement (opens in a new tab).
A terminal that writes the timeline
Late in the month came the Neuron CLI (opens in a new tab). It runs on the tester’s laptop, pairs with an engagement, and starts a recorded shell, locally or over SSH on the box they test from. Every command and its output lands on the engagement’s timeline as it runs.
Scans run through the CLI are imported when they finish. The engagement’s in-scope hosts or web apps come back out as a plain list, ready for the next tool.
The operation, already documented
On red team work, the implant’s side of the operation lives in the C2. The CLI’s collectors stream a Mythic or Sliver operation into the engagement while it runs: tasks, callbacks, credentials and downloaded files, each with the operator who ran it. On a Mythic operation, every artifact Mythic tracks, such as a process started, a file written or a registry key set, also becomes its own entry linked to the host, so the cleanup list has a head start while the operation is still running. Select a run of events and they become a finding, written into its evidence as one story, step by step. The Neuron CLI and your C2 on the timeline (opens in a new tab) covers the whole workflow, and a short video of a Mythic operation (opens in a new tab) shows the events arriving live.
Evidence fit to send early
Two of October’s stories were about what leaves the engagement.
Print Memo (opens in a new tab) turns selected findings into a document of their own, ahead of the full report. The output can be split per finding, per group or per assessment, so each team on the client side receives only its own. The memo comes from the same reviewed finding that will appear in the final report, and it carries a clear notice when something in it has not passed QA yet.
Screenshots got an image editor inside Neuron (opens in a new tab). It reads the text in a screenshot and suggests redactions for passwords, tokens and hashes. Saving a redaction replaces the original in every document and revision in the engagement that uses it, rather than leaving the secret under a box. The image editor video (opens in a new tab) walks through it.
Also shipped
- Time off and holiday calendars on the schedule, so staffing counts only the days people are actually working.
- Keyword search across findings, notes and the contents of files, one shortcut away from any page.
- Engagement boards rebuilt as kanban lists, holding hosts, findings and credentials beside the team’s own task cards.
- Library-linked findings that pull in newer library wording, with a merge review that keeps the tester’s own edits.
- File share previews for PDFs, spreadsheets and Word documents, and CSV files that open in a grid collaborators edit together.
The thread through it
None of this asks a tester to change tools. Burp stays Burp, and Mythic stays Mythic. What changes is that the engagement keeps up with them, so the report starts from a record instead of a reconstruction.
See the proxies, the CLI and the collectors working on one engagement at neuron.ws/demo (opens in a new tab).
Get the next one by email.
Neuron product news and what we are building at PenTest.WS, sent to your inbox. Unsubscribe anytime.
See Neuron on your terms.
Tell us about your team and environment. We will show you Neuron running the way you would run it: on your infrastructure, under your control.