Every vulnerability matters

ScanSuite finds them in your code, dependencies and secrets, proves which ones are real, and follows each one from first detection to a verified fix, with the same answer on every scan. Self-hosted, with your own models.

  • On-premise, private cloud or air-gapped
  • Your model: hosted, gateway or local
  • Keeps the scanners you already license
ScanSuite Products page: every product ranked by open risk, with a Needs attention list and a 12-week trend of open findings
30+
languages read by AI SAST, 39 vulnerability classes
~155k
CVEs with exploitation evidence, held locally
3+AI
secret scanners, one verdict: real or not
30+
open-source and commercial scanners orchestrated
1
record per issue, across every scan
AI code security

Everything in your repository, checked the way a reviewer would

Code, dependencies and secrets in one scan; every finding lands in one record you can triage, prove and close on evidence.

AI SAST

Reads code like a reviewer, reports like an auditor

Finds broken authorization and business-logic flaws no rule describes, and shows how each one is reached before it is reported.

AI SAST
30+ languages, 39 vulnerability classes
Every finding shown with the path that reaches it
A fix with corrected code for High and Critical
DEPENDENCIES

Dependency risk verification

Only advisories that are exploitable and reached by your code.

  • Known exploit: KEV, public exploit or PoC
  • Installed version checked against the range
  • Call path traced into your code
Dependency reachability
SBOM

Software bill of materials

Every component of every repository, kept current.

  • Direct and transitive, licences, manifest line
  • Re-checked when the exploit database changes
  • CycloneDX, XLSX and CSV
Static analysis
SECRETS

Secrets verification

Several scanners, one verdict.

  • The current code and its full git history
  • AI verdict: real, placeholder, not a secret
  • Hide secrets from AI: models see redacted code
Secrets detection
FIX CHECK

Resolved means verified

An agent reads the current code before anything closes.

  • Cites the line that fixed it
  • Moved or still present keeps it open
  • Verify Fixes on demand
Fix verification
PROOF OF CONCEPT

Settle severity with a run

Generated from the finding, run in a sandbox.

  • Editable before it runs
  • Read-only, unprivileged, time and memory capped
  • Refine it from a failed run's output
Proof of concept
CI/CD

Fail the build on what matters

One command in any pipeline.

  • GitLab, GitHub, Jenkins, Azure DevOps, Bitbucket
  • Gate on severity, class, reachability, secrets
  • SARIF, JUnit, changed-files scans
CI/CD
Dependency risk

From every CVE in the lock file to the few that matter

Four gates, each with its evidence on the finding. What passes all four is worth a developer's afternoon.

GATE 1

Critical or High

Severity floor from the advisory.

GATE 2

Known exploit

KEV, public exploit or PoC in the local database.

GATE 3

Your version is affected

Installed version checked against the affected range.

GATE 4

Your code reaches it

Call path traced from your code to the vulnerable function, with a diagram.

Reproducible results

Run it again. Get the same answer.

Scan the same code twice and get the same findings. Each new scan adds only what changed.

Example · one repository, four scansfinding SHOP-7F3A21
SCAN 1
14 found
Each with its evidence
SHOP-7F3A21 · open
SCAN 2
Same 14
Nothing new, nothing re-rated
SHOP-7F3A21 · open
SCAN 3
1 new · 2 fixed
Fixes confirmed in the code
SHOP-7F3A21 · open
SCAN 4
SHOP-7F3A21 fixed
Closed with the proof
SHOP-7F3A21 · resolved

Same issue, same record

A finding keeps its ID and history from the first scan to the last.

No surprises between runs

What was confirmed stays confirmed, at the same severity. Only new code brings new findings.

Closed only when fixed

A finding closes when the fix is confirmed in the code, and reopens if the issue comes back.

Vulnerability management

From finding to verified fix, in one place

Findings from every engine and every scanner follow the same path, with a full history on each one. Hand them on to DefectDojo, ServiceNow, XLSX, HTML, PDF or PowerPoint.

Deduplicated

One record per issue, however many scans report it.

Triaged

Every decision needs a reason. False positives can become suppression rules.

Owned

An owner and a due date by severity: 7, 30, 90 or 180 days by default.

Fixed

A deep link to the line, the suggested fix and the evidence.

Verified

Closed when the fix is confirmed, reopened if the issue comes back.

Product tour

What your team works with every day

Screens from the product, unedited. Click one to see it full size.

Products page ranked by open risk
Products ranked by open risk, with a Needs attention list and a 12-week trendDocs
Beyond the code

Web, infrastructure and the hosts behind them

Proven open-source and commercial scanners, run on schedule against the targets your team allows, with results in the same vulnerability record.

Web and API

  • Websites and APIs, from quick checks to deep scans
  • APIs tested from their OpenAPI specification
  • Signed-in scans behind a login
  • Web application firewalls detected first
Web scanning

Infrastructure

  • Vulnerability scans of hosts and networks
  • Network discovery with service versions
  • Signed-in patch checks on servers
  • Domain reconnaissance and container images
Infrastructure checks

Assets

  • Every host, ranked by risk from its open findings
  • Technologies and services views
  • Saved filters and bulk actions
  • Deletion you can undo for 7 days
Assets
Issues several scanners report on one endpoint become one finding, enriched from the local exploit database. Scans reach only targets on the team's allow-list.
Self-hosted or air-gappedOne-command install and update
Your modelsOpenAI-compatible, Claude, Vertex AI, Azure or local, routed per task
Cost per scanTokens and money, per model and task
Teams and rolesSSO, team API tokens and audit logs
Request a demo

See it find, prove and explain on your own code

A working session on real findings, not a slide deck.

  1. 1
    A walkthrough on a sample applicationAI static analysis, dependency reachability and fix verification, end to end.
  2. 2
    Your deployment questions answeredAir-gapped installs, model choice, sizing and integrations.
  3. 3
    A trial installation, if it fitsRun it on your own repositories, inside your own network.

Tell us about your environment

We come back to you by email to arrange a time.

Protected by reCAPTCHA.