 




<?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>Regulatory Compliance, Governance and Security &#187; pci dss logging</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/compliance-governance/tag/pci-dss-logging/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/compliance-governance</link>
	<description></description>
	<lastBuildDate>Thu, 10 Mar 2011 15:04:50 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>PCI DSS Requirement 10: Regularly Monitor and Test Networks</title>
		<link>http://itknowledgeexchange.techtarget.com/compliance-governance/pci-dss-requirement-10-regularly-monitor-and-test-networks/</link>
		<comments>http://itknowledgeexchange.techtarget.com/compliance-governance/pci-dss-requirement-10-regularly-monitor-and-test-networks/#comments</comments>
		<pubDate>Wed, 11 Feb 2009 22:27:01 +0000</pubDate>
		<dc:creator>Charles Denyer</dc:creator>
				<category><![CDATA[12 pci requirements]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[payment card industry data security standards (PCI DSS)]]></category>
		<category><![CDATA[pci audit trails]]></category>
		<category><![CDATA[pci dss logging]]></category>
		<category><![CDATA[PCI Requirement 10: Regularly Monitor and Test Networks]]></category>
		<category><![CDATA[qualified security assessor (QSA)]]></category>
		<category><![CDATA[unix]]></category>
		<category><![CDATA[windows]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/compliance-governance/?p=110</guid>
		<description><![CDATA[Payment Card Industry (PCI) Data Security Standards (DSS) compliance is often not a black and white assessment. Sure the PCI council gives you the complete assessment document, which fully explains each of the twelve (12) requirements and what is needed for validating each of these respective areas. However, it&#8217;s one thing to read them, its [...]]]></description>
				<content:encoded><![CDATA[<p>Payment Card Industry (PCI) Data Security Standards (DSS) compliance is often not a black and white assessment. Sure the PCI council gives you the complete assessment document, which fully explains each of the twelve (12) requirements and what is needed for validating each of these respective areas. However, it&#8217;s one thing to read them, its a another to truly understand what they mean.</p>
<p>Take PCI Requirement 10: Regularly Monitor and Test Networks. The question often asked to me as a <a href="http://www.pciassessment.org">Qualified Security Assessor</a> (QSA) is: What do you want to see logging and audit trails for, that is what systems&#8230;.and if we&#8217;re not logging and producing audit trails, then EXACTLY what system components do we need to start doing this for&#8221;? And in all honesty, this is a great question. It&#8217;s the who, what, when, where and why for requirement 10. </p>
<p>My initial answer is the following: You need to truly &#8220;identify&#8221; all system components in the cardholder environment, thus you need to be able to configure and establish logging and audit trail mechanisms for these &#8220;system components&#8221;. Remember, &#8220;system components&#8221; are just that, any &#8220;system (hardware, software, etc&#8221; used in the cardholder environment. So, at a minimum logging and audit trails NEED to be established for the following:</p>
<p>1. Network Devices (firewalls, routers, etc.)<br />
2. Operating Systems (UNIX/LINUX, Windows)<br />
3. Applications on these Operating Systems that support the &#8220;cardholder environment&#8221;<br />
4. Databases that support the cardholder environment where data is written and saved to.</p>
<p>Remember, this is just a starting point and the above four (4) items are MANDATORY in my view, with many other &#8220;system components&#8221; that could truly be in scope.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/compliance-governance/pci-dss-requirement-10-regularly-monitor-and-test-networks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
