<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Defining SIEM/Log Management &#8220;Integration&#8221;</title>
	<atom:link href="http://blog.eiqnetworks.com/2009/07/22/defining-siemlog-management-integration/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.eiqnetworks.com/2009/07/22/defining-siemlog-management-integration/</link>
	<description>Perspectives on Security and Compliance Management from eIQnetworks</description>
	<lastBuildDate>Thu, 29 Oct 2009 15:57:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Security, Compliance, SIEM and Log Management: Making sense of it all &#171; eIQviews</title>
		<link>http://blog.eiqnetworks.com/2009/07/22/defining-siemlog-management-integration/#comment-166</link>
		<dc:creator>Security, Compliance, SIEM and Log Management: Making sense of it all &#171; eIQviews</dc:creator>
		<pubDate>Mon, 31 Aug 2009 21:15:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.eiqnetworks.com/?p=225#comment-166</guid>
		<description>[...] This need for both security and compliance has driven for convergence of previously separate technologies (security information and event management (SIEM) and log management) coming together. And now most vendors have solutions to address both problems. Of course, we can (and do) debate about what integration really means, which we wrote about recently on eIQviews. [...]</description>
		<content:encoded><![CDATA[<p>[...] This need for both security and compliance has driven for convergence of previously separate technologies (security information and event management (SIEM) and log management) coming together. And now most vendors have solutions to address both problems. Of course, we can (and do) debate about what integration really means, which we wrote about recently on eIQviews. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Lane</title>
		<link>http://blog.eiqnetworks.com/2009/07/22/defining-siemlog-management-integration/#comment-128</link>
		<dc:creator>Adrian Lane</dc:creator>
		<pubDate>Wed, 22 Jul 2009 17:12:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.eiqnetworks.com/?p=225#comment-128</guid>
		<description>Nice post. The goal here is to provide a breadth of functionality without the end user having the underlying technology complexities shoved in their face.

Agree with almost all of it except point 3. Just because the engine that performs the analysis is not owned by the SIEM provider. In fact, I would like the option of including different analysis -even correlation- engines to see who provides the best results, or use under different circumstances.  Kind of the same thing that I get with email/web security and multiple A/V engines. Maybe when the SIEM market reaches that level of maturity we will see that.

-Adrian</description>
		<content:encoded><![CDATA[<p>Nice post. The goal here is to provide a breadth of functionality without the end user having the underlying technology complexities shoved in their face.</p>
<p>Agree with almost all of it except point 3. Just because the engine that performs the analysis is not owned by the SIEM provider. In fact, I would like the option of including different analysis -even correlation- engines to see who provides the best results, or use under different circumstances.  Kind of the same thing that I get with email/web security and multiple A/V engines. Maybe when the SIEM market reaches that level of maturity we will see that.</p>
<p>-Adrian</p>
]]></content:encoded>
	</item>
</channel>
</rss>
