In a mid-sized organization, a vulnerability scanner typically returns thousands of findings, hundreds of them rated “critical” or “high.” Nobody can work through that many, and the usual result is that nobody pays attention to the list anymore.
More resources will not fix this; better prioritization will. This article shows how to pick, out of thousands of findings, the few dozen that really matter.
Why CVSS is not enough
The CVSS score measures the theoretical severity of a vulnerability under laboratory conditions. What it does not tell you:
- whether it is actually being exploited in the wild,
- whether an attacker can reach the system at all,
- what the system is worth to the business,
- whether compensating controls surround it.
That is why a CVSS 9.8 flaw on an isolated test system that cannot be reached from the internet is less urgent than a CVSS 6.5 flaw in a public web application under active attack.
Three data sources that bring order
1. KEV: what is actually being exploited
The CISA Known Exploited Vulnerabilities catalog lists the vulnerabilities with confirmed active exploitation. That is a few thousand entries out of hundreds of thousands of CVEs.
If a finding is in KEV, it is an immediate priority, whatever its CVSS score. This one filter alone cuts most organizations’ lists to a manageable size right away.
2. EPSS: the probability of exploitation
The Exploit Prediction Scoring System estimates how likely it is that a given vulnerability will be exploited in the next 30 days. The score ranges from 0 to 1.
In practice, the vast majority of CVEs have an EPSS score below 0.01, which means they are practically never exploited. High CVSS paired with low EPSS is the most common combination, and it is what floods the list.
3. Your own context
No external database can supply this:
- Reachability: is it reachable from the internet, from the internal network, or only from an isolated segment?
- Business criticality: what happens if this system goes down or is compromised?
- Data: does it handle personal or commercially sensitive data?
- Compensating controls: is there a WAF, IPS, or segmentation in front of it that prevents exploitation?
Prioritization order in practice
| Priority | Condition | Deadline |
|---|---|---|
| P1 | In KEV and reachable by an attacker | 24-72 hours |
| P2 | High EPSS (>0.1) and reachable from the internet | 7 days |
| P3 | Critical CVSS, internal system, important to the business | 30 days |
| P4 | Everything else | Next maintenance window |
| P5 | Low EPSS, isolated, compensated | Documented acceptance |
The P5 category matters because not every vulnerability has to be fixed. Documented risk acceptance is a legitimate answer if someone makes the decision and signs it. Quietly ignoring a finding is not a legitimate answer.
OT environments are different
In industrial environments, patching is often not an option. Vendor support has ended, an update would void the certification, or the downtime window comes once a year.
You can still act, just in a different order:
1. Know your assets. Passive discovery and an exact record of firmware versions. Without these, there is no vulnerability matching.
2. Filter by reachability. A vulnerable PLC in a well-segmented zone that can only be reached from the engineering workstation is a much smaller risk than the same PLC on a flat network.
3. Apply compensating controls. A network-level virtual patch (an industrial IPS that blocks traffic targeting the specific vulnerability) is often the only realistic answer. It does not fix the flaw, but it prevents its exploitation.
4. Plan for the downtime window. Have the list of items that really need patching ready when the window comes, because you will have hours, not days.
5. Document. The fifth NIS2 measure and IEC 62443-2-3 both ask you to show a process, not zero vulnerabilities.
Elements of a working process
Discovery. Continuous, automated scanning across the full asset inventory. Active in IT, passive in OT.
Prioritization. Following the order above, automated where possible. The goal is a list of ten items in front of the team, not two thousand.
Ownership. Every item needs an owner. Saying “IT will take care of it” does not assign one.
Deadlines and tracking. A fixed deadline for each priority level, and measurement of whether it is met.
Verification. A rescan after the fix. Surprisingly often it turns out that the patch was installed but the service was never restarted, so the old version is still running.
Exception handling. Written, time-limited, reviewed risk acceptance for the items that will not be fixed.
What to measure
Three metrics are enough:
- Mean time to remediate (MTTR) for each priority level. This shows whether the process works.
- Number of open KEV-listed items. This should trend toward zero.
- Coverage: what percentage of the asset inventory is scanned at all.
The third one usually brings the biggest surprise. In many organizations, scanning is limited to servers, while workstations, network devices, and edge devices are left out. Those are exactly the devices attackers use to get in.
If you want to find out where you stand, our IT security assessment also reviews the state of your updates, and patch and update management handles fixes on a schedule. On the OT side, the OT security assessment goes into full depth and also analyzes legacy systems that cannot be updated. We covered the IT security assessment and the IEC 62443 framework in separate articles.