<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-1426281128647295476.post3233730148672934694..comments</id><updated>2009-06-12T05:48:01.284-05:00</updated><title type='text'>Comments on radi::blog: Threat modeling: bringing it all together</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://radi.r-n-d.org/feeds/3233730148672934694/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1426281128647295476/3233730148672934694/comments/default'/><link rel='alternate' type='text/html' href='http://radi.r-n-d.org/2009/06/threat-modeling-bringing-it-all.html'/><author><name>radi</name><uri>http://www.blogger.com/profile/11459795773754260693</uri><email>radi@r-n-d.org</email></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>1</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-1426281128647295476.post-301360384713316913</id><published>2009-06-12T05:48:01.284-05:00</published><updated>2009-06-12T05:48:01.284-05:00</updated><title type='text'>I personally believe that the distinction you perc...</title><content type='html'>I personally believe that the distinction you perceive at the beginning of this post - that is, financial sector threat modeling vs. technology sector threat modeling - is not a real difference but just a side-effect of the nature of the two sectors. &lt;br /&gt;&lt;br /&gt;All threat modeling is done for a business reason - you don&amp;#39;t do threat modeling to produce nice wallpapers or to be kind to your neighbor, you do it to meet a certain business goal. It is essential, then, that threat modeling begins with the &amp;quot;business goals&amp;quot;-&amp;gt;&amp;quot;business risk&amp;quot;-&amp;gt;&amp;quot;technical risk&amp;quot; mapping step that you are talking about. All threat models should in fact start like this. However, for software vendors - like Microsoft - the technical risks happen to overlap with the business risks, and that&amp;#39;s why IMHO you see this step missing in the MS-sanctioned way of doing threat modeling.&lt;br /&gt;&lt;br /&gt;In other words, when you do threat modeling for a bank, you need to start from the business goals and business risks in order to understand that a certain database is an asset to protect. On the other hand, when you do threat modeling of a system being sold by a software vendor, you already know that whatever user data gets touched by that system, it&amp;#39;ll be an asset to protect.&lt;br /&gt;&lt;br /&gt;My two cents.</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1426281128647295476/3233730148672934694/comments/default/301360384713316913'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1426281128647295476/3233730148672934694/comments/default/301360384713316913'/><link rel='alternate' type='text/html' href='http://radi.r-n-d.org/2009/06/threat-modeling-bringing-it-all.html?showComment=1244803681284#c301360384713316913' title=''/><author><name>Gabe</name><uri>http://www.blogger.com/profile/13958752731645145468</uri><email>noreply@blogger.com</email></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://radi.r-n-d.org/2009/06/threat-modeling-bringing-it-all.html' ref='tag:blogger.com,1999:blog-1426281128647295476.post-3233730148672934694' source='http://www.blogger.com/feeds/1426281128647295476/posts/default/3233730148672934694' type='text/html'/></entry></feed>