Remediation Within Target
Wisec gives your organisation one graded figure about how you handle vulnerabilities over time:
What share of your critical and high findings were fixed within the deadlines you set?
It appears on the Exposure page and in your NIS2 and ISO 27001 compliance reports. Its definition is published here in full, because a figure you hand to an auditor must be one you can explain without us in the room.
This is version 2 (November 2026), and it is still provisional: the rule will be reviewed once enough history exists across organisations. Every figure carries its version, and figures from different versions do not compare. Version 2 counts a vulnerability reported by several tools once (step 1); version 1 counted it once per tool.
What it measures, and what it does not
It measures a process: how fast your team deals with what the scanners find. That is what NIS2 (article 21(2)(e), vulnerability handling) and ISO 27001 (control A.8.8, management of technical vulnerabilities) ask an auditor to assess.
It does not measure how many findings you have. That is the job of the security score, which grades each build, and of the counts on the Exposure page. Adding a scanner adds findings; it does not lower this figure, as long as what it finds is handled in time.
It never appears on a build certificate. A certificate states facts about one build; this figure describes a period.
The rule, in four steps
1. Which findings count
- Critical and high findings only: the two severities that carry a deadline. Medium and low findings stay visible on the Exposure page and are not part of the figure.
- On your release branches only:
mainandmasterby default, adjustable per project by an administrator on the Projects page ("Release branches"). A finding introduced on a feature branch and abandoned with it was never late. Every change of this setting is written to your audit log. - On projects that declared a scanner: a project whose latest release build declared no tool is listed as "not counted". A rate computed on no search would be worth nothing.
- One vulnerability is one finding, whatever the number of tools that report it. When Wisec's dependency scan and Trivy both report
CVE-2022-23307on the same project and branch, it counts once: at the highest severity either tool gave it (hence the shortest deadline), first seen when the earliest saw it, and fixed only once no tool reports it any more. A code or configuration rule is not merged: each file it fires in is a place to fix.
The projects counted, and the reason each other project is not, are always shown next to the figure.
2. Every finding gets a deadline
deadline = the day the finding was first seen + your target for its severity
The targets are yours: 7 days for critical and 30 days for high by default, set by an administrator in Settings ("Remediation targets"). Each change is written to the audit log with the previous values. The targets are printed next to every figure.
A finding that comes back after being fixed keeps its original first-seen date: its clock does not restart.
3. On time, late, or not due yet
| The finding is... | It counts as | When |
|---|---|---|
| Fixed on or before its deadline | On time | On the day it was fixed |
| Fixed after its deadline | Late | While it was late |
| Still open past its deadline | Late | Until it is fixed, however old it gets |
| No longer reported because its scanner stopped running | Late | It was never confirmed fixed |
| Open, deadline still ahead | Not due yet | Not counted, shown apart |
Fixed means the scanner that reported the finding ran again on a later build and no longer reports it. A finding that disappears because a scanner was removed from the pipeline is not a fix, and is never counted as one.
4. The figure
figure = on time / (on time + late), over the last 90 days, rounded down
Rounded down: 199 on time out of 200 reads 99%, so 100% means every single deadline was met.
Next to it you always see: the rate for critical and for high separately with their counts, the findings late right now, the findings not due yet with the date of the next deadline, the accepted risks, and the findings dismissed as false positives.
The decisions you take on findings
| Your decision | Effect on the figure |
|---|---|
| Accepted risk / won't fix (or OpenVEX "affected") | Set aside until its review date, and shown as "accepted risks". Once the review date has passed, the finding counts again, and since its deadline is long gone, it counts as late. A decision with no review date counts as expired. |
| False positive (or OpenVEX "not affected") | Set aside, and counted as "false positives" next to the figure, never hidden. Every such decision is in your audit log. |
| Fixed, while a scanner still reports it | No effect: the finding stays open, and the contradiction is recorded. |
A decision only matters while the finding is open. A finding that was fixed counts as fixed, whatever was decided about it before.
Accepted risks get a review date when you accept them (90 days by default, adjustable). Accepting a risk is a legitimate answer; never looking at it again is not.
When there is no figure
You will see "No figure yet" rather than a number:
- while your history is shorter than two weeks, or fewer than three findings have been resolved;
- when fewer than three critical or high findings reached their deadline or were fixed in the last 90 days.
In that case Wisec shows how many findings are being tracked and when the first deadline falls. A figure of 100% because nothing had to be fixed would say something false about your process.
What it is designed to resist
| Manoeuvre | Why it does not improve the figure |
|---|---|
| Removing a scanner from the pipeline | Its findings become "no longer observed", which counts as late, never as fixed |
| Declaring everything a false positive | The number dismissed is shown next to the figure, and each decision is in the audit log |
| Accepting every risk | Accepted risks are set aside only until their review date, then count as late |
| Setting a 365-day target | The targets are printed with every figure, and every change is audit-logged with the previous value |
| Leaving a bad project out of the scope | The scope is printed with every figure, and "all projects" is the default |
| Running no scanner at all | No findings means no figure, and the project is listed as not counted |
| Adding a second scanner that reports the same vulnerabilities | A vulnerability counts once, at the highest severity a tool gave it |
| Loosening a target to make past months read better | Each month is frozen in a signed record when it closes, so a later change cannot rewrite it |
Signed monthly records
The figure on screen is always recomputed with your current targets and scope. A signed monthly record freezes it as it stood when each month closed, so the figure of a given month stays opposable whatever changes afterwards.
How a record is taken
- During the first three days of each month (UTC), Wisec computes the figure for your organisation over the 90 days to that moment, and records it as the month just closed. The record carries the exact time it was computed.
- It covers all your projects (their release branches), with the same rules as above, and is taken even when there is no figure: "no figure yet, and why" is a fact worth recording too.
- The record holds the figure, the counts behind it, your targets, the scope (projects, release branches, counted or not) and the posture version. It holds no personal data, but it does name your projects and branches.
- It is signed with the Wisec attestation key, anchored on IPFS with a copy in write-once storage, and logged in the public Rekor transparency log, like the other Wisec evidence. Nothing is stored unless it was signed and anchored.
Three rules
- A missed month stays missed. The figure reads the current state of each finding, which cannot be rewound, so a month whose record was not taken in its first three days is shown as "Not recorded" and is never rebuilt afterwards.
- No record on demand. Records are only taken at the start of the month, so nobody can choose the day that looks best.
- A record is never rewritten. Changing a target or a release branch changes the figure on screen, not the months already recorded.
Where they appear
- The Exposure page, under the figure, with a link to each signed statement and its Rekor entry.
- NIS2 and ISO 27001 compliance reports (dashboard and PDF): the records of the months that overlap the report period. They are the posture of that period, while the figure at the top of the section is computed on the generation date.
A third party can check, without a Wisec account and with standard tools, that a statement is intact, that it was signed with the Wisec key, and when it was logged in Rekor. Its content remains a statement made by Wisec from your recorded history.
Signed monthly records are available on the Business and Pro plans. The first records cover November 2026.
Where it appears
- The Exposure page of the dashboard, with a scope selector, followed by the signed monthly records.
- NIS2 and ISO 27001 compliance reports (dashboard and PDF), with the same scope as the report. It is computed on the date the report is generated, over the 90 days before it, and not over the period selected for the report: it reads the current state of each finding, which cannot be rewound to a past date. The report says so, and the figure changes the status of no requirement.
The figure itself is available on the Business and Pro plans. On the Free plan, the Exposure page shows whether the figure is still establishing.
Known limits
- The figure on screen uses your current targets. Changing a target today changes how the past reads on screen. The audit log keeps every change with its previous value, and the signed monthly records keep each month as it stood. Months before the first record have no such record.
- Critical and high weigh the same in this version. Whether critical findings should weigh more will be decided on real history, as a new version.
- Only critical and high findings carry a deadline.