Guide · Portfolio management

How to check a cyber book for CISA KEV exposure.

CISA’s Known Exploited Vulnerabilities catalog lists the flaws attackers are actually using. Checking every insured against it is one of the fastest ways to find the policyholders most likely to become a claim this quarter. Here is how to do it, and where the catalog leaves gaps.

What the KEV catalog is

A short list of vulnerabilities with proof of attack.

CISA adds a vulnerability to the catalog when it meets three criteria. Federal civilian agencies must remediate listed vulnerabilities within set deadlines under Binding Operational Directive 22-01, and CISA encourages every other organization to prioritize them too.

It has a CVE ID

The vulnerability has been assigned a Common Vulnerabilities and Exposures identifier.

It is exploited in the wild

There is reliable evidence of active exploitation, not just a theoretical risk.

It has a clear fix

A clear remediation action exists, such as a vendor-provided update.

Source: CISA, Reducing the Significant Risk of Known Exploited Vulnerabilities.

Step by step

Checking a book, insured by insured.

The same process works for a carrier, an MGA or a reinsurer reviewing a portfolio.

  1. List the insureds and their domains. The domain is the starting point for finding each organization’s internet-facing systems.
  2. Discover what each insured exposes. Identify internet-facing hosts and the software and versions they run.
  3. Match that technology to the catalog. Flag every host running a product and version listed on the KEV catalog.
  4. Confirm what is really exploitable. Version matching alone over-reports, because patches and mitigations don’t always change the version string. Non-destructive testing confirms which findings are real.
  5. Check exposed services separately. Remote access and data services reachable from the internet are a risk even with no listed vulnerability.
  6. Prioritize, contact and rescan. Start with confirmed exploitable findings, alert those insureds, and rescan to confirm each fix.

Where the catalog leaves gaps

Attackers don’t wait for the catalog.

A vulnerability can be exploited in the wild for some time before CISA analyzes it and adds it to the catalog. A book check that relies on the KEV catalog alone misses that window. Covering it means watching for newly exploited vulnerabilities and matching them to the technology each insured runs, before the listing arrives.

How CyRisk does it

RED and ZED, across the whole book.

CyRisk Portfolio Management runs this process across every policyholder at once, with no credentials, no notifications and no policyholder lift.

RED · Ransomware Exposure Detection

Finds KEV-listed vulnerabilities and risky exposed services, and a human analyst tests each exploit non-destructively to confirm it works.

ZED · Zero-day Exposure Detection

Flags exploited vulnerabilities that are not on the catalog yet and matches them to the technology each insured runs.

Results for the book

Insureds with confirmed exploitable flaws rise to the top. Rescan to confirm what was fixed.

Questions underwriters ask

Frequently asked questions.

What is the CISA KEV catalog?

It is CISA’s list of vulnerabilities with a CVE ID, reliable evidence of active exploitation in the wild, and a clear remediation action. Federal civilian agencies must fix listed vulnerabilities under Binding Operational Directive 22-01.

Why should insurers check a book against the KEV catalog?

Listed vulnerabilities are being used by attackers, so an insured exposed to one carries a more urgent risk than an insured with only theoretical vulnerabilities.

Is checking against the KEV catalog enough?

No. Exposed remote access and data services are a risk even without a listed vulnerability, and newly exploited vulnerabilities can be used for some time before they reach the catalog.

Do insureds need to take part in a book-wide check?

Not with an outside-in approach. CyRisk needs only a list of policyholders, with nothing to install and nobody to notify.

What is the difference between a version match and a confirmed finding?

A version match means a host appears to run an affected version. A confirmed finding means testing showed the vulnerability actually works on that host, which removes many false alarms.

Run RED on a sample of your book.

See which insureds carry exploitable exposure today, or book a walkthrough with our team.