Minimize Cybersecurity Risk with the Known Exploited Vulnerabilities Catalog
Secured™ recommends the CISA Known Exploited Vulnerabilities (KEV) Catalog as a source to prioritize vulnerability management. In November 2021 the Cybersecurity and Infrastructure Security Agency (CISA) started the Known Exploited Vulnerabilities (KEV) Catalog and Binding Operational Directive 22-01. The KEV catalog lists only vulnerabilities known to be actively exploited. The BOD 22-01 requires all federal civilian executive branch (FCEB) agencies to remediate all vulnerabilities in the KEV catalog. This helps organizations focus on vulnerabilities to patch. Secured encourages all enterprises to implement the CISA KEV Catalog in their vulnerability management practice.
The National Vulnerability Database (NVD) is a U.S. government repository of standards-based vulnerability management data and best known for providing this CVE database. Last year over 20,000 vulnerabilities were assigned Common Vulnerabilities and Exposures (CVE) identifiers.
The KEV catalog helps prioritize vulnerability management. At the time of writing, the CISA KEV Catalog lists only 857 CVEs.
From November 1-15, 2022 over 1,190 CVEs were published, but CISA only added 8 CVEs to the KEV Catalog:
These three Samsung vulnerabilities were published in March 2021, but are now designated to be higher priority vulnerabilities to remediate. The KEV Catalog helps pinpoint older CVEs that now have clearly demonstrated risk of exploitation and verified remediation solutions.
CISA’s KEV Catalog Three Criteria
CISA uses three criteria for submitting a vulnerability into the KEV Catalog.
From the CISA website:
These three criteria show that CISA emphasizes vulnerabilities that have both evidence of real-time attacks and a clear solution to prevent exploitation, either through mitigation or workaround solutions. The directive, BOD 22-01, requires all federal civilian executive branch (FCEB) agencies remediate all vulnerabilities in the KEV Catalog. Each KEV Catalog submission has a due date to remediate the vulnerability, typically two to three weeks from its submission.
Actively following new submissions to the KEV Catalog helps your organization stay apprised of key vulnerabilities and remediation solutions. Secured™ recommends all organizations complete remediation solutions by the KEV Catalog due dates. Twitter users can easily become inundated with hourly updates from @CVEnew. For Twitter users, Secured™ recommends the Twitter accounts @CISAgov and @USCERT_gov for more curated KEV Catalog updates. Secured™ also recommends subscribing to CISA’s KEV Catalog Update Bulletin, which provides email updates of new KEV Catalog submissions. Secured™ actively monitors the KEV catalog and provides organizations with security assessments that check for a wide range of vulnerabilities.