<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Logged</title>
	<atom:link href="http://www.syslog.org/logged/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.syslog.org/logged</link>
	<description>Event and Log Management</description>
	<lastBuildDate>Thu, 11 Mar 2010 02:53:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Using Trends In Logs To Define New Security Requirements For Internet Facing Hosts</title>
		<link>http://www.syslog.org/logged/using-trends-in-logs-to-define-new-security-requirements-for-internet-facing-hosts/</link>
		<comments>http://www.syslog.org/logged/using-trends-in-logs-to-define-new-security-requirements-for-internet-facing-hosts/#comments</comments>
		<pubDate>Thu, 11 Mar 2010 02:53:25 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[attack]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=189</guid>
		<description><![CDATA[I have a few servers at a colocation datacenter for running a number of sites, including this one.  I have written before about detecting brute force attacks in logs.   I have been watching the attacks continue in my logs, and have noticed a few things:
1. The attacks, as before, are coming from many different sources, [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/using-trends-in-logs-to-define-new-security-requirements-for-internet-facing-hosts/">Using Trends In Logs To Define New Security Requirements For Internet Facing Hosts</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/using-trends-in-logs-to-define-new-security-requirements-for-internet-facing-hosts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pot Of Syslog-NG Tricks Version 2</title>
		<link>http://www.syslog.org/logged/pot-of-syslog-ng-tricks-version-2/</link>
		<comments>http://www.syslog.org/logged/pot-of-syslog-ng-tricks-version-2/#comments</comments>
		<pubDate>Wed, 03 Mar 2010 03:04:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[logging]]></category>
		<category><![CDATA[syslog-ng]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=179</guid>
		<description><![CDATA[Correcting bad or duplicate time and date stamps
Trying to accept logs from applications or devices into syslog-ng, but end up seeing two date and time fields in the resulting log coming out of syslog-ng?  This happens because syslog-ng is not able to understand the format that the date and time stamp arrive in.  Here&#8217;s an [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/pot-of-syslog-ng-tricks-version-2/">Pot Of Syslog-NG Tricks Version 2</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/pot-of-syslog-ng-tricks-version-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Designing A Log and Event Monitoring Program</title>
		<link>http://www.syslog.org/logged/designing-a-log-and-event-monitoring-program/</link>
		<comments>http://www.syslog.org/logged/designing-a-log-and-event-monitoring-program/#comments</comments>
		<pubDate>Tue, 23 Feb 2010 02:25:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Policy]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[logging]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=133</guid>
		<description><![CDATA[Ultimately, as with all IT security programs, log monitoring programs are designed to address risks to data confidentiality, integrity and availability.  Risks come in many types:

Hardware failure
System compromise
User error
Rogue administrator

An organization&#8217;s program around log &#38; event monitoring needs to be based on the specific risks that exist in that organization.  Consider two these two scenarios:
Scenario [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/designing-a-log-and-event-monitoring-program/">Designing A Log and Event Monitoring Program</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/designing-a-log-and-event-monitoring-program/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Running Syslog-NG on Windows</title>
		<link>http://www.syslog.org/logged/running-syslog-ng-on-windows/</link>
		<comments>http://www.syslog.org/logged/running-syslog-ng-on-windows/#comments</comments>
		<pubDate>Mon, 22 Feb 2010 01:43:09 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Windows]]></category>
		<category><![CDATA[logging]]></category>
		<category><![CDATA[syslog-ng]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=154</guid>
		<description><![CDATA[This post describes running syslog-ng as a server on Windows.  In another post, we describe how to send Windows Event Logs to syslog.
There are many great commercial syslog servers for Windows.  There are not many options for those looking for a free alternative.  One option is Aonaware.  Another option is to install syslog-ng through cygwin.  [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/running-syslog-ng-on-windows/">Running Syslog-NG on Windows</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/running-syslog-ng-on-windows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pot Of Syslog-NG Tricks Version 1</title>
		<link>http://www.syslog.org/logged/pot-of-syslog-ng-tricks-version-1/</link>
		<comments>http://www.syslog.org/logged/pot-of-syslog-ng-tricks-version-1/#comments</comments>
		<pubDate>Fri, 19 Feb 2010 21:24:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[logging]]></category>
		<category><![CDATA[syslog-ng]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=148</guid>
		<description><![CDATA[Fixing Duplicate Date and/or Hostname Problems
Some devices send syslog messages with improperly formatted headers, which can cause syslog-ng to append a new set of header information, meaning that the host name and/or date appear twice in the logs.  A simple way to solve this is using a template:
source s_net { udp();};
destination d_file { file(&#8220;/var/log/file.log&#8221; template(&#8220;$MSG\n&#8221;)); [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/pot-of-syslog-ng-tricks-version-1/">Pot Of Syslog-NG Tricks Version 1</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/pot-of-syslog-ng-tricks-version-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Defining Log Management and Log Monitoring Objectives</title>
		<link>http://www.syslog.org/logged/defining-log-management-and-log-monitoring-objectives/</link>
		<comments>http://www.syslog.org/logged/defining-log-management-and-log-monitoring-objectives/#comments</comments>
		<pubDate>Fri, 12 Feb 2010 23:19:25 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Log Management]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=139</guid>
		<description><![CDATA[System logs are good for more purposes that many people realize.  In this post, I&#8217;ll describe the four broad categories of log usage.
Forensic Record Keeping
Many organizations choose to archive log data for a period of time for future reference.  Generally, the usefulness of keeping archived logs comes from the situation where a system problem is [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/defining-log-management-and-log-monitoring-objectives/">Defining Log Management and Log Monitoring Objectives</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/defining-log-management-and-log-monitoring-objectives/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Configuring SUDO for Effective Activity Monitoring Via Syslog</title>
		<link>http://www.syslog.org/logged/configuring-sudo-for-effective-activity-monitoring-via-syslog/</link>
		<comments>http://www.syslog.org/logged/configuring-sudo-for-effective-activity-monitoring-via-syslog/#comments</comments>
		<pubDate>Fri, 05 Feb 2010 22:26:43 +0000</pubDate>
		<dc:creator>mutex</dc:creator>
				<category><![CDATA[Accountability]]></category>
		<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Policy]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[logging]]></category>
		<category><![CDATA[SUDO]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=123</guid>
		<description><![CDATA[I have discussed in previous posts the importance of administrators using SUDO to provide individual accountability.  SUDO provides command-by-command accounting of actions performed by administrators, with logs sent as standard syslog events looking like this:
Feb  4 19:23:23 bsd sudo:    jerry : TTY=pts/0 ; PWD=/usr/home/jerry ; USER=root ; COMMAND=/bin/ps -x
Feb  4 19:23:34 bsd sudo:    jerry : [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/configuring-sudo-for-effective-activity-monitoring-via-syslog/">Configuring SUDO for Effective Activity Monitoring Via Syslog</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/configuring-sudo-for-effective-activity-monitoring-via-syslog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building A Program To Manage And Monitor Administrators</title>
		<link>http://www.syslog.org/logged/program-to-manage-and-monitor-administrators/</link>
		<comments>http://www.syslog.org/logged/program-to-manage-and-monitor-administrators/#comments</comments>
		<pubDate>Sun, 24 Jan 2010 21:46:24 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Policy]]></category>
		<category><![CDATA[SUDO]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=111</guid>
		<description><![CDATA[Monitoring the activities of privileged users or server administrators is becoming a common requirement in many organizations for a few reasons:

Compliance with legal or regulatory requirements, such as PCI, HIPAA, etc
Performing outsourcing services to clients who require controls to prevent the service provider&#8217;s employees from causing harm to the client.
A recent experience where a trusted [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/program-to-manage-and-monitor-administrators/">Building A Program To Manage And Monitor Administrators</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/program-to-manage-and-monitor-administrators/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Segregating Logs From Different Log Files On A Centralized Log Server Using Syslog-NG</title>
		<link>http://www.syslog.org/logged/segregating-logs-from-different-log-files-on-a-centralized-log-server-using-syslog-ng/</link>
		<comments>http://www.syslog.org/logged/segregating-logs-from-different-log-files-on-a-centralized-log-server-using-syslog-ng/#comments</comments>
		<pubDate>Sun, 23 Aug 2009 20:22:25 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Log Management]]></category>
		<category><![CDATA[logging]]></category>
		<category><![CDATA[syslog-ng]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=103</guid>
		<description><![CDATA[In this post, I will demonstrate a way to capture logs from a series of log files, and relay those logs to a central log server, where the logs will be separated into log files, as they existed on the original host.
Reading from files
Syslog-ng has the ability to pull log data from files, then treat [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/segregating-logs-from-different-log-files-on-a-centralized-log-server-using-syslog-ng/">Segregating Logs From Different Log Files On A Centralized Log Server Using Syslog-NG</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/segregating-logs-from-different-log-files-on-a-centralized-log-server-using-syslog-ng/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Syslog Logs For Validation of Security Policy Compliance</title>
		<link>http://www.syslog.org/logged/using-syslog-logs-for-validation-of-security-policy-compliance/</link>
		<comments>http://www.syslog.org/logged/using-syslog-logs-for-validation-of-security-policy-compliance/#comments</comments>
		<pubDate>Fri, 07 Aug 2009 21:49:23 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Policy]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=100</guid>
		<description><![CDATA[In a previous post, I wrote about the general use of syslog logs as a method of ensuring compliance with policy.  This is a specific example of how one might use syslog to do that.
As IT operations mature, particularly in regulated environments, it is not uncommon for an organization&#8217;s security policy to require controls on [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/using-syslog-logs-for-validation-of-security-policy-compliance/">Using Syslog Logs For Validation of Security Policy Compliance</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/using-syslog-logs-for-validation-of-security-policy-compliance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
