<?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: Establishing a Hardened Syslog Log Server</title>
	<atom:link href="http://www.syslog.org/logged/establishing-a-hardened-syslog-log-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.syslog.org/logged/establishing-a-hardened-syslog-log-server/</link>
	<description>Event and Log Management</description>
	<lastBuildDate>Thu, 11 Mar 2010 02:53:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Configuring SUDO for Effective Activity Monitoring Via Syslog &#124; Logged</title>
		<link>http://www.syslog.org/logged/establishing-a-hardened-syslog-log-server/comment-page-1/#comment-9</link>
		<dc:creator>Configuring SUDO for Effective Activity Monitoring Via Syslog &#124; Logged</dc:creator>
		<pubDate>Fri, 05 Feb 2010 22:26:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.syslog.org/logged/?p=78#comment-9</guid>
		<description>[...] cover his tracks by deleting logs.  This is best accomplished by streaming the logs to a hardened syslog server, where the administrator doesn&#8217;t have the ability to delete [...]</description>
		<content:encoded><![CDATA[<p>[...] cover his tracks by deleting logs.  This is best accomplished by streaming the logs to a hardened syslog server, where the administrator doesn&#8217;t have the ability to delete [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Building A Program To Manage And Monitor Administrators &#124; Logged</title>
		<link>http://www.syslog.org/logged/establishing-a-hardened-syslog-log-server/comment-page-1/#comment-8</link>
		<dc:creator>Building A Program To Manage And Monitor Administrators &#124; Logged</dc:creator>
		<pubDate>Sun, 24 Jan 2010 21:46:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.syslog.org/logged/?p=78#comment-8</guid>
		<description>[...] user monitoring program&#8221;, defined later.  Following the good practice of sending logs to a hardened log server for storage and processing will prevent determined administrators from covering his tracks by [...]</description>
		<content:encoded><![CDATA[<p>[...] user monitoring program&#8221;, defined later.  Following the good practice of sending logs to a hardened log server for storage and processing will prevent determined administrators from covering his tracks by [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Using Syslog Logs For Validation of Security Policy Compliance &#124; Logged</title>
		<link>http://www.syslog.org/logged/establishing-a-hardened-syslog-log-server/comment-page-1/#comment-7</link>
		<dc:creator>Using Syslog Logs For Validation of Security Policy Compliance &#124; Logged</dc:creator>
		<pubDate>Fri, 07 Aug 2009 21:49:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.syslog.org/logged/?p=78#comment-7</guid>
		<description>[...] ability to remove the log evidence of his presence, which is a very good reason to relay logs to a central syslog server.  It then becomes imperative that administrators with access to root accounts on systems do not [...]</description>
		<content:encoded><![CDATA[<p>[...] ability to remove the log evidence of his presence, which is a very good reason to relay logs to a central syslog server.  It then becomes imperative that administrators with access to root accounts on systems do not [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
