Deployed 7742c72 with MkDocs version: 1.5.3

Author: Crashedmind

impact/impact/index.html

@@ -2065,7 +2065,8 @@ <h2 id="impact-text-and-mitre-technical-impact-extraction-from-a-cve">Impact Tex
 <p class="admonition-title">Takeaways</p>
 <ul>
 <li>The Technical impact is useful for end users (beyond the <abbr title="Common Vulnerability Scoring System Standard. A framework for scoring the severity of vulnerabilities based on factors such as exploitability and impact.">CVSS</abbr> Confidentiality, Integrity, Availability impact) which is not so useful as it is not granular.</li>
-<li>Technical impact is not represented in CVEs today, even though there is an "impacts" field in the <abbr title="CVE Common Vulnerability and Exposures. A standardized list of publicly known vulnerabilities and exposures maintained by the MITRE Corporation.">CVE</abbr> schema.</li>
+<li>Technical impact is not well represented in published CVEs today, even though there is an "impacts" field in the <abbr title="CVE Common Vulnerability and Exposures. A standardized list of publicly known vulnerabilities and exposures maintained by the MITRE Corporation.">CVE</abbr> schema.</li>
+<li>People may want to know the Impact more than the CAPEC (where CAPEC lives under Impact in the schema - and is often used as the only representation of Impact in a <abbr title="CVE Common Vulnerability and Exposures. A standardized list of publicly known vulnerabilities and exposures maintained by the MITRE Corporation.">CVE</abbr>, if at all)</li>
 <li>The <abbr title="CVE Common Vulnerability and Exposures. A standardized list of publicly known vulnerabilities and exposures maintained by the MITRE Corporation.">CVE</abbr> Description (and reference content) impact keyphrases, and the MITRE Technical Impacts that they map to, could be placed in the <abbr title="CVE Common Vulnerability and Exposures. A standardized list of publicly known vulnerabilities and exposures maintained by the MITRE Corporation.">CVE</abbr> schema impacts field.</li>
 </ul>
 </div>

print_page/index.html

@@ -6240,7 +6240,8 @@ <h2 id="impact-impact-impact-text-and-mitre-technical-impact-extraction-from-a-c
 <p class="admonition-title">Takeaways</p>
 <ul>
 <li>The Technical impact is useful for end users (beyond the <abbr title="Common Vulnerability Scoring System Standard. A framework for scoring the severity of vulnerabilities based on factors such as exploitability and impact.">CVSS</abbr> Confidentiality, Integrity, Availability impact) which is not so useful as it is not granular.</li>
-<li>Technical impact is not represented in CVEs today, even though there is an "impacts" field in the <abbr title="CVE Common Vulnerability and Exposures. A standardized list of publicly known vulnerabilities and exposures maintained by the MITRE Corporation.">CVE</abbr> schema.</li>
+<li>Technical impact is not well represented in published CVEs today, even though there is an "impacts" field in the <abbr title="CVE Common Vulnerability and Exposures. A standardized list of publicly known vulnerabilities and exposures maintained by the MITRE Corporation.">CVE</abbr> schema.</li>
+<li>People may want to know the Impact more than the CAPEC (where CAPEC lives under Impact in the schema - and is often used as the only representation of Impact in a <abbr title="CVE Common Vulnerability and Exposures. A standardized list of publicly known vulnerabilities and exposures maintained by the MITRE Corporation.">CVE</abbr>, if at all)</li>
 <li>The <abbr title="CVE Common Vulnerability and Exposures. A standardized list of publicly known vulnerabilities and exposures maintained by the MITRE Corporation.">CVE</abbr> Description (and reference content) impact keyphrases, and the MITRE Technical Impacts that they map to, could be placed in the <abbr title="CVE Common Vulnerability and Exposures. A standardized list of publicly known vulnerabilities and exposures maintained by the MITRE Corporation.">CVE</abbr> schema impacts field.</li>
 </ul>
 </div></section><h1 class='nav-section-title-end'>Ended: Impact</h1><h1 class='nav-section-title-end'>Ended: Common Weakness and Enumeration (CWE)</h1><h1 class='nav-section-title-end'>Ended: Related Standards</h1>