<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Security Template Exception (part 2) – The Assessment</title>
	<atom:link href="http://risktical.com/2008/11/06/security-template-exception-part-2-%e2%80%93-the-assessment/feed/" rel="self" type="application/rss+xml" />
	<link>http://risktical.com/2008/11/06/security-template-exception-part-2-%e2%80%93-the-assessment/</link>
	<description>Assessing, Articulating &#38; Quantifying Information Security Risk</description>
	<lastBuildDate>Fri, 04 Jun 2010 19:07:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Audit Trail Blog Archive &#187; Risk Intrigue</title>
		<link>http://risktical.com/2008/11/06/security-template-exception-part-2-%e2%80%93-the-assessment/#comment-133</link>
		<dc:creator>Audit Trail Blog Archive &#187; Risk Intrigue</dc:creator>
		<pubDate>Mon, 17 Nov 2008 18:14:05 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.wordpress.com/?p=120#comment-133</guid>
		<description>[...] King (whose risk management blog is at computerweekly.com)? It seems Stuart believes Chris&#8217;s strategies for risk assessment are impractical. Chris, in a response, takes a stab at explaining how he and [...]</description>
		<content:encoded><![CDATA[<p>[...] King (whose risk management blog is at computerweekly.com)? It seems Stuart believes Chris&#8217;s strategies for risk assessment are impractical. Chris, in a response, takes a stab at explaining how he and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rational Risk Management, &#8216;Angry Italians&#8217;, and Irrational Security Analysts &#124; RiskAnalys.is</title>
		<link>http://risktical.com/2008/11/06/security-template-exception-part-2-%e2%80%93-the-assessment/#comment-131</link>
		<dc:creator>Rational Risk Management, &#8216;Angry Italians&#8217;, and Irrational Security Analysts &#124; RiskAnalys.is</dc:creator>
		<pubDate>Mon, 17 Nov 2008 16:43:24 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.wordpress.com/?p=120#comment-131</guid>
		<description>[...] you all had a great weekend.  I had meant to point you earlier to a FAIR analysis that Chris Hayes did over at his Blog.  But I&#8217;ve been a little busy, and before I could mention it, Stuart King put up a kind of [...]</description>
		<content:encoded><![CDATA[<p>[...] you all had a great weekend.  I had meant to point you earlier to a FAIR analysis that Chris Hayes did over at his Blog.  But I&#8217;ve been a little busy, and before I could mention it, Stuart King put up a kind of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hayes</title>
		<link>http://risktical.com/2008/11/06/security-template-exception-part-2-%e2%80%93-the-assessment/#comment-118</link>
		<dc:creator>Chris Hayes</dc:creator>
		<pubDate>Fri, 07 Nov 2008 02:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.wordpress.com/?p=120#comment-118</guid>
		<description>@ Christian - Thank you so much for the kind feedback! If you have any suggestions on any specific types of scenarios in the future - let me know! Take care!</description>
		<content:encoded><![CDATA[<p>@ Christian &#8211; Thank you so much for the kind feedback! If you have any suggestions on any specific types of scenarios in the future &#8211; let me know! Take care!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian</title>
		<link>http://risktical.com/2008/11/06/security-template-exception-part-2-%e2%80%93-the-assessment/#comment-117</link>
		<dc:creator>Christian</dc:creator>
		<pubDate>Fri, 07 Nov 2008 02:12:29 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.wordpress.com/?p=120#comment-117</guid>
		<description>Awesome series of posts Chris! I&#039;m a huge advocate of the FAIR methodology and have helped our internal info risk folk also start to leverage some of the methodology and language in to our existent, legacy processes.

What is really interesting is the way you have documented out the process is very similar to how I&#039;ve used the FAIR method to document and assess info risk scenarios here at work. As you highlight, walking through the BRAG is a very effective way to do a quick review of a particular scenario.

Another thing that I really enjoyed about this series was bringing quite common scenarios out into the open. I&#039;m all for the concept of &#039;open&#039; RA, particularly because there are a number of scenarios out there that multiple companies are facing, and whilst some of the context is different per company, people can still accommodate for that.

I&#039;ll definitely be sharing these posts with some colleagues.

Cheers!</description>
		<content:encoded><![CDATA[<p>Awesome series of posts Chris! I&#8217;m a huge advocate of the FAIR methodology and have helped our internal info risk folk also start to leverage some of the methodology and language in to our existent, legacy processes.</p>
<p>What is really interesting is the way you have documented out the process is very similar to how I&#8217;ve used the FAIR method to document and assess info risk scenarios here at work. As you highlight, walking through the BRAG is a very effective way to do a quick review of a particular scenario.</p>
<p>Another thing that I really enjoyed about this series was bringing quite common scenarios out into the open. I&#8217;m all for the concept of &#8216;open&#8217; RA, particularly because there are a number of scenarios out there that multiple companies are facing, and whilst some of the context is different per company, people can still accommodate for that.</p>
<p>I&#8217;ll definitely be sharing these posts with some colleagues.</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
