<div dir="ltr"><div>I'm going to nitpick this. Not because your complaints about CVSS are bad, just that they are unsupported and insufficiently explained.</div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jan 8, 2019 at 8:23 AM Dave Aitel <<a href="mailto:dave.aitel@cyxtera.com">dave.aitel@cyxtera.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div id="gmail-m_3463265021637175619divtagdefaultwrapper" style="font-size:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif" dir="ltr">
<p style="margin-top:0px;margin-bottom:0px">I wanted to take a few minutes and do a quick highlight of a paper from CMU-CERT which I think most people have missed out on: <a href="https://resources.sei.cmu.edu/asset_files/WhitePaper/2018_019_001_538372.pdf" class="gmail-m_3463265021637175619OWAAutoLink" id="gmail-m_3463265021637175619LPlnk432222" target="_blank">https://resources.sei.cmu.edu/asset_files/WhitePaper/2018_019_001_538372.pdf</a></p>
<div id="gmail-m_3463265021637175619LPBorder_GT_15469630031460.183622448101032" style="margin-bottom:20px;overflow:auto;width:100%;text-indent:0px">
<table id="gmail-m_3463265021637175619LPContainer_15469630031410.7814532219479569" cellspacing="0" style="width:90%;background-color:rgb(255,255,255);overflow:auto;padding-top:20px;padding-bottom:20px;margin-top:20px;border-top:1px dotted rgb(200,200,200);border-bottom:1px dotted rgb(200,200,200)">
<tbody>
<tr valign="top" style="border-spacing:0px">
<td id="gmail-m_3463265021637175619TextCell_15469630031430.4920052779439892" colspan="2" style="vertical-align:top;padding:0px;display:table-cell">
<div id="gmail-m_3463265021637175619LPRemovePreviewContainer_15469630031430.19212764500547808"><a id="gmail-m_3463265021637175619LPlnk47344" class="gmail-m_3463265021637175619ms-Icon--x gmail-m_3463265021637175619ms-icon-font-size-14 gmail-m_3463265021637175619OWAAutoLink" style="font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif;font-weight:normal;padding:8px;float:right;color:rgb(102,102,102);background-color:rgb(249,242,252);margin-left:10px"></a></div>
<div id="gmail-m_3463265021637175619LPTitle_15469630031430.5656392074504" style="color:rgb(105,9,139);font-weight:400;font-size:21px;font-family:wf_segoe-ui_light,"Segoe UI Light","Segoe WP Light","Segoe UI","Segoe WP",Tahoma,Arial,sans-serif;line-height:21px">
<a id="gmail-m_3463265021637175619LPUrlAnchor_15469630031440.3834621873971975" href="https://resources.sei.cmu.edu/asset_files/WhitePaper/2018_019_001_538372.pdf" style="text-decoration:none" target="_blank">Towards Improving CVSS - resources.sei.cmu.edu</a></div>
<div id="gmail-m_3463265021637175619LPMetadata_15469630031440.623748296566867" style="margin:10px 0px 16px;color:rgb(102,102,102);font-weight:400;font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif;font-size:14px;line-height:14px">
<a href="http://resources.sei.cmu.edu" target="_blank">resources.sei.cmu.edu</a></div>
<div id="gmail-m_3463265021637175619LPDescription_15469630031450.5530823382524725" style="display:block;color:rgb(102,102,102);font-weight:400;font-family:wf_segoe-ui_normal,"Segoe UI","Segoe WP",Tahoma,Arial,sans-serif;font-size:14px;line-height:20px;max-height:100px;overflow:hidden">
SOFTWARE ENGINEERING INSTITUTE | CARNEGIE MELLON UNIVERSITY REV-03.18.2016.0 Distribution Statement A: Approved for Public Release; Distribution Is Unlimited TOWARDS IMPROVING CVSS</div>
</td>
</tr>
</tbody>
</table>
</div>
It's almost as funny a read as their previous best work on how "<a href="https://www.kb.cert.org/vuls/id/261869/" class="gmail-m_3463265021637175619OWAAutoLink" id="gmail-m_3463265021637175619LPlnk522980" target="_blank">clientless HTTPS VPNs are insanely dumb</a> what were you thinking omg?"
<div><br>
</div>
<div>They use a ton of big words in the paper to call CVSS out and give it a shellacking. Like most of you, we have extensive use of CVSS in our consulting practice and I've seen this stuff first hand. CVSS is of course just a buggy compression algorithm for
taking complex qualitative data and then putting it on a number line. The paper has three angles here: </div>
<div>
<ol style="margin-bottom:0px;margin-top:0px">
<li><span style="font-size:12pt"></span>Qualitative mappings into quantitative numbers are a silly thing to do, like people trying to do "social science" by using SurveyMonkey.</li></ol></div></div></div></blockquote><div><br></div><div><br></div><div>A. I have been smacking people who try to pretend that qualitative measurements are made better by wrapping them in numbers for 15 years. I completely agree.</div><div><br></div><div>Second. We use numbers to represent qualitative values to enable reasoning. You can't multiply High * Medium * Low but you can multiply 5 * 3 * 1. That's not turning qualitative data into quantitative data it is just providing a short cut to think about qualitative data.</div><div><br></div><div>Finally. Social sciences when done right are collecting quantitative data about qualitative data so Survey Monkey is actually useful from that perspective. We will set aside the problem of selection bias due to access and interest in participation for the moment. The point stands; a single person's assessment of a qualitative thing is not data. 10,000 people's assessment of that qualitative thing is data.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div id="gmail-m_3463265021637175619divtagdefaultwrapper" style="font-size:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif" dir="ltr"><div><ol style="margin-bottom:0px;margin-top:0px"><li>We're pretty sure that the compression algorithm is not, in fact, putting higher risk items as bigger numbers, which is the whole point of the thing. </li><li>Nobody is applying this in any sort of consistent way (which is probably impossible) which is ALSO the whole point of the thing.</li></ol>
</div>
<div><br>
</div>
<div>It's fine to have a lossy compression algorithm that emphasizes certain aspects of the input signal over others, of course, but an additional CERT/CC critique is we have no reason to think CVSS does this in any useful way. <br></div></div></div></blockquote><div><br></div><div>1. By definition every compression algorithm emphasizes certain aspects of the signal over others. In this case you are complaining that the parts that are emphasized are not the ones you think are important.</div><div>B. That's completely reasonable. Offer me an alternative. Seriously, I'm not a fan of CVSS but I haven't seen a better alternative to a complete memory dump and description of all the consequences beyond that. So give me an alternative or grab me at the next conference and ply me with drinks and conversation and we can debate it.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div id="gmail-m_3463265021637175619divtagdefaultwrapper" style="font-size:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif" dir="ltr"><div>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
<p style="margin-top:0px;margin-bottom:0px">There's definitely people in the CVSS process (who I will avoid calling out by name) who think ANY quantization is good. But read the paper and decide for yourself - because these are probably serious issues that are
turning your entire risk org into a Garbage-In-Garbage-Out org...</p></div></div></div></blockquote><div><br></div><div>That I cannot agree more with.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div id="gmail-m_3463265021637175619divtagdefaultwrapper" style="font-size:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif" dir="ltr"><div>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
<p style="margin-top:0px;margin-bottom:0px">-dave</p>
<p style="margin-top:0px;margin-bottom:0px"><br>
</p>
</div>
</div>
</div>
_______________________________________________<br>
Dailydave mailing list<br>
<a href="mailto:Dailydave@lists.immunityinc.com" target="_blank">Dailydave@lists.immunityinc.com</a><br>
<a href="https://lists.immunityinc.com/mailman/listinfo/dailydave" rel="noreferrer" target="_blank">https://lists.immunityinc.com/mailman/listinfo/dailydave</a><br>
</blockquote></div></div>