<?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 &#187; Security</title>
	<atom:link href="http://www.syslog.org/logged/category/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.syslog.org/logged</link>
	<description>Event and Log Management</description>
	<lastBuildDate>Sun, 25 Jul 2010 21:40:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Determining What To Monitor</title>
		<link>http://www.syslog.org/logged/determining-what-to-monitor/</link>
		<comments>http://www.syslog.org/logged/determining-what-to-monitor/#comments</comments>
		<pubDate>Sun, 28 Mar 2010 03:32:08 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Policy]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[IPS]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=224</guid>
		<description><![CDATA[Earlier in my career, I was the IT director for a medium sized enterprise and had responsibility for information security, in addition to networking, server ops, help desk, etc.  I was fortunate to be able to start with a mostly clean slate and had the help of many talented and energetic thinkers.  The company was [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/determining-what-to-monitor/">Determining What To Monitor</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/determining-what-to-monitor/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<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 [...]<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>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.  [...]<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>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:    [...]<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>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 [...]<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>
		<item>
		<title>How To Avoid Source Spoofing In Centralized Syslog Environments</title>
		<link>http://www.syslog.org/logged/how-to-avoid-source-spoofing-in-centralized-syslog-environments/</link>
		<comments>http://www.syslog.org/logged/how-to-avoid-source-spoofing-in-centralized-syslog-environments/#comments</comments>
		<pubDate>Sun, 17 May 2009 20:04:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[stunnel]]></category>
		<category><![CDATA[tcp]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=95</guid>
		<description><![CDATA[An obvious weakness of the syslog network protocol is the ease of spoofing messages into a central syslog server.   The default use of UDP as a transport and lack of any sort of authentication, in fact, make it trivial to spoof any part of a syslog message. The most concerning issue with spoofing is faking [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/how-to-avoid-source-spoofing-in-centralized-syslog-environments/">How To Avoid Source Spoofing In Centralized Syslog Environments</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/how-to-avoid-source-spoofing-in-centralized-syslog-environments/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Establishing a Hardened Syslog Log Server</title>
		<link>http://www.syslog.org/logged/establishing-a-hardened-syslog-log-server/</link>
		<comments>http://www.syslog.org/logged/establishing-a-hardened-syslog-log-server/#comments</comments>
		<pubDate>Wed, 29 Apr 2009 22:58:36 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Log Management]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[logging]]></category>
		<category><![CDATA[Centralized Log Server]]></category>
		<category><![CDATA[Log Management Service]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=78</guid>
		<description><![CDATA[Maintaining a reliable and secure repository of logs is important for many reasons: establishing a foresnic trail of evidence in the case of fraud or attack, and enabling event correlation across many devices, among others.  Particularly in regulated industries, management should enact controls that prevent security, application and system logs from being tampered with. Many [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/establishing-a-hardened-syslog-log-server/">Establishing a Hardened Syslog Log Server</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/establishing-a-hardened-syslog-log-server/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>On The Importance of Centralized Windows Event Logging</title>
		<link>http://www.syslog.org/logged/on-the-importance-of-centralized-windows-event-logging/</link>
		<comments>http://www.syslog.org/logged/on-the-importance-of-centralized-windows-event-logging/#comments</comments>
		<pubDate>Mon, 27 Apr 2009 19:55:42 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[logging]]></category>
		<category><![CDATA[forensic logs]]></category>
		<category><![CDATA[Windows syslog]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=70</guid>
		<description><![CDATA[I was just catching up on my reading on Technorati and came across this article that details the ways attackers can cover their tracks upon compromising a Windows server.  This article should serve as a warning: if your logs are not moved off to a separate server, you will lose visibility and key evidence in [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/on-the-importance-of-centralized-windows-event-logging/">On The Importance of Centralized Windows Event Logging</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/on-the-importance-of-centralized-windows-event-logging/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Logging Windows Events To Syslog Using Snare</title>
		<link>http://www.syslog.org/logged/logging-windows-events-to-syslog-using-snare/</link>
		<comments>http://www.syslog.org/logged/logging-windows-events-to-syslog-using-snare/#comments</comments>
		<pubDate>Wed, 22 Apr 2009 23:28:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Log Management]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[logging]]></category>
		<category><![CDATA[Snare]]></category>
		<category><![CDATA[Windows Logging]]></category>
		<category><![CDATA[Windows syslog]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=58</guid>
		<description><![CDATA[There are now a bunch of commercial and open source agents that can run on a Windows system to take in Windows Event Logs and send them off to a syslog server.  We&#8217;ll be looking at the Snare agent in this post. As of this writing, Snare is compatible with Windows NT, 2000, XP, 2003 [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/logging-windows-events-to-syslog-using-snare/">Logging Windows Events To Syslog Using Snare</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/logging-windows-events-to-syslog-using-snare/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Why Using A Log Management Service Might Be Right For You</title>
		<link>http://www.syslog.org/logged/why-using-a-log-management-service-might-be-right-for-you/</link>
		<comments>http://www.syslog.org/logged/why-using-a-log-management-service-might-be-right-for-you/#comments</comments>
		<pubDate>Sun, 19 Apr 2009 04:09:27 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Log Management]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Log Management Service]]></category>
		<category><![CDATA[Outsourcing]]></category>

		<guid isPermaLink="false">http://www.syslog.org/logged/?p=34</guid>
		<description><![CDATA[There are a growing number of Managed Security Service Providers (MSSP&#8217;s), such as IBM and Symantec, and Verisign, and other companies, such as Savvis, offering an outsourced service to collect and retain system logs, generally called a log management service (LMS).  The initial instinct for many would be to reject such a crazy thought as [...]<p>Post from: <a href="http://www.syslog.org/logged">Logged - Log Management Blog</a><br/><br/><a href="http://www.syslog.org/logged/why-using-a-log-management-service-might-be-right-for-you/">Why Using A Log Management Service Might Be Right For You</a></p>
]]></description>
		<wfw:commentRss>http://www.syslog.org/logged/why-using-a-log-management-service-might-be-right-for-you/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
