<?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>The State of Security &#187; PCI DSS</title>
	<atom:link href="http://www.tripwire.com/state-of-security/tag/pci-dss/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tripwire.com/state-of-security</link>
	<description>Debunking myths, analyzing trends and sharing best practices in IT security and compliance.</description>
	<lastBuildDate>Fri, 10 Feb 2012 20:54:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>How Safe is Your Credit Card Data?</title>
		<link>http://www.tripwire.com/state-of-security/compliance/pci/how-safe-is-your-credit-card-data/</link>
		<comments>http://www.tripwire.com/state-of-security/compliance/pci/how-safe-is-your-credit-card-data/#comments</comments>
		<pubDate>Fri, 06 Jan 2012 16:30:15 +0000</pubDate>
		<dc:creator>Cindy Valladares</dc:creator>
				<category><![CDATA[Continuous Monitoring]]></category>
		<category><![CDATA[Cyber Security]]></category>
		<category><![CDATA[File Integrity Monitoring]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Configuration Assessment]]></category>
		<category><![CDATA[IT Security]]></category>
		<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[PCI DSS]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/state-of-security/?p=3937</guid>
		<description><![CDATA[Well, that depends on who is responsible for safeguarding your credit card information. This is a case study of how Point is providing better protection to its customers, merchants in Europe. Organization Point is the leading provider of electronic payment solutions in Europe, serving every type of business that require multi-channel payment capabilities: from small [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/compliance/pci/how-safe-is-your-credit-card-data/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using PCI Compliance As a Business Driver</title>
		<link>http://www.tripwire.com/state-of-security/it-security-data-protection/using-pci-compliance-as-a-business-driver/</link>
		<comments>http://www.tripwire.com/state-of-security/it-security-data-protection/using-pci-compliance-as-a-business-driver/#comments</comments>
		<pubDate>Fri, 04 Nov 2011 19:13:25 +0000</pubDate>
		<dc:creator>Cindy Valladares</dc:creator>
				<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[Log Management and SIEM]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[event management]]></category>
		<category><![CDATA[File Integrity Monitoring]]></category>
		<category><![CDATA[log management]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[tripwire]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=3605</guid>
		<description><![CDATA[Here at Tripwire we get many great customer success stories, so I&#8217;ve decided to start a series of blog posts that bring those stories to you. This week&#8217;s post focuses on a The Logic Group, a large payment processor in the UK. Organization The Logic Group solutions process in excess of three billion credit and [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/it-security-data-protection/using-pci-compliance-as-a-business-driver/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>PCI DSS Compliance: More Carrot and Less Stick?</title>
		<link>http://www.tripwire.com/state-of-security/it-security-data-protection/pci-dss-compliance-more-carrot-and-less-stick/</link>
		<comments>http://www.tripwire.com/state-of-security/it-security-data-protection/pci-dss-compliance-more-carrot-and-less-stick/#comments</comments>
		<pubDate>Tue, 17 May 2011 23:13:02 +0000</pubDate>
		<dc:creator>Cindy Valladares</dc:creator>
				<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[IT Security]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[Risk management]]></category>
		<category><![CDATA[_IT Compliance]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=2497</guid>
		<description><![CDATA[Or a less sexy title: does compliance with mandates such as Payment Card Industry Data Security Standard (PCI DSS) help reduce risks for organizations (the carrot) even though it&#8217;s costly and the consequences of non-compliance even costlier (the stick)? The best politically-correct answer is: it depends on who you are and what your approach to [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/it-security-data-protection/pci-dss-compliance-more-carrot-and-less-stick/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>PCI DSS Picks Up a Missouri Accent with V2’s 11.5b: “Show Me”</title>
		<link>http://www.tripwire.com/state-of-security/compliance/pci/pci-dss-picks-up-a-missouri-accent-with-v2%e2%80%99s-11-5b-%e2%80%9cshow-me%e2%80%9d/</link>
		<comments>http://www.tripwire.com/state-of-security/compliance/pci/pci-dss-picks-up-a-missouri-accent-with-v2%e2%80%99s-11-5b-%e2%80%9cshow-me%e2%80%9d/#comments</comments>
		<pubDate>Mon, 28 Feb 2011 17:30:44 +0000</pubDate>
		<dc:creator>Cindy Valladares</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[File Integrity Monitoring]]></category>
		<category><![CDATA[FIM]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[_IT Compliance]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=1931</guid>
		<description><![CDATA[We all know what PCI 11.5 says, right? At Tripwire it’s almost a corporate anthem: “Deploy file-integrity monitoring tools to alert personnel to unauthorized modification of critical system files, configuration files, or content files&#8230;” Ensuring the integrity of files and configurations is essential to IT security in general, and indispensable in protecting the cardholder information [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/compliance/pci/pci-dss-picks-up-a-missouri-accent-with-v2%e2%80%99s-11-5b-%e2%80%9cshow-me%e2%80%9d/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The implications of Visa’s new Technology Innovation Program (TIP)</title>
		<link>http://www.tripwire.com/state-of-security/it-security-data-protection/the-implications-of-visas-new-technology-innovation-program-tip/</link>
		<comments>http://www.tripwire.com/state-of-security/it-security-data-protection/the-implications-of-visas-new-technology-innovation-program-tip/#comments</comments>
		<pubDate>Wed, 23 Feb 2011 20:02:03 +0000</pubDate>
		<dc:creator>Cindy Valladares</dc:creator>
				<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[TIP]]></category>
		<category><![CDATA[Visa]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=1885</guid>
		<description><![CDATA[A few days ago, Visa announced a new Technology Innovation Program (TIP) that will allow merchants outside of the United States to be exempt from having to validate for PCI DSS. This program will go into effect on March 31, 2011. The TIP program allows non-US merchants to discontinue their compliance with PCI DSS if [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/it-security-data-protection/the-implications-of-visas-new-technology-innovation-program-tip/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PCI Compliance alert: Time to switch to version 2.0 of PCI DSS</title>
		<link>http://www.tripwire.com/state-of-security/compliance/pci/pci-compliance-alert-time-to-switch-to-version-2-0-of-pci-dss/</link>
		<comments>http://www.tripwire.com/state-of-security/compliance/pci/pci-compliance-alert-time-to-switch-to-version-2-0-of-pci-dss/#comments</comments>
		<pubDate>Tue, 22 Feb 2011 17:00:47 +0000</pubDate>
		<dc:creator>David Spark</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[PCI Compliance]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[RSA Conference]]></category>
		<category><![CDATA[RSAC]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=1848</guid>
		<description><![CDATA[PCI compliant? Want to stay that way? Then you&#8217;re going to have to upgrade this year to version 2.0 of the PCI DSS, said Bob Russo, General Manager of the PCI Security Standards Council. What&#8217;s different in version 2.0? Mostly clarifications, said Russo. It isn&#8217;t that much different than 1.0 beyond clarifications. Lot more focus [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/compliance/pci/pci-compliance-alert-time-to-switch-to-version-2-0-of-pci-dss/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The True Cost of Compliance</title>
		<link>http://www.tripwire.com/state-of-security/it-security-data-protection/the-true-cost-of-compliance/</link>
		<comments>http://www.tripwire.com/state-of-security/it-security-data-protection/the-true-cost-of-compliance/#comments</comments>
		<pubDate>Mon, 31 Jan 2011 13:00:56 +0000</pubDate>
		<dc:creator>Cindy Valladares</dc:creator>
				<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[data breach]]></category>
		<category><![CDATA[Infosec]]></category>
		<category><![CDATA[IT Security]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[_IT Compliance]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=1622</guid>
		<description><![CDATA[We often hear from customers and prospects that compliance is expensive and cumbersome, yet it allows them to rally for a piece of the IT security budget. Up to this point, however, there was no data on what the cost of compliance was. In order to provide some quantifiable data on this subject, we partnered [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/it-security-data-protection/the-true-cost-of-compliance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>New PCI Data Security Standard version 2.0</title>
		<link>http://www.tripwire.com/state-of-security/compliance/pci/new-pci-data-security-standard-version-2-0/</link>
		<comments>http://www.tripwire.com/state-of-security/compliance/pci/new-pci-data-security-standard-version-2-0/#comments</comments>
		<pubDate>Wed, 03 Nov 2010 13:00:20 +0000</pubDate>
		<dc:creator>Cindy Valladares</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[PCI DSS v2]]></category>
		<category><![CDATA[PCI SSC]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=1538</guid>
		<description><![CDATA[Last week the Payment Card Industry Security Standard Council released version 2.0 of the PCI Data Security Standard. I&#8217;ve covered my initial impressions of the changes on a previous blogpost. To get a deeper understanding on how the changes may affect your organization, I&#8217;ll be holding a webcast to discuss: Timelines for PCI DSS v2.0 [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/compliance/pci/new-pci-data-security-standard-version-2-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Interesting Facts about Verizon’s PCI Report</title>
		<link>http://www.tripwire.com/state-of-security/it-security-data-protection/interesting-facts-about-verizon%e2%80%99s-pci-report/</link>
		<comments>http://www.tripwire.com/state-of-security/it-security-data-protection/interesting-facts-about-verizon%e2%80%99s-pci-report/#comments</comments>
		<pubDate>Thu, 21 Oct 2010 19:00:13 +0000</pubDate>
		<dc:creator>Cindy Valladares</dc:creator>
				<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[2010 Verizon PCI Compliance Report]]></category>
		<category><![CDATA[PCI DSS]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=1485</guid>
		<description><![CDATA[A couple of weeks ago, Verizon Business issued their first PCI Compliance Report. The report analyses organizations, mainly in the US, who have gone through the PCI DSS validation process and have engaged the services of Verizon’s QSAs. There are a lot of interesting tidbits in this report that I thought would be good to [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/it-security-data-protection/interesting-facts-about-verizon%e2%80%99s-pci-report/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>PCI Resources</title>
		<link>http://www.tripwire.com/state-of-security/compliance/pci/pci-resources/</link>
		<comments>http://www.tripwire.com/state-of-security/compliance/pci/pci-resources/#comments</comments>
		<pubDate>Thu, 16 Sep 2010 14:00:35 +0000</pubDate>
		<dc:creator>~Previous Contributers</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[PCI DSS]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=1229</guid>
		<description><![CDATA[Of course you know that Tripwire offers industry leading solutions to help companies achieve and maintain PCI compliance. But did you know we also offer a large knowledge base, a resource library and superior technical support? And that our experts will guide you every step of the way toward PCI compliance? Well you do now! [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/compliance/pci/pci-resources/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Upset about the subjectivity and ambiguity in the PCI DSS compliance standards? My #BSides submission on the answer&#8230;</title>
		<link>http://www.tripwire.com/state-of-security/it-security-data-protection/upset-about-the-subjectivity-and-ambiguity-in-the-pci-dss-compliance-standards-my-bsides-submission-on-the-answer/</link>
		<comments>http://www.tripwire.com/state-of-security/it-security-data-protection/upset-about-the-subjectivity-and-ambiguity-in-the-pci-dss-compliance-standards-my-bsides-submission-on-the-answer/#comments</comments>
		<pubDate>Tue, 01 Jun 2010 15:31:31 +0000</pubDate>
		<dc:creator>~Previous Contributers</dc:creator>
				<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Compliance #BSides]]></category>
		<category><![CDATA[Gene Kim]]></category>
		<category><![CDATA[PCI DSS]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=1030</guid>
		<description><![CDATA[(First a disclaimer: Although I am part of the leadership team of the PCI Scoping Special Interest Group, everything in this article are only my opinions, not anyone else’s, or an official position of the PCI Security Standards Council.) Don’t get me wrong.  I think the mission behind the Payment Card Industry Data Security Standard [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/it-security-data-protection/upset-about-the-subjectivity-and-ambiguity-in-the-pci-dss-compliance-standards-my-bsides-submission-on-the-answer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>RSA 2010: PCI 2.0? What’s Next for the PCI Security Standards and Council?</title>
		<link>http://www.tripwire.com/state-of-security/it-security-data-protection/pci-2-0-whats-next-for-the-pci-security-standards-and-council/</link>
		<comments>http://www.tripwire.com/state-of-security/it-security-data-protection/pci-2-0-whats-next-for-the-pci-security-standards-and-council/#comments</comments>
		<pubDate>Wed, 03 Mar 2010 17:30:23 +0000</pubDate>
		<dc:creator>David Spark</dc:creator>
				<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[IT Security]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[RSA]]></category>
		<category><![CDATA[RSA 2010]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=553</guid>
		<description><![CDATA[David Spark here reporting for Tripwire at the 2010 RSA Conference in San Francisco. What makes the mainstream news in security? High profile data breaches especially with credit cards. In an effort to improve the value of your organization&#8217;s security strategy and hopefully keep all of us out of the news, Bob Russo, General Manager [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/it-security-data-protection/pci-2-0-whats-next-for-the-pci-security-standards-and-council/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>ThereÃ¢â‚¬â„¢s nothing wrong with PCI DSS that cannot be cured by following it</title>
		<link>http://www.tripwire.com/state-of-security/compliance/pci/there%e2%80%99s-nothing-wrong-with-pci-dss-that-cannot-be-cured-by-following-it/</link>
		<comments>http://www.tripwire.com/state-of-security/compliance/pci/there%e2%80%99s-nothing-wrong-with-pci-dss-that-cannot-be-cured-by-following-it/#comments</comments>
		<pubDate>Sat, 09 May 2009 03:06:53 +0000</pubDate>
		<dc:creator>Ed Rarick</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[continuous compliance]]></category>
		<category><![CDATA[data breach]]></category>
		<category><![CDATA[PCI DSS]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Verison Business]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=310</guid>
		<description><![CDATA[I continue to hear comments that PCI DSS doesn’t work and that it should be modified or even eliminated. My favorite recent criticism was from Rep. Yvette Clarke (D-N.Y.) when she said &#8220;the standard by itself is simply not enough to protect cardholder data… I do want to dispel the myth once and for all [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/compliance/pci/there%e2%80%99s-nothing-wrong-with-pci-dss-that-cannot-be-cured-by-following-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Would Tripwire have caught the Heartland Payment breach sooner?</title>
		<link>http://www.tripwire.com/state-of-security/compliance/pci/would-tripwire-have-caught-the-heartland-payment-breach-sooner/</link>
		<comments>http://www.tripwire.com/state-of-security/compliance/pci/would-tripwire-have-caught-the-heartland-payment-breach-sooner/#comments</comments>
		<pubDate>Fri, 13 Feb 2009 01:14:21 +0000</pubDate>
		<dc:creator>Ed Rarick</dc:creator>
				<category><![CDATA[PCI]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[Center for Internet Security]]></category>
		<category><![CDATA[CIS]]></category>
		<category><![CDATA[Configuration Assessment]]></category>
		<category><![CDATA[File Integrity Monitoring]]></category>
		<category><![CDATA[Payment Card Industry]]></category>
		<category><![CDATA[PCI DSS]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=260</guid>
		<description><![CDATA[Had Heartland Payment been using Tripwire’s Enhanced File Integrity Monitoring solution, they would have uncovered something amuck within hours or even minutes of being breached—provided the solution was utilized as described below and the alerts were acted upon. Here is a simple summary of what Tripwire’s Enhanced File Integrity Monitoring solution would have provided the [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/compliance/pci/would-tripwire-have-caught-the-heartland-payment-breach-sooner/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

