<?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"
	>
<channel>
	<title>Comments on: Application Logging Is Critical In Detecting Attacks</title>
	<atom:link href="http://www.liquidmatrix.org/blog/2006/07/11/application-logging-is-critical-in-detecting-attacks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.liquidmatrix.org/blog/2006/07/11/application-logging-is-critical-in-detecting-attacks/</link>
	<description>Bringing Fire To The Village: Your Source For Computer, Network &#38; Information Security News from Dave Lewis, Security Blogger</description>
	<pubDate>Thu, 04 Dec 2008 08:13:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: A MattPayne.org blog &#187; Liquidmatrix Security Digest</title>
		<link>http://www.liquidmatrix.org/blog/2006/07/11/application-logging-is-critical-in-detecting-attacks/#comment-905</link>
		<dc:creator>A MattPayne.org blog &#187; Liquidmatrix Security Digest</dc:creator>
		<pubDate>Wed, 12 Jul 2006 19:11:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.liquidmatrix.org/blog/2006/07/11/application-logging-is-critical-in-detecting-attacks/#comment-905</guid>
		<description>[...] Liquidmatrix Security Digest “It was the damn network again!” This tired refrain is often the refuge of the application developer. I have built a career on explaining to coders why it isn’t the network or the firewall that is causing an app to break. What has to happen is that application developers have to wake up and take some accountability. That being said, one way to improve matters is to have better application logging. Or better yet, REVIEW the logs that apps generate. Simple root cause analysis seems to be dying a slow, agonizing death replaced by the pointed finger. [...]</description>
		<content:encoded><![CDATA[<p>[...] Liquidmatrix Security Digest “It was the damn network again!” This tired refrain is often the refuge of the application developer. I have built a career on explaining to coders why it isn’t the network or the firewall that is causing an app to break. What has to happen is that application developers have to wake up and take some accountability. That being said, one way to improve matters is to have better application logging. Or better yet, REVIEW the logs that apps generate. Simple root cause analysis seems to be dying a slow, agonizing death replaced by the pointed finger. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
