Deployed c307d7f with MkDocs version: 1.5.3

Author: Crashedmind

introduction/Introduction/index.html

@@ -1454,7 +1454,7 @@
 <h1 id="introduction">Introduction<a class="headerlink" href="#introduction" title="Permanent link">&para;</a></h1>
 <div class="admonition abstract">
 <p class="admonition-title">About this Guide</p>
-<p>This <abbr title="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> Based Prioritization Guide is a pragmatic user-centric view of risk, the related standards and data sources, and how you can apply them for an effective <abbr title="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> Based Prioritization for your organization.</p>
+<p>This <abbr title="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> Based Prioritization Guide is a pragmatic user-centric view of <a href="../Scope/#per-vulnerability">Relative <abbr title="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> per Vulnerability</a>, the related standards and data sources, and how you can apply them for an effective <abbr title="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> Based Prioritization for your organization.</p>
 <p>It is written by, or contributed to, some of the thought leaders in this space <strong>for YOU.</strong></p>
 <p><a href="https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities"><abbr title="Cybersecurity &amp; Infrastructure Security Agency">CISA</abbr></a>, <a href="https://www.gartner.com/smarterwithgartner/focus-on-the-biggest-security-threats-not-the-most-publicized">Gartner</a>, and others, recommend focusing on vulnerabilities that are known-exploited as an effective approach to risk mitigation and prevention, yet very few organizations do this. </p>
 <p>Maybe because they don't know they should, why they should, or how they should? This guide will cover all these points.</p>

introduction/Scope/index.html

@@ -1341,7 +1341,8 @@ <h2 id="per-vulnerability">Per Vulnerability<a class="headerlink" href="#per-vul
 <p>The scope is 
 - "Per Vulnerability" branch in the diagram below
 - Generic vulnerability data - not the organization-specific context</p>
-<p>A different way of looking at this is that this guide can be used as a first pass triage and prioritization of vulnerabilities, before the overall asset-specific business and runtime context, and remediation context, is considered, and all the context-specific dependencies that go with that.</p>
+<p>A different way of looking at this is that this guide (and the prioritization schemes herein), can be used as a first pass triage and prioritization of vulnerabilities, before the overall asset-specific business and runtime context, and remediation context, is considered, and all the context-specific dependencies that go with that.</p>
+<p>In other words, Relative <abbr title="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> per vulnerability.</p>
 <figure>
 <p><img alt="Image title" src="../../assets/images/risk_remediation_taxonomy.png" /></p>
 <figcaption>The scope for this guide is the "Per Vulnerability" branch</figcaption>

print_page/index.html

@@ -1528,7 +1528,7 @@ <h1 class='nav-section-title' id='section-introduction'>
                         <section class="print-page" id="introduction-introduction"><h1 id="introduction-introduction-introduction">Introduction<a class="headerlink" href="#introduction-introduction-introduction" title="Permanent link">&para;</a></h1>
 <div class="admonition abstract">
 <p class="admonition-title">About this Guide</p>
-<p>This <abbr title="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> Based Prioritization Guide is a pragmatic user-centric view of risk, the related standards and data sources, and how you can apply them for an effective <abbr title="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> Based Prioritization for your organization.</p>
+<p>This <abbr title="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> Based Prioritization Guide is a pragmatic user-centric view of <a href="#introduction-scope-per-vulnerability">Relative <abbr title="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> per Vulnerability</a>, the related standards and data sources, and how you can apply them for an effective <abbr title="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> Based Prioritization for your organization.</p>
 <p>It is written by, or contributed to, some of the thought leaders in this space <strong>for YOU.</strong></p>
 <p><a href="https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities"><abbr title="Cybersecurity &amp; Infrastructure Security Agency">CISA</abbr></a>, <a href="https://www.gartner.com/smarterwithgartner/focus-on-the-biggest-security-threats-not-the-most-publicized">Gartner</a>, and others, recommend focusing on vulnerabilities that are known-exploited as an effective approach to risk mitigation and prevention, yet very few organizations do this. </p>
 <p>Maybe because they don't know they should, why they should, or how they should? This guide will cover all these points.</p>
@@ -1706,7 +1706,8 @@ <h2 id="introduction-scope-per-vulnerability">Per Vulnerability<a class="headerl
 <p>The scope is 
 - "Per Vulnerability" branch in the diagram below
 - Generic vulnerability data - not the organization-specific context</p>
-<p>A different way of looking at this is that this guide can be used as a first pass triage and prioritization of vulnerabilities, before the overall asset-specific business and runtime context, and remediation context, is considered, and all the context-specific dependencies that go with that.</p>
+<p>A different way of looking at this is that this guide (and the prioritization schemes herein), can be used as a first pass triage and prioritization of vulnerabilities, before the overall asset-specific business and runtime context, and remediation context, is considered, and all the context-specific dependencies that go with that.</p>
+<p>In other words, Relative <abbr title="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> per vulnerability.</p>
 <figure>
 <p><img alt="Image title" src="../assets/images/risk_remediation_taxonomy.png" /></p>
 <figcaption>The scope for this guide is the "Per Vulnerability" branch</figcaption>