<?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: The Fort Knox Approach To Security</title>
	<atom:link href="http://pciguru.wordpress.com/2012/04/06/the-fort-knox-approach-to-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://pciguru.wordpress.com/2012/04/06/the-fort-knox-approach-to-security/</link>
	<description>A common sense approach to achieving PCI compliance and retaining your sanity</description>
	<lastBuildDate>Sat, 18 May 2013 17:32:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: The Fort Knox Approach to Security &#124; IT Security</title>
		<link>http://pciguru.wordpress.com/2012/04/06/the-fort-knox-approach-to-security/#comment-1879</link>
		<dc:creator><![CDATA[The Fort Knox Approach to Security &#124; IT Security]]></dc:creator>
		<pubDate>Tue, 24 Apr 2012 03:22:16 +0000</pubDate>
		<guid isPermaLink="false">http://pciguru.wordpress.com/?p=1003#comment-1879</guid>
		<description><![CDATA[[...] Cross-posted from PCI Guru [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Cross-posted from PCI Guru [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PCIGuru</title>
		<link>http://pciguru.wordpress.com/2012/04/06/the-fort-knox-approach-to-security/#comment-1859</link>
		<dc:creator><![CDATA[PCIGuru]]></dc:creator>
		<pubDate>Mon, 16 Apr 2012 10:17:37 +0000</pubDate>
		<guid isPermaLink="false">http://pciguru.wordpress.com/?p=1003#comment-1859</guid>
		<description><![CDATA[You point out just one of many things that get in the way of properly securing information.  There is also application architecture, ease of user access, reporting, the list can go on and on.  What it takes is management&#039;s willingness to cut through all of that and just say, &quot;We will do what is necessary to ensure we do not suffer a data breach, because I do not want this company&#039;s imaged tarnished over something we could have stopped.&quot;  I have had a couple of clients take that approach and are now very secure versus where they started.]]></description>
		<content:encoded><![CDATA[<p>You point out just one of many things that get in the way of properly securing information.  There is also application architecture, ease of user access, reporting, the list can go on and on.  What it takes is management&#8217;s willingness to cut through all of that and just say, &#8220;We will do what is necessary to ensure we do not suffer a data breach, because I do not want this company&#8217;s imaged tarnished over something we could have stopped.&#8221;  I have had a couple of clients take that approach and are now very secure versus where they started.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: QSA Steve</title>
		<link>http://pciguru.wordpress.com/2012/04/06/the-fort-knox-approach-to-security/#comment-1857</link>
		<dc:creator><![CDATA[QSA Steve]]></dc:creator>
		<pubDate>Mon, 16 Apr 2012 09:40:16 +0000</pubDate>
		<guid isPermaLink="false">http://pciguru.wordpress.com/?p=1003#comment-1857</guid>
		<description><![CDATA[Essentially this is a plea for an approach to security based on risk assessment of information assets.   I wholeheartedly agree that this is the right approach.   In my experience many organisations have never really even analysed exactly what they do hold never mind assessed its value.   However, in practice, assuming that an organisation has taken this first step and knows what they have, the problem is assessing the &#039;right&#039; level of security and the human issue of covering one&#039;s back.  To clarify what I mean, turn the problem around.  Starting with PCI requirements ask yourself, which requirement would I NOT want to apply to this particular dataset and am I happy to justify why not?  And if I am applying it to A, B and C, is it actually going to cost any more to apply it to X,Y,and Z as well?  Suddenly we see why so many will take a one size fits all approach.]]></description>
		<content:encoded><![CDATA[<p>Essentially this is a plea for an approach to security based on risk assessment of information assets.   I wholeheartedly agree that this is the right approach.   In my experience many organisations have never really even analysed exactly what they do hold never mind assessed its value.   However, in practice, assuming that an organisation has taken this first step and knows what they have, the problem is assessing the &#8216;right&#8217; level of security and the human issue of covering one&#8217;s back.  To clarify what I mean, turn the problem around.  Starting with PCI requirements ask yourself, which requirement would I NOT want to apply to this particular dataset and am I happy to justify why not?  And if I am applying it to A, B and C, is it actually going to cost any more to apply it to X,Y,and Z as well?  Suddenly we see why so many will take a one size fits all approach.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
