Self-hosted vulnerability remediation

Hundreds of findings.
A handful of upgrades.

Hakeem reads your scanner's export, ranks every finding by real-world risk, and turns the top of the list into upgrades your developers can finish in the hours you have. A finding closes only when a later scan shows it's gone.

Runs on your own servers. Never touches your code. Works without internet access.

Where remediation stalls

Your scanner finds the problems. It doesn't tell you which to fix first.

A backlog with no orderThousands of findings, most of them marked critical or high.
→
A ranked plan that fits your weekEvery finding is scored from CISA KEV, FIRST EPSS, CVSS and public exploit data. You set the hours you have, and the plan stops there. Nothing further down is squeezed in to fill the gap.
No one owns itFindings sit on a dashboard and nobody is responsible for them.
→
Sent to the developer who owns the codeYour analyst sends each upgrade to a developer on the team that owns the application. The developer picks a fix or sends it back with a reason. The analyst then replans it, parks it or accepts the risk.
"Did it actually get fixed?"Tickets get closed because someone says so.
→
Proven by the next scanNobody marks work as done. Hakeem closes a finding when a later scan shows the fixed version installed, the scanner reports it closed, or the package is gone.
Nothing to show the auditorAccepted risks live in email.
→
The RecordEvery accepted risk is kept with its reason, compensating control, who approved it and when it's due for review. Every action goes into a tamper-evident audit log.

How it works

Your analyst plans, your developers fix, the next scan checks.

Everyone sees only the work they can act on.

01 / ANALYST

Triage

Upload a scanner export, or have your CI pipeline send a lockfile. Hakeem groups findings by the upgrade that fixes them and ranks them. Your scanner's severity stays exactly as it was. Hakeem's priority sits beside it and sets the order.

02 / DEVELOPER

Fix or push back

The developer gets an email from your own mail server, opens the item in Hakeem, and either picks a fix or sends it back with a note. Developers can't upload or delete scans.

03 / NEXT SCAN

Verify

When the next scan shows the fix in place, the item moves to Remediated, marked Scan Verified. Until then it stays open.

What else it does

Built for the findings a bot can't fix.

No fix released yet, a malicious package, or a risk you've decided to accept.

Malicious packages

When OSV records this package and version as malicious, Hakeem opens an incident and suggests a clean version to move to.

Awaiting a fix

Findings with no fix yet stay on the list and join the plan as soon as a fix is released.

Recheck without a new scan

New advisories are checked against the packages Hakeem already knows each application uses, so an application that hasn't been scanned lately is still covered.

Scanner exports and lockfiles

Wiz and Trivy exports, generic JSON and CSV, and lockfiles from CI: package-lock.json, poetry.lock, requirements.txt, pom.xml, go.mod, Gemfile.lock.

Roles and teams

Admin, analyst and developer. Teams own applications, and developers only see their own team's work.

Signals from the source

KEV from CISA, CVSS from NVD, EPSS from FIRST. Where a scan carries its own copy of a score, Hakeem uses the original source instead.

The Record

Who decided, when, and why.

Every accepted risk keeps its reason and a review date. Sign-ins, credential changes, hand-offs, risk acceptances and refused requests go into an audit log where each entry is linked to the one before, so any tampering shows. The screen tells you whether the chain is intact.

Self-hosted and air-gapped

Runs on your servers. With or without internet.

Hakeem is installed on your own infrastructure and keeps everything in its own database. On a network with no internet, turn on offline mode: it makes no outside requests, works from the catalogue copies shipped with each release, and shows you how old they are.

  • ◆Your servers, your data. Findings, accounts and decisions never leave your deployment. There is no hosted version.
  • ◆Nothing leaves your network. KEV, EPSS and the OSV advisory data come with the release.
  • ◆Always dated. Each catalogue's date is on screen, and you're warned when one gets old.
  • ◆Signed advisory updates. Bring in a newer OSV advisory file between releases, and every application is rechecked against it.
  • ◆Offline licence. A signed file, checked on your own server. Hakeem never sends us anything.

For procurement and the CISO

Least access, by design.

Who it's for

For teams that have to explain their decisions to an auditor.

Banks & credit unions Healthcare Fintech Regional & mid-size regulated firms Air-gapped networks

With forty repositories and no auditor, a pull-request bot is probably enough. Hakeem is for teams that answer for what they fixed, what they didn't, and why.

Pricing

Priced per resource, billed yearly.

A resource is each application or asset your scanner reports.

Resources 1 to 50 $120 / resource / year Minimum 50 resources
Resources 51 to 200 $110 / resource / year Each resource in this band
Resources 201 to 500 $100 / resource / year Each resource in this band
Resources 501 to 1,000 $90 / resource / year Above 1,000: by quote
Resources502003005001,000
Per year$6,000$22,500$32,500$52,500$97,500
Free 14-day trial. Up to 30 resources.
Request a trial

Questions

FAQ

Isn't this just another CVE scorer?

Scoring is only the first step. Hakeem then gives each fix an owner, fits the work to your team's hours, checks the next scan to prove it's done, and records every exception.

Does it replace our scanner?

No. It reads your scanner's export. The scanner's severity is shown as the scanner wrote it, and Hakeem's priority sits beside it.

Won't automated fixing make this obsolete?

When a bot merges an upgrade, the next scan sees it and the item is remediated. The cases that stay manual are the ones Hakeem is for: no fix exists, the fix breaks something, the package is malicious, or the risk is accepted on purpose.

Do you need access to our code?

No. Hakeem takes no source-control credential and never writes to a repository.

How current is the data on an air-gapped install?

As current as the catalogue copies it holds, and each one's date is on screen. A signed advisory store can be installed between releases. KEV and EPSS update with each release.

Stop sorting findings. Start closing them.

We'll walk you through it with a scanner export.

We'll show you Hakeem working through a scanner export, start to finish.

Used only to reply to you.

FEEDBACK