<?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/"
		>
<channel>
	<title>Comments on: How Guilty Hackers Escape</title>
	<atom:link href="http://www.thevirtualcircle.com/2008/11/how-guilty-hackers-escape/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thevirtualcircle.com/2008/11/how-guilty-hackers-escape/</link>
	<description>WordPress site</description>
	<lastBuildDate>Wed, 16 Nov 2011 20:21:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Colin Beveridge</title>
		<link>http://www.thevirtualcircle.com/2008/11/how-guilty-hackers-escape/comment-page-1/#comment-443</link>
		<dc:creator>Colin Beveridge</dc:creator>
		<pubDate>Wed, 19 Nov 2008 22:54:12 +0000</pubDate>
		<guid isPermaLink="false">http://havemacwillblog.com/?p=2933#comment-443</guid>
		<description>Robin

As usual, I agree with much of what you say. However, it is impractical for any organisation of size to restrict access out of hours on a &quot;by exception&quot; basis because, sadly, most data miscreants tend to have higher level access privileges and duties that require constant access.

You rightly suggest that forensically sound preservation of log files is tremendously challenging but intelligent corroboration can be achieved by combining pieces of information. Of course the criminal level of guilt is &quot;beyond reasonable doubt&quot; rather than the lower [and sometimes more convenient] civil level of &quot;on the balance of probability.&quot;

In addition to the measures you mention there are other practical measures to prevent data leakage and  I have recently published a public domain paper for free download on my website at http://tinyurl.com/6eblad</description>
		<content:encoded><![CDATA[<p>Robin</p>
<p>As usual, I agree with much of what you say. However, it is impractical for any organisation of size to restrict access out of hours on a &#8220;by exception&#8221; basis because, sadly, most data miscreants tend to have higher level access privileges and duties that require constant access.</p>
<p>You rightly suggest that forensically sound preservation of log files is tremendously challenging but intelligent corroboration can be achieved by combining pieces of information. Of course the criminal level of guilt is &#8220;beyond reasonable doubt&#8221; rather than the lower [and sometimes more convenient] civil level of &#8220;on the balance of probability.&#8221;</p>
<p>In addition to the measures you mention there are other practical measures to prevent data leakage and  I have recently published a public domain paper for free download on my website at <a href="http://tinyurl.com/6eblad" rel="nofollow">http://tinyurl.com/6eblad</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Served from: www.thevirtualcircle.com @ 2012-02-08 10:24:45 -->
