HomeSolutions

Stop triaging maybes. Review proofs.

Nullgap reports a vulnerability only when it can exploit it, and attaches the requests that prove it. Your team spends its time on real problems, not on ruling out alerts.

FoundProvenFixed✓ Proven fixed
A shield next to a card listing the four states: Found, Proven, Fixed, Proven fixed
The problem

Long alert lists hide the few findings that matter.

Most tools tell you what might be wrong. Someone on your team then has to work out which of those are real. Nullgap does that work first, and shows you how it decided.

Only proven findings

The attack works, works again, a harmless control doesn’t, and an independent check accepts it. A status code alone never counts.

Replay every proof

The exact requests and sandbox output ship with each finding. Anyone on your team can run it again.

See what was ruled out

Leads that were tested and shown not to be exploitable are listed, so you know what was covered.

Access control across accounts

Up to five named identities per target, plus signed-out. The access matrix proves who can read whose data.

A researcher when you need one

Ask a Nullgap security researcher to check a finding or a whole report by hand.

Controls you can audit

Owner, admin and member roles, SSO and SCIM, required MFA, and a hash-chained audit log you can export.

What your team sees

A short list, each line backed by evidence.

Findings across a sample workspace
FindingSourceState
Read-only user can delete a projectLive testing · access matrixProven
Any signed-in user can read any invoiceWhitebox pentestFixed
SQL injection in the report filterPull request review✓ Proven fixed
9 other leads testedShown not to be exploitableRuled out
Illustrative sample.
Products for this

Questions security teams ask

How do we know a finding is real?

Each finding passes four checks and ships with the requests that prove it. You can replay it yourself. How proof works.

What happens to leads Nullgap can’t prove?

They aren’t reported as findings. They are listed as ruled out, so you can see what was tested.

Can we export findings into our own tools?

Yes. Findings export as SARIF or CSV, and the audit log can be exported too. Jira, Slack, webhooks and the REST API are available.

How is our code and data handled?

Code is checked out per run and deleted after. AI prompts and responses are never stored, and credentials are masked and never sent to the AI. See Security and trust.

✓ Proven fixed

Get your first proof today.

Connect a repository and watch Nullgap find, prove and fix. You only ever see what it could prove.

Free 14-day trial · No card · or book a demo with a security engineer