<?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>Log Management &#38; SIEM for Security, Compliance, Operations &#124; the dialog &#187; pci</title>
	<atom:link href="http://blog.logrhythm.com/tags/pci/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.logrhythm.com</link>
	<description>Log Management &#38; SIEM for Security, Compliance, Operations &#124; the dialog</description>
	<lastBuildDate>Tue, 24 Apr 2012 15:35:28 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>In the belly of the whale&#8230;</title>
		<link>http://blog.logrhythm.com/security/in-the-belly-of-the-whale/</link>
		<comments>http://blog.logrhythm.com/security/in-the-belly-of-the-whale/#comments</comments>
		<pubDate>Fri, 13 May 2011 19:26:17 +0000</pubDate>
		<dc:creator>npalmer</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[advanced persistent threats]]></category>
		<category><![CDATA[compliance]]></category>
		<category><![CDATA[network security]]></category>
		<category><![CDATA[pci]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[advanced persistent threats,pci,compliance,network security <a href="http://blog.logrhythm.com/security/in-the-belly-of-the-whale/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I recall a story from <a href="http://en.wikipedia.org/wiki/Infant_school">infant school</a>.  It described a holy man being begged by frightened mariners during a storm to pray for calm waters.  He refused, suggesting that it was better not to wait until the storm, but to have acted before the clouds gathered.</p>
<p>To a similar point, &#8216;feast or famine&#8217; is a favourite phrase of mine.  I use it to describe folly of all kinds.  But it&#8217;s a great way to highlight a major organisational shortcoming too &#8211; the side-lining of known important activities in favour of short term pressures.  This is a tactic everyone uses though, surely?  Well, in the security field it&#8217;s not working and hasn&#8217;t worked for years.</p>
<p>&#8220;Little and often&#8217; is another favourite.  I use it to describe a more virtuous method.  It seems that whether you&#8217;re seeking to keep fit, preparing for an important event or even keeping on top of expenses, it&#8217;s a phrase that describes desirable behaviour.  For many organisations, security spending has been far more &#8216;feast or famine&#8217; than &#8216;little and often&#8217;, certainly as long as I have been in the industry anyway.  Could this be about to change?</p>
<p>It all used to be about compliance.  Security-related expenditure, that is.  As long as the compliance box was ticked, the CFO&#8217;s job was safe, and the operations team could avoid getting yelled at in review meetings.  But look at the last three months &#8211; it seems like the highest profile, most trusted brands are haemorrhaging customer information, credit card details and intellectual property to hackers.  I&#8217;m not using those terms licentiously either &#8211; RSA, Sony and even the X-Factor database have been compromised.  Those three events alone could add up to nearly half a billion compromised records.  Does this mean compliance measures are not working?  Well, the recent Verizon report suggests that where breaches have occurred, an overwhelming percentage of the companies that should have been <a href="https://www.pcisecuritystandards.org/">PCI</a> compliant, weren&#8217;t.  89% in fact.  But these recent breaches were all despite compliance systems in being place, which seems to increasingly be the case.</p>
<p>What does this mean in terms of brand confidence?  Here&#8217;s an example.  I spend a lot of money with Amazon annually.  In fact, I transact with them twenty or thirty times a year.   Their customer service is every bit as good as people say.  But, do you think Barnes and Noble or Play.com would get my business if Amazon lost my credit card number?  You bet they would.  Maybe this is where security is at an inflexion point.  Are we at the stage, where organisations have to make &#8216;pre-sale&#8217; commitments to customers about the safety of their data?  Would I move suppliers in favour of someone who offered guarantees as to the safety of my personal information?  Maybe.</p>
<p>In any event, security is getting interesting again.  Do we now work in a discipline which, rather than being a perceived cost and burden to an organisation, could quickly become a competitive differentiator?  I can see it happening, but not while spending patterns are so &#8216;feast or famine &#8216;?  Maybe it&#8217;s time to start bidding for security funding not just for compliance and risk mitigation, but as a way that organisations can improve customer confidence, retention and intimacy through cast-iron security guarantees.</p>
<p>This may sound like blue-sky thinking &#8211; particularly in the context of things like <a href="http://en.wikipedia.org/wiki/Advanced_Persistent_Threat">Advanced Persistent Threats (APTs)</a>.  If a syndicate has enough time and resources, won&#8217;t they always find a way in?  Not if you have the right resources to hand.  Whether access to your systems has been socially engineered, or via a stealth APT that may have taken 6 months, a good logging solution is key.  Pinpoint and exploit early warnings, and use targeted resources to take remedial action and mobilise defences quickly.  Be warned though &#8211; feast or famine won&#8217;t work &#8211; this requires a little effort, often.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.logrhythm.com/security/in-the-belly-of-the-whale/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Compliance &#8211; Time to Change the Future</title>
		<link>http://blog.logrhythm.com/compliance/compliance-time-to-change-the-future/</link>
		<comments>http://blog.logrhythm.com/compliance/compliance-time-to-change-the-future/#comments</comments>
		<pubDate>Fri, 13 Aug 2010 05:25:17 +0000</pubDate>
		<dc:creator>mskinner</dc:creator>
				<category><![CDATA[Compliance]]></category>
		<category><![CDATA[gpg 13]]></category>
		<category><![CDATA[information security]]></category>
		<category><![CDATA[log management]]></category>
		<category><![CDATA[pci]]></category>
		<category><![CDATA[protective monitoring]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[pci,information security,log management,protective monitoring,gpg 13 <a href="http://blog.logrhythm.com/compliance/compliance-time-to-change-the-future/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><em><img style="margin: 5px 4px; float: left;" src="http://blog.logrhythm.com/files/G.jpg" alt="groundhog day image" width="183" height="275" />He&#8217;s having the worst day of his life&#8230; over and over again.&#8217; </em></p>
<p>Ring any bells? It&#8217;s the strap line from the film Groundhog Day which sees Bill Murray&#8217;s character, Phil Connors, caught in a time warp &#8211; repeatedly waking up to find that things are exactly the same as the day before.</p>
<p>The film charts Connors&#8217; frustration at being faced with the same situations every single day and seemingly unable to start the next day afresh.</p>
<p>Whether it&#8217;s travelling the same daily commute, or having repeated discussions about the latest information security regulation directive, I&#8217;m sure we&#8217;ve all related to that character at some point. Particularly if you are a miserable old curmudgeon like me (in fact I think you will find that Bill Murray based his screen persona on yours truly&#8230;.)</p>
<p>With a seemingly endless list of new or amended regulations being introduced, it&#8217;s no wonder that IT security professionals can often feel like they&#8217;re stuck in their own Groundhog Day.  No sooner does an organisation achieve compliance for one regulation, than another comes along, often bringing with it a sense of <em>déjà vu</em> for all involved.</p>
<p>Take the <a href="http://www.logrhythm.com/Applications/Compliance/PCIDSS.aspx" target="_blank">Payment Card Industry Data Security Standard</a> for example. The first standard was introduced in December 2004, with the most recent revision in 2008, and an updated version due this October.  As such, the regulation seems to have been around for an eternity and it&#8217;s no wonder that mentioning the subject will trigger a glazed response from many in the industry.</p>
<p>This rings even more true in the public sector where there seems to be a never ending stream of new initiatives and guidelines relating to information management and technology infrastructures. In the UK alone, organisations are faced with, for example, <a href="http://www.logrhythm.com/Applications/Compliance/GCSx.aspx" target="_blank">GSI/GCSX, CoCo</a> compliance and latterly Memo 22 replacement, <a href="http://www.logrhythm.com/Applications/Compliance/ProtectiveMonitoringGPG13.aspx" target="_blank">Good Practice Guide 13 (GPG 13.)</a></p>
<p>Information security is an ever changing beast. As technology evolves, so do the risks posed which is why it&#8217;s imperative that organisations -public and private &#8211; don&#8217;t become complacent when it comes to compliance.</p>
<p>As Bill Murray found in Groundhog Day, the only way to escape the monotony of his time warp was to re-assess his attitude to life. Of course I&#8217;m not suggesting for one minute that we turn our lives upside down, but there&#8217;s a lot to be said for taking a proactive approach when it comes to guarding against risk.</p>
<p>In every information security related regulation, there&#8217;s a requirement in some shape or form to protect the information being held by the organisation &#8211; from credit card details to children at risk records.  Despite this, all too often security incidents are discovered after the event, once the damage has been done.</p>
<p><a href="http://www.logrhythm.com/Applications/Compliance/ProtectiveMonitoringGPG13.aspx" target="_blank">Protective Monitoring</a> tools such as LogRhythm&#8217;s bring a new proactive dimension to information security-fulfilling multiple compliance requirements in the process.  By centralising and automating how log data is managed, organisations can gain a clear insight into network and user behaviour.  Any irregular activity is automatically flagged in real-time while reporting for compliance purposes is simpler and less time consuming.</p>
<p>As with most Hollywood films, Bill Murray&#8217;s ultimate goal was to get the girl. While I can&#8217;t guarantee that LogRhythm will bring similar results, it will help ease the Groundhog Day frustrations for those facing the continued compliance struggle.</p>
<p>Unless you&#8217;re happy living in Punxsutawney of course&#8230;.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.logrhythm.com/compliance/compliance-time-to-change-the-future/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

