<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Software, the New Insider Threat</title>
	<link>http://www.cigital.com/justiceleague/2007/08/16/software-the-new-insider-threat/</link>
	<description>The Cigital Software Security and Quality Blog</description>
	<pubDate>Fri, 16 May 2008 03:49:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: gem</title>
		<link>http://www.cigital.com/justiceleague/2007/08/16/software-the-new-insider-threat/#comment-2088</link>
		<pubDate>Fri, 17 Aug 2007 13:00:00 +0000</pubDate>
		<guid>http://www.cigital.com/justiceleague/2007/08/16/software-the-new-insider-threat/#comment-2088</guid>
					<description>As is many times the case, there are two threads of responses going on this idea (neither of them here on the blog).  The first thread is on sc-l (for info on sc-l which all of us at cigital highly recommend, see http://securecoding.org/list/) and another thread has developed on darkreading.

The gist of the two threads focuses on how to define an "insider" and the complexity of modern trust models.

gem</description>
		<content:encoded><![CDATA[<p>As is many times the case, there are two threads of responses going on this idea (neither of them here on the blog).  The first thread is on sc-l (for info on sc-l which all of us at cigital highly recommend, see <a href="http://securecoding.org/list/" rel="nofollow">http://securecoding.org/list/</a>) and another thread has developed on darkreading.</p>
<p>The gist of the two threads focuses on how to define an &#8220;insider&#8221; and the complexity of modern trust models.</p>
<p>gem
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
