Your vulnerability management, as one defensible figure.

What share of your critical and high vulnerabilities was fixed within the deadlines you set?

That is what NIS2 and ISO 27001 ask an auditor to assess: your process, not your number of vulnerabilities. Wisec measures it over 90 days, and its full definition is public.

NIS2 art. 21(2)(e)ISO 27001 A.8.8Version 2, provisional
1 · A deadline

Every vulnerability gets a deadline.

The day it was first detected, plus your target: 7 days for a critical, 30 for a high by default. The targets are yours, and every change is written to the audit log with the previous value.

deadline = first detection + target for its severity
2 · 90 days

Met, or missed.

Each line is a vulnerability, from detection to fix. A fix counts only if the scanner that reported it ran again and no longer sees it: removing a scanner fixes nothing.

Fixed within targetLateDeadline
3 · The figure

A rate, rounded down.

Illustrative example
83 %20 within target out of 24 due

100% means every deadline was met. Next to the figure, always: your targets, the scope, the accepted risks and the dismissed false positives.

4 · The record

Frozen every month, signed.

The figure on screen follows your current settings. The monthly record freezes it when the month closes: signed, anchored on IPFS and logged in Rekor. Loosening a target later does not rewrite the past. First records: November 2026.

The rule

Four steps, published in full.

A figure handed to an auditor must be explainable without us. Every figure carries its version, and two versions do not compare.

1 · What counts

Critical and high, on your release branches.

Only projects that declare a scanner. A vulnerability reported by two tools counts once, at the highest severity.

2 · The deadline

Your targets, not ours.

7 and 30 days by default. A vulnerability that comes back keeps its original detection date.

3 · The status

Within target, late, or not yet due.

A vulnerability that disappears because its scanner stopped running counts as late.

4 · The figure

Within target, divided by everything that was due.

Over 90 days, rounded down. No figure before two weeks of history and three resolved findings.

What it resists

A figure that cannot be inflated.

Every move that would lift a naive indicator has an answer in the rule.

MoveWhy it does not work
Remove a scanner from the pipelineIts findings are no longer observed, which counts as late, never as fixed.
Declare everything a false positiveThe number of dismissed findings is shown next to the figure, and every decision is in the audit log.
Accept every riskAn accepted risk is set aside only until its review date, then it counts as late.
Set a 365-day targetTargets are printed with every figure, and every change is audited with the previous value.
Add a second scannerA vulnerability counts once, whatever the number of tools that report it.
Rewrite past monthsEach month is frozen in a signed record when it closes.
Where it appears

Where the auditor will look for it.

The Exposure page

The figure and its scope, vulnerabilities by severity, the scanner inventory of each project.

NIS2 and ISO 27001 reports

In the dashboard and as PDF, with the records of the months the report covers.

The monthly records

One signed statement per month, verifiable without a Wisec account, with standard tools.

Available on the Business and Pro plans. On the Free plan, the Exposure page shows whether the figure is still being established. The figure never appears on a build certificate: a certificate states facts, this figure describes a period.