Vulnerability Management

Run vulnerability management as a program you can measure

Alvor turns scanner findings into fixes with a named owner and a deadline set by your own policy. A fix closes only when a rescan proves it, and the report shows whether your fixes land on time.

Findings from

Rapid7 InsightVM · Qualys · Tenable Vulnerability Management · Tenable Security Center · CrowdStrike Spotlight · Microsoft Defender Vulnerability Management · Greenbone · Wiz · GitHub · GitLab · Veracode · Snyk · SonarQube · Checkmarx One · AWS · pentest spreadsheetsfixes in Jira Cloud

Scanners find more every year. Programs fall behind on the fixing.

Finding vulnerabilities is the solved half. The unsolved half is getting the few that matter fixed on time, by the right person, and being able to prove it.

100,222

CVEs published in 2026 by 13 November, more than double 2025's total.

VulnCheck count, via The Register

1.4%

of them are in VulnCheck's catalogue of known exploited vulnerabilities. The rest compete for the same hours.

VulnCheck, via The Register

26%

of the known exploited vulnerabilities organisations detected were fully remediated.

Verizon 2026 DBIR, via Tenable

Half

of organisations close a vulnerability only after a rescan verifies the fix.

Vicarius survey of 300 leaders, via Help Net Security

Program reporting

Report on deadlines met, not vulnerabilities counted

The remediation timeline report measures every closed fix against the deadline it had. Break it down by owner, business service or priority. Every missed deadline is listed with the rule that set it, and every finding closed without a fix shows who approved it.

Measured against the deadline each fix had

On time is judged against the deadline each fix had, and a change to your timeline rules shows as a marker on the weekly chart.

Late fixes explained by the rule behind them

A missed deadline names the rule that set it. The conversation moves from who was slow to whether the rule fits the team.

Nothing closes quietly

Closed without a fix is its own figure, split by risk accepted, not a real issue and findings suppressed inside a scanner.

Fix what attackers use first, by deadlines your policy sets

Severity is one input. Each fix is also ranked by whether attackers are exploiting it, how likely exploitation is, whether the asset faces the internet, the data it holds and the business service that depends on it. Deadlines come from timeline rules you write, and the shortest matching rule wins.

  • Every reason shows where it came from, so a priority can be checked, not just trusted
  • A new signal only shortens a deadline; a longer one needs an approved decision
  • Rules are versioned, and the backlog you inherit gets a one-time starting baseline

Every fix reaches its owner, and closes only when a rescan proves it

The owner comes from the asset register, so nobody spends Monday deciding who gets what. Findings that one upgrade clears become one fix. “Mark as fixed” is a claim: the fix closes when every scanner that found it rescans and no longer sees it, and a Jira status never closes a finding.

  1. Assigned
  2. Acknowledged
  3. Fixing
  4. Fix claimed
  5. Verified

These are the exact links in the data model.

Named precisely, because “everything connects to everything” is not a claim anyone can check. Select any module to see its links.

01Set the program
02Design new systems
03Prove controls work
04Manage risk, vulnerabilities, vendors and continuity
RegisterThe register the rest stands on
Runs onYour own instance
Dedicated cloudOne instance for your company, in your region
On-premiseThe same platform, on your own servers
Air-gappedFully disconnected, with a self-hosted model

Links the product makes today

Vulnerability Management links to

Asset ManagementEvery finding sits on an asset in the register. The asset's technical owner owns the fix, its business owner is accountable, and its criticality, exposure, data classification and the business services that depend on it set the priority.

Every exception has an approver, a reason and an end date

When a fix has to wait, the owner asks for a decision instead of letting the deadline slide. A vulnerability analyst who is not the requester decides. If the threat changes, an accepted risk is suspended and a mitigation goes back for review.

Accept the risk

Ends by priority, never open-ended. A reminder starts seven days before it expires.

Mitigate with another control

Sets a fix-by date that becomes the new deadline, with a review within 180 days.

Not a real issue

Rechecked after 180 days, and disputed automatically if another scanner still sees the finding.

Questions

Common questions about vulnerability management in Alvor

Risk-based vulnerability management ranks vulnerabilities by the harm they can do to your organisation, not by severity score alone. It weighs whether attackers are exploiting a flaw (the CISA Known Exploited Vulnerabilities catalogue), how likely exploitation is (EPSS), whether the asset faces the internet, the data it holds and the business services that depend on it. The point is to spend limited fixing hours on the small share of vulnerabilities that get exploited, and to set deadlines that match that risk.

Vulnerability Management

See your on-time rate on your own scanner data

Vulnerability Management is included in every Alvor plan, beside the other eight modules, on a dedicated instance in your region, on your own servers or air-gapped.