Exploitability validationNot every vulnerability is exploitable.

95% of your vulnerabilities cannot be exploited. Onit's Exploitability Agent checks whether an attacker can actually exploit your vulnerabilities, with proof.

Watch the Exploitability Agent at work.

One CVE, checked on every Linux server. Nothing installed, nothing changed.

One verdict moves the whole queue.

Your scanner ranks findings by score. The Exploitability Agent validates whether the vulnerability's requirements exist, on every asset that you own. Exploitable moves to the top. Not exploitable drops to the bottom, with proof.

Exposures

4In queue

0Exploitable

0Deprioritized

  1. 1OpenSSH regreSSHionCVE-2024-6387lnx-web-07Not checked92
  2. 2Windows PrintNightmareCVE-2021-34527win-print-03Not checked88
  3. 3HTTP/2 Rapid ResetCVE-2023-44487api-gw-02Not checked85
  4. 4glibc Looney TunablesCVE-2023-4911lnx-app-11Not checked81

How do you know if an exposure is exploitable?

Every attack needs certain conditions on the machine. The agent works them out from the advisory, the patch and public exploits, then checks each asset for their existence.

lnx-web-12 has all four conditions the attack needs, so it's exploitable (risk 100). lnx-web-07 is missing one, 'LoginGraceTime = 0', so it's not exploitable (risk 30).

  • 01 ยท Check

    Looks at the asset itself

    Reads files, registry keys and config files. With nothing installed. And, no changes needed.

  • 02 ยท Prove

    Shows evidence

    Each verdict comes with what the attack needs, what it found, and how it checked. Evidence your IT and infrastructure teams need.

  • 03 ยท Watch

    Checks again

    Assets get rebuilt and settings rolled back. When conditions change, so does the finding.

regreSSHion across a Linux fleet

Fixed today. Still fixed next week?

IT says the fix for the OpenSSH bug (CVE-2024-6387) went out to all 400 servers. The agent proves that 340 have a setting that blocks the attack and 60 do not, and then keeps checking every day. When a rebuild makes a server exploitable again, it knows that day.

"Not exploitable" is never "ignored." It's closed for a reason, and it reopens when that reason goes away.

Watch ยท CVE-2024-6387 ยท 400 Linux servers

Day 1: 60 of 400 are exploitable.

The other 340 have a setting that blocks the attack.

340Not exploitable

60Exploitable

Day 1Last check

OverviewDaily checksEvidence

A rebuild removed the blocking setting on 38 servers. The agent flagged them the same day.

Use case ยท Zero-Day Agent + Exploitability Agent

Zero-day, no patch. Know what to fix today.

The Zero-Day Agent finds every asset the new CVE affects (how zero-day response works). The Exploitability Agent checks which of them the attack can actually work on. A company-wide emergency becomes a short list the same day.

The attack needs the ms-msdt handler on the machine. Where it's present, mitigate today. Where IT already removed it, the machine can safely wait for Microsoft's patch.

What are the possible exploitability verdicts?

Four answers. None of them a guess.

What "needs one check" looks like

It doesn't guess "safe."

When the agent can't see inside a device, it doesn't mark it safe. It asks your team one precise question, the one setting that decides the risk. One answer, and the finding is closed with proof.

How many of your criticals are actually exploitable?

Find out on your own infra. Book a 30-minute demo.

For audit and compliance

Every "not exploitable" is an exception your auditor needs.

When a critical stays open past its deadline, the auditor asks why. Today the answer is a spreadsheet note: "mitigated, per IT." Nobody rechecks it, and audit prep takes days.

Exception ยท CVE-2021-34527 ยท win-app-14Open 187 days ยท SLA 30
Decision
Not exploitable. Patch on the normal cycle.
Reason
Print Spooler disabled. The attack needs it running.
Evidence
HKLM\SYSTEM\CurrentControlSet\Services\Spooler ยท Start = 4 (disabled)
Last checked
Today, 06:12 ยท checked daily
If it changes
Reopens on its own

The promise of using a tool like Onit to automate a huge amount of manual work allows my team to focus on more important issues.

Chase Carpenter
CSO, Honeywell

Exploitability validation: questions CISOs ask

Straight answers. Anything else, ask us in the demo.

Do you run exploits on my production machines?

No. The agent only reads files, registry keys, configurations and other variables.

Do I have to install an agent?

No. The Exploitability Agent works through your current stack. Nothing new goes on your machines.

What if a config changes after the check?

The agent checks again. If the conditions come back, so does the finding.

How is this different from my scanner's risk score?

A score weighs the CVE against signals like exposure, running processes and asset tags. It doesn't read the configuration that decides whether the attack works. This answer comes from the machine itself, today, with the proof attached.

Will my auditor accept "not exploitable"?

Each one carries the reason, the evidence from the asset and the date it was last checked. If the setting changes, the finding reopens on its own.

What is the difference between vulnerable and exploitable?

Vulnerable means an affected version is installed. Exploitable means the conditions the attack needs are present on that machine. The agent checks the second and shows what it found.

Give IT a decision it can say yes to.

Every verdict comes with proof.

Get a Demo