<?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: Application Security Risk Assessments</title>
	<atom:link href="http://risktical.com/2009/03/16/application-security-risk-assessments/feed/" rel="self" type="application/rss+xml" />
	<link>http://risktical.com/2009/03/16/application-security-risk-assessments/</link>
	<description>Assessing, Articulating &#38; Quantifying Information Security Risk</description>
	<lastBuildDate>Mon, 31 Oct 2011 20:19:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Patrick</title>
		<link>http://risktical.com/2009/03/16/application-security-risk-assessments/#comment-748</link>
		<dc:creator><![CDATA[Patrick]]></dc:creator>
		<pubDate>Wed, 08 Dec 2010 19:19:07 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=168#comment-748</guid>
		<description><![CDATA[Chris,  I stumbled upon your site while searching for an approach to application risk assessments.  I am also a first time application risk assessment noob.  I was tasked to put together an application risk assessment that is &quot;simple&quot; and &quot;do-able&quot; for a small e-commerce company.  Most of the apps are home grown (about 16) that I would like to conduct an risk assessment on.
I have classified them and am trying to put together a questionnaire for the data owners.  Not sure how granular I should get.  Any assistance would be greatly appreciated.

Thanks!]]></description>
		<content:encoded><![CDATA[<p>Chris,  I stumbled upon your site while searching for an approach to application risk assessments.  I am also a first time application risk assessment noob.  I was tasked to put together an application risk assessment that is &#8220;simple&#8221; and &#8220;do-able&#8221; for a small e-commerce company.  Most of the apps are home grown (about 16) that I would like to conduct an risk assessment on.<br />
I have classified them and am trying to put together a questionnaire for the data owners.  Not sure how granular I should get.  Any assistance would be greatly appreciated.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Moloko Monyepao</title>
		<link>http://risktical.com/2009/03/16/application-security-risk-assessments/#comment-353</link>
		<dc:creator><![CDATA[Moloko Monyepao]]></dc:creator>
		<pubDate>Wed, 21 Oct 2009 10:03:34 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=168#comment-353</guid>
		<description><![CDATA[This is good. I am a first time application security assesor. I have been doing normal Security and risk asssessment but never application security. Reading this blog gave me some ideas.

Thanks]]></description>
		<content:encoded><![CDATA[<p>This is good. I am a first time application security assesor. I have been doing normal Security and risk asssessment but never application security. Reading this blog gave me some ideas.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hayes</title>
		<link>http://risktical.com/2009/03/16/application-security-risk-assessments/#comment-245</link>
		<dc:creator><![CDATA[Chris Hayes]]></dc:creator>
		<pubDate>Mon, 20 Apr 2009 14:00:39 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=168#comment-245</guid>
		<description><![CDATA[Jason - You are absolutely right and I think this is adequately covered in paragraph 6. &quot;The first three concepts are straightforward and usually give you 80% of the information you need to facilitate a risk assessment. The last three concepts usually require more time and understanding.&quot; In my experience using the methodology I have outlined, the first three parts can usually be accomplished in an hour or so - depending on the amount of information available to the assessor. Think of it as a triage review. From there, we determine if we need to deep dive or not. We are on the same sheet of music.]]></description>
		<content:encoded><![CDATA[<p>Jason &#8211; You are absolutely right and I think this is adequately covered in paragraph 6. &#8220;The first three concepts are straightforward and usually give you 80% of the information you need to facilitate a risk assessment. The last three concepts usually require more time and understanding.&#8221; In my experience using the methodology I have outlined, the first three parts can usually be accomplished in an hour or so &#8211; depending on the amount of information available to the assessor. Think of it as a triage review. From there, we determine if we need to deep dive or not. We are on the same sheet of music.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://risktical.com/2009/03/16/application-security-risk-assessments/#comment-244</link>
		<dc:creator><![CDATA[Jason]]></dc:creator>
		<pubDate>Mon, 20 Apr 2009 11:14:01 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=168#comment-244</guid>
		<description><![CDATA[Chris,
When referring to &quot;quick&quot;, I mean that an application should be easily profiled for risk.  If there is low risk then the assessment should be minimal with very little time and money spent.  If there is high risk (i.e. sensitive data, high exposure, etc.) then the assessment should scale based on those high risk factors.  Therefore, in this fashion we will focus time and effort appropriately.]]></description>
		<content:encoded><![CDATA[<p>Chris,<br />
When referring to &#8220;quick&#8221;, I mean that an application should be easily profiled for risk.  If there is low risk then the assessment should be minimal with very little time and money spent.  If there is high risk (i.e. sensitive data, high exposure, etc.) then the assessment should scale based on those high risk factors.  Therefore, in this fashion we will focus time and effort appropriately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hayes</title>
		<link>http://risktical.com/2009/03/16/application-security-risk-assessments/#comment-243</link>
		<dc:creator><![CDATA[Chris Hayes]]></dc:creator>
		<pubDate>Sun, 19 Apr 2009 00:58:48 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=168#comment-243</guid>
		<description><![CDATA[@Jason - Hi Jason. The application security post you are referencing is more of a methodology to assess applications. Towards the bottom of my post I state “Of course, once you flush out some risk issues, you can assess them for risk using your favorite risk assessment methodology.” In this case, the ‘favorite risk assessment methodology’ would be where the Cost vs. Risk answer would be questioned. Thanks for the pingback!

Also - in terms of an application risk assessment. I disagree. The speed of the assessment whether it is strictly a code review - or truly a holistic assessment will differ based on time, resources, skill of the assessor, sensitivity of the data at risk.]]></description>
		<content:encoded><![CDATA[<p>@Jason &#8211; Hi Jason. The application security post you are referencing is more of a methodology to assess applications. Towards the bottom of my post I state “Of course, once you flush out some risk issues, you can assess them for risk using your favorite risk assessment methodology.” In this case, the ‘favorite risk assessment methodology’ would be where the Cost vs. Risk answer would be questioned. Thanks for the pingback!</p>
<p>Also &#8211; in terms of an application risk assessment. I disagree. The speed of the assessment whether it is strictly a code review &#8211; or truly a holistic assessment will differ based on time, resources, skill of the assessor, sensitivity of the data at risk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jtbevis</title>
		<link>http://risktical.com/2009/03/16/application-security-risk-assessments/#comment-242</link>
		<dc:creator><![CDATA[jtbevis]]></dc:creator>
		<pubDate>Fri, 17 Apr 2009 21:21:45 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=168#comment-242</guid>
		<description><![CDATA[Chris,

Your approach covers many of the major items.  I see a couple of major gaps that I would consider fundamental for any risk assessment, such as Cost and Metrics.

I wrote a blog post in response to yours which you can see at:
http://infosecalways.com/2009/04/17/application-risk-assessments/ 

As you will see I think your inline with Threat Modeling (it can be used for all applications not just web) but hopefully you can see there are already some pretty good models in use already.  I would look to enhance or build off the existing work already done.

Another item to consider is time.  Most applicaiton risk assessments need to be quick and ongoing as to not disrupt the SDLC.

Jason
http://infosecalways.com]]></description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>Your approach covers many of the major items.  I see a couple of major gaps that I would consider fundamental for any risk assessment, such as Cost and Metrics.</p>
<p>I wrote a blog post in response to yours which you can see at:<br />
<a href="http://infosecalways.com/2009/04/17/application-risk-assessments/" rel="nofollow">http://infosecalways.com/2009/04/17/application-risk-assessments/</a> </p>
<p>As you will see I think your inline with Threat Modeling (it can be used for all applications not just web) but hopefully you can see there are already some pretty good models in use already.  I would look to enhance or build off the existing work already done.</p>
<p>Another item to consider is time.  Most applicaiton risk assessments need to be quick and ongoing as to not disrupt the SDLC.</p>
<p>Jason<br />
<a href="http://infosecalways.com" rel="nofollow">http://infosecalways.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Application Risk Assessments &#171; InfoSecAlways.com</title>
		<link>http://risktical.com/2009/03/16/application-security-risk-assessments/#comment-241</link>
		<dc:creator><![CDATA[Application Risk Assessments &#171; InfoSecAlways.com]]></dc:creator>
		<pubDate>Fri, 17 Apr 2009 21:13:33 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=168#comment-241</guid>
		<description><![CDATA[[...] http://risktical.com/2009/03/16/application-security-risk-assessments/ [...]]]></description>
		<content:encoded><![CDATA[<p>[...] <a href="http://risktical.com/2009/03/16/application-security-risk-assessments/" rel="nofollow">http://risktical.com/2009/03/16/application-security-risk-assessments/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-03-20 &#8226; Bare Identity</title>
		<link>http://risktical.com/2009/03/16/application-security-risk-assessments/#comment-212</link>
		<dc:creator><![CDATA[links for 2009-03-20 &#8226; Bare Identity]]></dc:creator>
		<pubDate>Sat, 21 Mar 2009 00:01:19 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=168#comment-212</guid>
		<description><![CDATA[[...] Application Security Risk Assessments « Risktical Ramblings A pragmatic approach to application security assessments. (tags: security infosec methodology assessment chrishayes) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Application Security Risk Assessments « Risktical Ramblings A pragmatic approach to application security assessments. (tags: security infosec methodology assessment chrishayes) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Interesting Information Security Bits for 03/16/2009 &#124; Infosec Ramblings</title>
		<link>http://risktical.com/2009/03/16/application-security-risk-assessments/#comment-209</link>
		<dc:creator><![CDATA[Interesting Information Security Bits for 03/16/2009 &#124; Infosec Ramblings]]></dc:creator>
		<pubDate>Mon, 16 Mar 2009 18:50:31 +0000</pubDate>
		<guid isPermaLink="false">http://risktical.com/?p=168#comment-209</guid>
		<description><![CDATA[[...] application security risk assessment. Good stuff. I hope he gets permission to share more details. Application Security Risk Assessments &lt;&lt; Risktical Ramblings Tags: ( risk assessment application [...]]]></description>
		<content:encoded><![CDATA[<p>[...] application security risk assessment. Good stuff. I hope he gets permission to share more details. Application Security Risk Assessments &lt;&lt; Risktical Ramblings Tags: ( risk assessment application [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

