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
@@ -1510,6 +1528,12 @@ <h2 id="how-to-use-this-guide">How to Use This Guide<a class="headerlink" href="
1510
1528
</ol>
1511
1529
<p>Each of the <abbrtitle="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> Based Prioritization Models above use similar risk factors (known exploitation and likelihood of exploitation, with variants of <abbrtitle="Common Vulnerability Scoring System Standard. A framework for scoring the severity of vulnerabilities based on factors such as exploitability and impact.">CVSS</abbr> base metrics parameters or scores) but in very different ways to rank/score the risk/priority. The outcome is the same - a much more granular prioritization at the high end of risk than offered by <abbrtitle="Common Vulnerability Scoring System Standard. A framework for scoring the severity of vulnerabilities based on factors such as exploitability and impact.">CVSS</abbr>.</p>
1512
1530
<p>If you're looking for the "easy button", or the one scheme to rule them all for <abbrtitle="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> Based Prioritization, you won't find it (here or anywhere else).</p>
1531
+
<h2id="who-contributed-to-this-guide">Who Contributed to This Guide<aclass="headerlink" href="#who-contributed-to-this-guide" title="Permanent link">¶</a></h2>
1532
+
<p>Various experts and thought leaders <ahref="../contributors/">contributed to this guide</a>, including those that:</p>
1533
+
<ul>
1534
+
<li>developed the standards or solutions described in this guide as used in industry</li>
1535
+
<li>have many years of experience in vulnerability management across various <ahref="../../requirements/Requirements/#personas">roles</a></li>
1536
+
</ul>
1513
1537
<h2id="how-to-contribute-to-this-guide">How to Contribute to This Guide<aclass="headerlink" href="#how-to-contribute-to-this-guide" title="Permanent link">¶</a></h2>
1514
1538
<p>You can contribute content or suggest changes:</p>
<li>This code is licensed under the Apache 2 Open Source License.</li>
1539
1563
</ol>
1564
+
<h2id="alternative-or-additional-guidance">Alternative or Additional Guidance<aclass="headerlink" href="#alternative-or-additional-guidance" title="Permanent link">¶</a></h2>
1565
+
<p>This guide is not an introductory or verbose treatment of topics with broader or background context. For that, consider the following (no affiliation to the authors): </p>
1566
+
<ul>
1567
+
<li><ahref="https://www.amazon.com/Effective-Vulnerability-Management-Vulnerable-Ecosystem/dp/1394221207">Effective Vulnerability Management: Managing <abbrtitle="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> in the Vulnerable Digital Ecosystem</a></li>
1568
+
<li><ahref="https://www.amazon.com/Software-Transparency-Security-Software-Driven-Society/dp/1394158483/">Software Transparency: Supply Chain Security in an Era of a Software-Driven Society</a></li>
1569
+
<li><ahref="https://www.amazon.com/Software-Supply-Chain-Security-End/dp/1098133706">Software Supply Chain Security: Securing the End-to-end Supply Chain for Software, Firmware, and Hardware</a></li>
<p>This guide is not affiliated with any Tool/Company/Vendor/Standard/Forum/Data source. </p>
1544
-
<ol>
1545
-
<li>Mention of a vendor in this guide is not a recommendation or endorsement of that vendor. <ol>
1546
-
<li>The choice of vendors was determined by different contributors who had an interest in that vendor.</li>
1547
-
</ol>
1548
-
</li>
1575
+
<li>This guide is not affiliated with any Tool/Company/Vendor/Standard/Forum/Data source. <ol>
1576
+
<li>Mention of a vendor in this guide is not a recommendation or endorsement of that vendor.
1577
+
1. The choice of vendors was determined by different contributors who had an interest in that vendor.</li>
1549
1578
</ol>
1550
1579
</li>
1551
-
<li>
1552
-
<p>This guide is a living document i.e. it will change and grow over time - with your input.</p>
1553
-
</li>
1580
+
<li>This guide is a living document i.e. it will change and grow over time - with your input.</li>
1554
1581
</ol>
1555
-
<h2id="alternative-or-additional-guidance">Alternative or Additional Guidance<aclass="headerlink" href="#alternative-or-additional-guidance" title="Permanent link">¶</a></h2>
1556
-
<p>This guide is not a verbose treatment of topics with broader or background context. For that, consider the following (no affiliation to the author): </p>
1557
-
<ul>
1558
-
<li><ahref="https://www.amazon.com/Effective-Vulnerability-Management-Vulnerable-Ecosystem/dp/1394221207">Effective Vulnerability Management: Managing <abbrtitle="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> in the Vulnerable Digital Ecosystem</a></li>
<p>A large part of that was to be able to prioritize vulnerabilities by Real <abbrtitle="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr>. </p>
1337
1337
<p>Lots of dumb questions and data analysis later, this guide represents the distillation of that knowledge into a user-centric system view - what I wish I knew before I started - and learnt by interacting with other users, standards groups, and tool vendors. </p>
1338
1338
<p>There's a friendly vibrant community in this space - many of whom have contributed to this guide.</p>
1339
-
<p>Special thanks to my colleague Lisa for the expert input, keeping all this real, and tolerating more dumb questions than any human should endure in one lifetime!</p>
1339
+
<p><imgalt="🙏" class="twemoji" src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/1f64f.svg" title=":pray:" /> Special thanks to</p>
1340
+
<ol>
1341
+
<li>My family <imgalt="❤" class="twemoji" src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/2764.svg" title=":heart:" /></li>
1342
+
<li>My employer Yahoo for cultivating such a rich environment for people to thrive.</li>
1343
+
<li>My colleague Lisa for the expert input, keeping all this real, and tolerating more dumb questions than any human should endure in one lifetime!</li>
Copy file name to clipboardExpand all lines: print_page/index.html
+26-16Lines changed: 26 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -1602,6 +1602,12 @@ <h2 id="introduction-introduction-how-to-use-this-guide">How to Use This Guide<a
1602
1602
</ol>
1603
1603
<p>Each of the <abbrtitle="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> Based Prioritization Models above use similar risk factors (known exploitation and likelihood of exploitation, with variants of <abbrtitle="Common Vulnerability Scoring System Standard. A framework for scoring the severity of vulnerabilities based on factors such as exploitability and impact.">CVSS</abbr> base metrics parameters or scores) but in very different ways to rank/score the risk/priority. The outcome is the same - a much more granular prioritization at the high end of risk than offered by <abbrtitle="Common Vulnerability Scoring System Standard. A framework for scoring the severity of vulnerabilities based on factors such as exploitability and impact.">CVSS</abbr>.</p>
1604
1604
<p>If you're looking for the "easy button", or the one scheme to rule them all for <abbrtitle="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> Based Prioritization, you won't find it (here or anywhere else).</p>
1605
+
<h2id="introduction-introduction-who-contributed-to-this-guide">Who Contributed to This Guide<aclass="headerlink" href="#introduction-introduction-who-contributed-to-this-guide" title="Permanent link">¶</a></h2>
1606
+
<p>Various experts and thought leaders <ahref="#introduction-contributors">contributed to this guide</a>, including those that:</p>
1607
+
<ul>
1608
+
<li>developed the standards or solutions described in this guide as used in industry</li>
1609
+
<li>have many years of experience in vulnerability management across various <ahref="#requirements-requirements-personas">roles</a></li>
1610
+
</ul>
1605
1611
<h2id="introduction-introduction-how-to-contribute-to-this-guide">How to Contribute to This Guide<aclass="headerlink" href="#introduction-introduction-how-to-contribute-to-this-guide" title="Permanent link">¶</a></h2>
1606
1612
<p>You can contribute content or suggest changes:</p>
<li>This code is licensed under the Apache 2 Open Source License.</li>
1631
1637
</ol>
1638
+
<h2id="introduction-introduction-alternative-or-additional-guidance">Alternative or Additional Guidance<aclass="headerlink" href="#introduction-introduction-alternative-or-additional-guidance" title="Permanent link">¶</a></h2>
1639
+
<p>This guide is not an introductory or verbose treatment of topics with broader or background context. For that, consider the following (no affiliation to the authors): </p>
1640
+
<ul>
1641
+
<li><ahref="https://www.amazon.com/Effective-Vulnerability-Management-Vulnerable-Ecosystem/dp/1394221207">Effective Vulnerability Management: Managing <abbrtitle="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> in the Vulnerable Digital Ecosystem</a></li>
1642
+
<li><ahref="https://www.amazon.com/Software-Transparency-Security-Software-Driven-Society/dp/1394158483/">Software Transparency: Supply Chain Security in an Era of a Software-Driven Society</a></li>
1643
+
<li><ahref="https://www.amazon.com/Software-Supply-Chain-Security-End/dp/1098133706">Software Supply Chain Security: Securing the End-to-end Supply Chain for Software, Firmware, and Hardware</a></li>
<p>This guide is not affiliated with any Tool/Company/Vendor/Standard/Forum/Data source. </p>
1636
-
<ol>
1637
-
<li>Mention of a vendor in this guide is not a recommendation or endorsement of that vendor. <ol>
1638
-
<li>The choice of vendors was determined by different contributors who had an interest in that vendor.</li>
1649
+
<li>This guide is not affiliated with any Tool/Company/Vendor/Standard/Forum/Data source. <ol>
1650
+
<li>Mention of a vendor in this guide is not a recommendation or endorsement of that vendor.
1651
+
1. The choice of vendors was determined by different contributors who had an interest in that vendor.</li>
1639
1652
</ol>
1640
1653
</li>
1654
+
<li>This guide is a living document i.e. it will change and grow over time - with your input.</li>
1641
1655
</ol>
1642
-
</li>
1643
-
<li>
1644
-
<p>This guide is a living document i.e. it will change and grow over time - with your input.</p>
1645
-
</li>
1646
-
</ol>
1647
-
<h2id="introduction-introduction-alternative-or-additional-guidance">Alternative or Additional Guidance<aclass="headerlink" href="#introduction-introduction-alternative-or-additional-guidance" title="Permanent link">¶</a></h2>
1648
-
<p>This guide is not a verbose treatment of topics with broader or background context. For that, consider the following (no affiliation to the author): </p>
1649
-
<ul>
1650
-
<li><ahref="https://www.amazon.com/Effective-Vulnerability-Management-Vulnerable-Ecosystem/dp/1394221207">Effective Vulnerability Management: Managing <abbrtitle="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr> in the Vulnerable Digital Ecosystem</a></li>
<p>Thanks to all who contributed! <imgalt="🙏" class="twemoji" src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/1f64f.svg" title=":pray:" /></p>
1653
1658
<p>Many experts volunteered their time and knowledge to this guide - and for that
<p>A large part of that was to be able to prioritize vulnerabilities by Real <abbrtitle="The likelihood of a vulnerability being exploited and the potential impact of such an exploit on an organization.">Risk</abbr>. </p>
1678
1683
<p>Lots of dumb questions and data analysis later, this guide represents the distillation of that knowledge into a user-centric system view - what I wish I knew before I started - and learnt by interacting with other users, standards groups, and tool vendors. </p>
1679
1684
<p>There's a friendly vibrant community in this space - many of whom have contributed to this guide.</p>
1680
-
<p>Special thanks to my colleague Lisa for the expert input, keeping all this real, and tolerating more dumb questions than any human should endure in one lifetime!</p></section><sectionclass="print-page" id="introduction-scope"><h1id="introduction-scope-scope">Scope<aclass="headerlink" href="#introduction-scope-scope" title="Permanent link">¶</a></h1>
1685
+
<p><imgalt="🙏" class="twemoji" src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/1f64f.svg" title=":pray:" /> Special thanks to</p>
1686
+
<ol>
1687
+
<li>My family <imgalt="❤" class="twemoji" src="https://cdn.jsdelivr.net/gh/jdecked/twemoji@15.0.3/assets/svg/2764.svg" title=":heart:" /></li>
1688
+
<li>My employer Yahoo for cultivating such a rich environment for people to thrive.</li>
1689
+
<li>My colleague Lisa for the expert input, keeping all this real, and tolerating more dumb questions than any human should endure in one lifetime!</li>
0 commit comments