Your Clients’ Vulnerability Reports Are Sorted by the Wrong Number

Person using a tablet
Blog

Your Clients’ Vulnerability Reports Are Sorted by the Wrong Number

Sooner or later, a security conversation with a mid-market client turns to the vulnerability report, usually sorted by severity with an alarming count at the top. Plenty of providers build their whole pitch on that count: here are your critical findings, and here’s what it costs to make them go away. 

That pitch got weaker in 2026, and most of your clients haven’t heard why. For Trusted Advisors, the change opens a better conversation about risk-based vulnerability management, which means deciding what to fix first by weighing what a weakness could do to the business, with the severity score as one input among several.

Most new vulnerabilities no longer come with a NIST score

On April 15, 2026, NIST changed how it runs the National Vulnerability Database (NVD), the public catalog many scanners and patch programs lean on for severity ratings. It now fully enriches only CVEs in CISA’s Known Exploited Vulnerabilities (KEV) catalog, CVEs in software the federal government uses, and CVEs in software designated critical under Executive Order 14028. Everything else still gets listed, without a NIST-issued severity score, product mapping, or classification. The Cloud Security Alliance estimates those three groups cover roughly 15 to 20 percent of expected CVE volume. 

Plenty of clients run their vulnerability program on a simple rule: patch everything above a CVSS threshold. That rule was already wasteful, since it treats a critical finding on a test box the same as one on the system that runs the business. Since April it has also had holes in it, because a growing share of new vulnerabilities won’t come with a NIST score to sort by. 

So when a client tells you “we have a scanner, we’re fine,” they may be leaning on an assumption that stopped holding this spring, and it’s likely nobody has explained the change to them.

What prioritizing by business risk looks like

Risk-based programs already look past CVSS. They check whether a vulnerability is in the CISA KEV catalog, which means attackers are exploiting it now, and how likely it is to be exploited according to its EPSS score. ECI’s GRC team also weighs the asset itself: whether it faces the internet or sits inside the network, what runs on it, who owns it, and whether it falls under a defined recovery time objective. 

Add that context and a moderate finding on a crown-jewel system can outrank a critical one on an isolated test box. The budget and engineering hours follow the new order, and the client ends up with a reason behind every priority that they can walk an auditor through.

The loudest finding on the scan was never fixed

One ECI engagement, with a healthcare software company, started with vulnerability counts that looked bad. The company ran Macs at scale with no central management platform to patch or configure them consistently. By raw severity that was the emergency, and it would have been an easy thing to sell against. 

The company’s product, though, was a cloud-hosted platform running in Azure, and its developers worked in a cloud environment too. People used the laptops to reach the work, while the work itself and the data that mattered lived in Azure. Once ECI accounted for the compensating controls already built into that setup, the Mac fleet’s real risk dropped considerably, and the cloud environment and the SaaS product’s scope moved to the top of the list. 

ECI spent the engagement reviewing that scope continuously and kept at it while the client went through a HITRUST audit, which they passed with zero findings. The Mac fleet, the loudest item on the scan, was never fixed. ECI documented why it was less dangerous than it looked and spent the effort elsewhere. A provider selling against the severity count would probably have scoped an endpoint management project.

What it takes, and what clients have to get comfortable with

The catch is inventory. Context-based scoring only works if someone keeps an accurate record of each system, what runs on it, who owns it, and what it connects to. Without that record, prioritization drifts back to sorting by severity score. Some clients will need inventory work first, and that’s worth raising in the first conversation so it doesn’t surprise anyone later. 

Some findings will also stay open on purpose, with compensating controls documented in place of a patch. Clients who measure security by a falling vulnerability count tend to find that uncomfortable until they see it survive an audit, which is where the HITRUST result helps. It ties back to a point ECI has made before about why passing an audit doesn’t mean a client is covered.

How to raise it with clients

You’ll probably hear some version of these. 

When you hear: “We already have a vulnerability scanner.” 
What to say: “Good. Now that NIST isn’t scoring most new CVEs, how are you deciding what to fix first?” 
When you hear: “We patch every critical within 30 days.” 
What to say: “Which of those criticals sit on the systems that hold your client data? A moderate finding on the system that runs your business can matter more than a critical on a test box.” 
When you hear: “Our numbers look bad. We need the count down before the audit.” 
What to say: “Getting the count down and passing the audit can be two different projects. ECI took a healthcare software company through HITRUST with zero findings without fixing the loudest item on its scan.”

Where ECI fits

ECI runs continuous vulnerability assessments with monthly reporting built for regulatory compliance, and its governance, risk, and compliance team works inside the frameworks your clients get audited against. ECI has spent nearly 30 years working with financial services, legal, healthcare, and other compliance-heavy firms. For you, that means a security conversation that goes past scan volume, plus a managed service that keeps going after the first engagement ends. 

Got a client heading into an audit, or one relying on a scanner and a CVSS threshold? Email channel@eci.com and the ECI channel team will help you plan the first call. If you’re new to working with ECI, here’s how the partner program works.

Frequently asked questions

What changed with the National Vulnerability Database in 2026?

Since April 15, 2026, NIST fully enriches only CVEs in the CISA KEV catalog, CVEs in software the federal government uses, and CVEs in software designated critical under Executive Order 14028. Other CVEs are still listed, but without a NIST-issued severity score, product mapping, or classification.

What is risk-based vulnerability management?

It’s a way of deciding what to fix first based on how likely a weakness is to be exploited and how much the affected system matters to the business. The severity score still counts, alongside exploitation data like the CISA KEV catalog and EPSS and the asset’s own context. 

Does risk-based prioritization mean leaving some vulnerabilities unpatched? 

Sometimes, yes. When a finding carries less risk than its score suggests, the compensating controls get documented and the effort goes where the exposure is. In the healthcare engagement above, that approach supported a HITRUST audit with zero findings. 

Which clients is this conversation a good fit for?

Clients in regulated industries who are heading into an audit, carrying a large severity backlog, or running a patch program built on a CVSS threshold.

How do I bring ECI into an opportunity?

Email the ECI channel team at channel@eci.com. They’ll help you plan the client conversation and work out where ECI’s Vulnerability Assessments and GRC services fit.

Microsoft 365 Copilot

Speak With One Of Our Experts Today

Learn How ECI Can Unlock Real Value For Your Firm.