<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The New School of Information Security &#187; Bejtlich</title>
	<atom:link href="http://newschoolsecurity.com/tag/bejtlich/feed/" rel="self" type="application/rss+xml" />
	<link>http://newschoolsecurity.com</link>
	<description>The Blog Inspired By The Book</description>
	<lastBuildDate>Fri, 11 May 2012 16:20:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Thoughts on Bejtlich&#8217;s Information Security Incident Ratings</title>
		<link>http://newschoolsecurity.com/2009/06/thoughts-on-bejtlichs-information-security-incident-ratings/</link>
		<comments>http://newschoolsecurity.com/2009/06/thoughts-on-bejtlichs-information-security-incident-ratings/#comments</comments>
		<pubDate>Mon, 01 Jun 2009 14:08:50 +0000</pubDate>
		<dc:creator>alex</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Bejtlich]]></category>
		<category><![CDATA[incident metrics]]></category>
		<category><![CDATA[risk modeling]]></category>
		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://newschoolsecurity.com/?p=181</guid>
		<description><![CDATA[Check out Richard Bejtlich&#8217;s Information Security Incident Rating post. In it, he establishes qualitative, color-based scales for various asset-states in relation to the aggregate threat community.  As Richard states, he&#8217;s not modeling risk, but rather he&#8217;s somewhat modeling half of risk (in FAIR terms, an attempt at TEF/LEF/TCap information, just not the loss magnitude side). [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://taosecurity.blogspot.com/2009/05/information-security-incident-rating.html">Check out Richard Bejtlich&#8217;s Information Security Incident Rating post.</a> In it, he establishes qualitative, color-based scales for various asset-states in relation to the aggregate threat community.  As Richard states, he&#8217;s not modeling risk, but rather he&#8217;s somewhat modeling half of risk (in FAIR terms, an attempt at TEF/LEF/TCap information, just not the loss magnitude side).</p>
<p>I say &#8220;somewhat&#8221; modeling because I find interesting is that Richard seems to be discussing probabilistic statements in the &#8220;greens&#8221; there (&#8220;my opinion/guess is that it would take some degree of force to compromise asset in question based on my admittedly incomplete knowledge of the control state&#8221;) , and then adding to that nature-state assessments (&#8220;here is the current state of attack/compromise&#8221;) in the rest of the spectrum.</p>
<p>Now obviously the probabilistic statements would eventually require more effort once some substantial level of organizational maturity has been achieved, but this sort of asset-state spectrum would be useful in establishing high-level assessments of the asset landscape.  It would allow the CISO (esp. a new CISO who finds herself in an environment fraught with &#8220;unknown, unknowns&#8221;) to create a relatively quick view of enterprise &#8220;vulnerability&#8221; (to borrow FAIR&#8217;s concept) and help begin the achievement of knowledge around enterprise risk management capability.</p>
<p>Other uses could eventually contribute significantly to risk models.  Obtaining accurate current/past Category 3 (the orange there) information would be *really* useful for creating probabilistic statements around threat models and risk models.  As I mentioned above, the Vuln ratings can be broken down to assist risk and risk management modeling (yeah, I continue to maintain that they are two different things despite what all the standards out there say, more on that tomorrow).  Finally, studying time frames and abilities around the post-compromise state (Breach 3-1, there) around incidents would be useful in establishing risk management model belief statements, as well.</p>
<p>One small problem I would have using this on an aggregate level would be the lack of granularity around the threat community w/regards to &#8220;impact&#8221; levels 1-5.  I might not really care if a script kiddie is doing reconnaissance, but if the recon is coming from someone in an internal administrative role, a contractor who has privileges, etc&#8230;</p>
<p>That said, my significant problem with Bejtlich&#8217;s model there has to do with <strong>*why*</strong> he created it.  He asks:</p>
<blockquote><p>What do you think of this rating system?  I am curious to hear how others explain the seriousness of an incident to management.</p></blockquote>
<p>To which my obvious response is, &#8220;<em><strong>why should management care about any of this when it doesn&#8217;t include impact&#8221;</strong></em>?  Even at it&#8217;s darkest colors, the scale is subject what I call the <em>tree falling in the woods problem</em> &#8211; does vulnerability or compromise matter independent of an impact statement?  Without impact, are we just &#8220;multiplying by zero&#8221;?</p>
<p>More directly, can you imagine going to a CFO with this but <em>without</em> impact information?  Wouldn&#8217;t you kind of look foolish if you said, when questioned about (probable) impact, &#8220;Well, then we would be modeling<em><strong> risk</strong></em>, and you know we can&#8217;t do that&#8221;?</p>
]]></content:encoded>
			<wfw:commentRss>http://newschoolsecurity.com/2009/06/thoughts-on-bejtlichs-information-security-incident-ratings/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

