Skip to main content
Promotional banner for a CUI buildout guide
KEV Is a Floor, Not a Vulnerability Management StrategyPrivacy and Security
4 min readFor GRC Leaders

KEV Is a Floor, Not a Vulnerability Management Strategy

The Conventional Wisdom

The advice is simple: if a CVE is in CISA's Known Exploited Vulnerabilities (KEV) Catalog, patch it first. CISA reinforces this with Binding Operational Directive (BOD) 26-04, directing Federal Civilian Executive Branch (FCEB) agencies to prioritize rapid remediation of KEV-listed vulnerabilities on publicly exposed assets that grant total control post-exploitation. Lower-risk items can wait. CISA also encourages all organizations, not just federal ones, to adopt risk-based vulnerability management and prioritize KEV remediation.

Many GRC teams use KEV as a shortcut. It becomes the Cybersecurity Risk Register's patching trigger, audit evidence, and board talking point. If your Key Control Indicator is "percentage of KEV items remediated within the target window," you're not alone.

Why It's Incomplete

KEV answers one question: has this been exploited in the wild? It doesn't address what exploitation would do to your organization.

BOD 26-04 doesn't say "patch every KEV entry." It targets KEV-listed CVEs on publicly exposed assets that grant total control after exploitation, deferring action on lower-risk vulnerabilities. This model involves three variables: confirmed exploitation, exposure, and impact. The catalog provides only the first. Your team must determine the other two.

This is where the shortcut fails. A KEV entry on an internal system with no external exposure and compensating controls isn't the same risk as the same CVE on an internet-facing gateway. Treating them the same wastes remediation resources. Worse, a vulnerability not in KEV but on your most exposed, high-impact asset might never reach the top of your queue because you've outsourced your triage logic to a list.

Also, KEV status is binary and lagging. A CVE enters the catalog after evidence of exploitation and clear mitigation guidance. That's useful, but it means KEV tells you where attackers have been, not where they're heading.

The Evidence

The most recent catalog addition illustrates the point. CISA added CVE-2026-19868, a SonicWall SonicOS SSLVPN vulnerability involving single-factor authentication, noting it's a frequent attack vector for malicious actors.

This isn't an exotic exploit chain. It's single-factor authentication on a remote access gateway, a weakness class, not just a product defect. A team that only reads the CVE number asks, "Do we run SonicOS SSLVPN, and have we patched?" A team doing real risk-based work asks broader questions:

  • Where else do we expose remote access with single-factor authentication, regardless of vendor?
  • Is multi-factor authentication enforced as a Compliance Control across all externally reachable authentication paths, and is that control tested?
  • If the gateway were compromised, what does the attacker reach next?

CISA's directive points the same way. BOD 26-04 establishes basic expectations for checking whether threat actors compromised a system before patching. Patching closes the door; it doesn't tell you if someone already walked through it. A KEV-driven program that measures only patch completion lacks evidence for this obligation.

What to Do Instead

Use KEV as a mandatory input to prioritization, then add your own context. A workable structure for GRC leaders:

1. Define Decision Criteria in Policy, Not in a Spreadsheet. Write a Policy Standard that states how exploitation evidence, asset exposure, and post-exploitation impact set remediation timelines. Mirror BOD 26-04 logic (exploited, publicly exposed, total control) and add factors specific to you, such as data sensitivity and business criticality.

2. Tie the Policy to Cyber Risk Appetite. Remediation windows should trace back to a stated appetite. If leadership has accepted a given level of exposure, the timelines should reflect it. If your appetite is low for internet-facing authentication weaknesses, the policy should say so explicitly.

3. Govern Deferrals Through Approved Exceptions. Deferring lower-risk items is legitimate, and BOD 26-04 contemplates it. But every deferral needs an owner, a rationale, compensating controls, and an expiry date. Deferral without documentation is just unmanaged risk.

4. Add a Compromise-Assessment Step. For KEV items on exposed assets, require a documented check for prior compromise before closing the item. Capture the evidence in your GRC Platform so Audit Fieldwork can test it later.

5. Track More Than Patch Speed. Pair remediation time with Key Control Indicators for exposure reduction, such as the count of externally reachable assets lacking multi-factor authentication. Automated Risk Scoring can help, provided the scoring inputs include exposure and impact, not just a KEV flag.

6. Feed Your Information Security Event Triage. When a new KEV entry lands, your team should quickly determine if you're affected and if there's any indication of exploitation. That's an Incident Response Structure question as much as a vulnerability one.

When the Conventional Wisdom Is Right

For many organizations, the KEV-first rule is the right default. If your team is overwhelmed with open findings scored by severity alone, KEV is a better starting filter than raw CVSS ranking. It's grounded in evidence of real exploitation, it's free, and it's maintained by a credible authority. Starting there beats starting with nothing.

It's also the correct approach when you lack the asset visibility to run a fuller model. If you can't reliably say which systems are publicly exposed, you can't apply the exposure variable, and "patch KEV items first" is a sound interim control. And if you're an FCEB agency, it isn't optional; BOD 26-04 applies to you.

The argument here isn't that KEV is overrated. It's that KEV is a floor. Meeting it shows you responded to known attacker behavior. It doesn't show you understand your own exposure. Your auditors, regulators, and board will eventually ask the harder question: not "did you patch what CISA listed," but "how did you decide what mattered here?" Make sure you have a documented answer.

Cybersecurity and Infrastructure Security Agency

Promotional banner graphic asking if you are ready for PCI DSS 4.0 with a call-to-action to get the guide

You Might Also Like