You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<pclass="admonition-title"><abbrtitle="Cybersecurity & Infrastructure Security Agency">CISA</abbr><abbrtitle="Known Exploited Vulnerability">KEV</abbr> currently includes ~1.1K CVEs, and defines criteria for inclusion</p>
1289
+
<p><abbrtitle="Cybersecurity & Infrastructure Security Agency">CISA</abbr> Known Exploited Vulnerabilities Catalog (<abbrtitle="Cybersecurity & Infrastructure Security Agency">CISA</abbr><abbrtitle="Known Exploited Vulnerability">KEV</abbr>) is a source of vulnerabilities that have been exploited in the wild</p>
1290
+
<p>There's several criteria including:</p>
1291
+
<divclass="admonition quote">
1292
+
<pclass="admonition-title">Quote</p>
1293
+
<p>"A vulnerability under active exploitation is one for which there is reliable evidence that execution of malicious code was performed by an actor on a system without permission of the system owner." </p>
1294
+
<p>"Events that do not constitute as active exploitation, in relation to the <abbrtitle="Known Exploited Vulnerability">KEV</abbr> catalog, include:</p>
<p>“All federal civilian executive branch (FCEB) agencies are required to <abbrtitle="The neutralization or elimination of a vulnerability or the likelihood of its exploitation.">remediate</abbr> vulnerabilities in the <abbrtitle="Known Exploited Vulnerability">KEV</abbr> catalog within prescribed timeframes under Binding Operational Directive (BOD) 22-01, Reducing the Significant <abbrtitle="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> of Known Exploited Vulnerabilities. Although not bound by BOD 22-01, every organization, including those in state, local, tribal, and territorial (SLTT) governments and <strong>private industry can significantly strengthen their security and resilience posture by prioritizing the remediation of the vulnerabilities listed in the <abbrtitle="Known Exploited Vulnerability">KEV</abbr> catalogue as well</strong>. <abbrtitle="Cybersecurity & Infrastructure Security Agency">CISA</abbr> strongly recommends all stakeholders include a requirement to immediately address <abbrtitle="Known Exploited Vulnerability">KEV</abbr> catalogue vulnerabilities as part of their vulnerability management plan.</p>
<pclass="admonition-title"><abbrtitle="Cybersecurity & Infrastructure Security Agency">CISA</abbr><abbrtitle="Known Exploited Vulnerability">KEV</abbr> currently includes ~1.1K CVEs, and defines criteria for inclusion</p>
3847
+
<p><abbrtitle="Cybersecurity & Infrastructure Security Agency">CISA</abbr> Known Exploited Vulnerabilities Catalog (<abbrtitle="Cybersecurity & Infrastructure Security Agency">CISA</abbr><abbrtitle="Known Exploited Vulnerability">KEV</abbr>) is a source of vulnerabilities that have been exploited in the wild</p>
3848
+
<p>There's several criteria including:</p>
3849
+
<divclass="admonition quote">
3850
+
<pclass="admonition-title">Quote</p>
3851
+
<p>"A vulnerability under active exploitation is one for which there is reliable evidence that execution of malicious code was performed by an actor on a system without permission of the system owner." </p>
3852
+
<p>"Events that do not constitute as active exploitation, in relation to the <abbrtitle="Known Exploited Vulnerability">KEV</abbr> catalog, include:</p>
<p>“All federal civilian executive branch (FCEB) agencies are required to <abbrtitle="The neutralization or elimination of a vulnerability or the likelihood of its exploitation.">remediate</abbr> vulnerabilities in the <abbrtitle="Known Exploited Vulnerability">KEV</abbr> catalog within prescribed timeframes under Binding Operational Directive (BOD) 22-01, Reducing the Significant <abbrtitle="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> of Known Exploited Vulnerabilities. Although not bound by BOD 22-01, every organization, including those in state, local, tribal, and territorial (SLTT) governments and <strong>private industry can significantly strengthen their security and resilience posture by prioritizing the remediation of the vulnerabilities listed in the <abbrtitle="Known Exploited Vulnerability">KEV</abbr> catalogue as well</strong>. <abbrtitle="Cybersecurity & Infrastructure Security Agency">CISA</abbr> strongly recommends all stakeholders include a requirement to immediately address <abbrtitle="Known Exploited Vulnerability">KEV</abbr> catalogue vulnerabilities as part of their vulnerability management plan.</p>
0 commit comments