Repository navigation
brainproxy 0.6.0
brainproxy 0.6.0
Reports you can hand over. Secrets are masked by default, findings become records with a history, and reports come in presets, with your branding, as PDF or Word. What an agent writes only reaches a report once a person has read it.
Schema change (v14 → v17): a project opened with 0.6.0 can't be opened by 0.5.x again. Keep a copy if you need to go back.
Changed: check these before updating scripts or CI
- Reports mask session secrets by default in every format: cookie values,
Authorizationcredentials, API-key headers, secret-named parameters, hidden fields, JWTs, and your auth profiles' passwords and tokens. A value masked in one place is masked wherever else the report quotes it.--no-redactkeeps everything, and the report says so. findings listand reports show work still to do by default: open, confirmed and retest pending. They used to show everything except false positives. Pass--state allfor everything.- SARIF fingerprints are
brainproxy/v2. They hash the alert, method, URL without its query, and parameter. The first upload after updating may show existing alerts as closed and reopened. - New risk level: Critical. Checks and vulnerable JavaScript libraries rated critical are now critical instead of high. A finding seen again at a higher risk is promoted.
- New states:
fixed,accepted_riskandretest_pending. Gates never count an accepted risk or a fixed finding.
New
- Issues (#95): one issue per alert type on one host, with the findings it was seen at (
findings issues,findings issue show | split | merge | title).findings mark --issue Ntriages them all. - Timelines (#95):
findings timeline IDshows who did what and when (created, triaged, retested, regressed, moved, removed).- A finding marked fixed reopens when a scanner sees it in traffic recorded after the mark.
- Retest (#95):
findings retest IDsends a passive finding's request again and marks it fixed when it no longer shows.- It refuses rather than guess: a disabled rule, or a login redirect or error page in reply.
- It sends only GET, HEAD and OPTIONS unless
--allow-unsafe, and stays within scope.
- Posture (#95):
findings posturegives open work at a glance, plus what each active scan found new or no longer found. - Report presets and branding (#96):
report --preset technical | executive | developer | retestpicks the sections, or--sectionssets them directly.- The developer preset has a curl line per finding; the retest preset is a letter of what changed since
--since. --company,--accentand--logogo on the cover.report-profile save | list | show | removekeeps layouts by name.
- PDF and Word (#96):
report pdfprints through a headless Chromium, which fetches nothing;report docxwrites a Word document. - CVSS 4.0 (#96):
findings issue cvss ID VECTORrates an issue, and reports and SARIF use the score. - The report builder in the app (#96): audience, sections, branding and format, with a live preview. Layouts can be saved.
- Reviewed write-ups (#97):
findings issue narrativeandreport-summary setwrite an issue's write-up and the executive summary.- A new text is a draft until a person reviews it, by the hash of exactly what they read:
findings issue review ID --hash H, or Mark reviewed in the app. - Reports leave drafts out unless
--drafts. - Reviewing is refused through MCP.
- Agent trail (#97):
findings trail IDlists what an agent did for a finding: its requests around it, its changes, and the first change a person made afterwards. Reports tag agent-touched findings as reviewed or not. - Repro packs and tickets (#97):
findings repro IDgives the masked request, a curl command, the response around the evidence and the command that checks it again.findings ticket ID --to github|jirawrites a ticket and sends nothing.--record URLkeeps the filed ticket's link on the finding. It is refused through MCP.
- Exports (#97):
report csv(formula injection defused),report junitandreport defectdojo(with the fingerprint asunique_id_from_tool). - Bulk triage (#94):
findings mark 7 8 9 --state confirmedmarks several findings: all of them change, or none does.- The app's findings view has search, source and host filters, checkboxes for bulk marking, and a note editor.
- A finding's latest sighting (#94) is shown next to its first.
- CI baselines from a file:
findings compare --scan J --baseline FILEcompares a scan against a savedreport json, matching by fingerprint, so a redacted baseline still compares as unchanged.findings mark --from FILEcopies a file's marks (confirmed, false positive, accepted risk) onto the findings that match, from areport jsonor a list of known false positives. It is refused through MCP.
Fixed
- A flaky authz live-mode test (#98).