<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: How do I lose thee?  Let me count the ways</title>
	<link>http://thurston.halfcat.org/blog/2007/01/10/how-do-i-lose-thee-let-me-count-the-ways/</link>
	<description>We are the people your IT department warned you about</description>
	<pubDate>Fri,  9 Jan 2009 13:55:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Security Insights Blog &#187; Understanding Different Types of Information Loss</title>
		<link>http://thurston.halfcat.org/blog/2007/01/10/how-do-i-lose-thee-let-me-count-the-ways/#comment-256345</link>
		<pubDate>Fri, 01 Aug 2008 01:05:42 +0000</pubDate>
		<guid>http://thurston.halfcat.org/blog/2007/01/10/how-do-i-lose-thee-let-me-count-the-ways/#comment-256345</guid>
					<description>[...] Chandler Howell has a great post over at the &#8220;Not Bad For a Cubicle&#8221; blog, discussing the three different ways information is lost: accidental loss, selfish loss (which might also be called carelessness) and malicious loss. While these may seem obvious after reading through them, it&#8217;s a nice and simple way of looking at information loss that&#8217;s useful to keep in mind. It&#8217;s often tempting in doing security risk management to focus too much on one or two of these areas, while spending not enough time on the possibility of a third option. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Chandler Howell has a great post over at the &#8220;Not Bad For a Cubicle&#8221; blog, discussing the three different ways information is lost: accidental loss, selfish loss (which might also be called carelessness) and malicious loss. While these may seem obvious after reading through them, it&#8217;s a nice and simple way of looking at information loss that&#8217;s useful to keep in mind. It&#8217;s often tempting in doing security risk management to focus too much on one or two of these areas, while spending not enough time on the possibility of a third option. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Not Bad For a Cubicle &#187; Blog Archive &#187; Risk and security: Separated at Birth</title>
		<link>http://thurston.halfcat.org/blog/2007/01/10/how-do-i-lose-thee-let-me-count-the-ways/#comment-43452</link>
		<pubDate>Thu, 25 Jan 2007 16:45:15 +0000</pubDate>
		<guid>http://thurston.halfcat.org/blog/2007/01/10/how-do-i-lose-thee-let-me-count-the-ways/#comment-43452</guid>
					<description>[...] They agreed that it would do very little to prevent a malicious attacker. If a baby was brought within range of the door&#8217;s sensor, the doors of the maternity ward were wired to mag-lock shut and an alarm would sound. Given the ease of removing the tag, however, that would do little to stop a malicious attacker. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] They agreed that it would do very little to prevent a malicious attacker. If a baby was brought within range of the door&#8217;s sensor, the doors of the maternity ward were wired to mag-lock shut and an alarm would sound. Given the ease of removing the tag, however, that would do little to stop a malicious attacker. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Secure Endpoints &#187; Blog Archive &#187; Data theft, data loss</title>
		<link>http://thurston.halfcat.org/blog/2007/01/10/how-do-i-lose-thee-let-me-count-the-ways/#comment-40966</link>
		<pubDate>Mon, 15 Jan 2007 21:38:47 +0000</pubDate>
		<guid>http://thurston.halfcat.org/blog/2007/01/10/how-do-i-lose-thee-let-me-count-the-ways/#comment-40966</guid>
					<description>[...] Chandler Howell discusses data theft and loss in the risk management blog &#8220;Not Bad For a Cubicle&#8221; last week. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Chandler Howell discusses data theft and loss in the risk management blog &#8220;Not Bad For a Cubicle&#8221; last week. [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
