<?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; FIM</title>
	<atom:link href="http://www.tripwire.com/state-of-security/tag/fim/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>Sony PSN Breach Fits Same Trend Seen in 2011 Verizon DBIR</title>
		<link>http://www.tripwire.com/state-of-security/it-security-data-protection/sony-psn-breach-fits-same-trend-seen-in-2011-verizon-dbir/</link>
		<comments>http://www.tripwire.com/state-of-security/it-security-data-protection/sony-psn-breach-fits-same-trend-seen-in-2011-verizon-dbir/#comments</comments>
		<pubDate>Tue, 03 May 2011 17:00:35 +0000</pubDate>
		<dc:creator>Jon Speer</dc:creator>
				<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[2011 Verizon Data Breach Investigations Report]]></category>
		<category><![CDATA[DBIR]]></category>
		<category><![CDATA[FIM]]></category>
		<category><![CDATA[Sony PlayStation Network]]></category>
		<category><![CDATA[Verizon]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=2368</guid>
		<description><![CDATA[It now appears that Sony PSN is framing up their breach as including the injection of a “communication tool” onto an application server via a vulnerability. They simply made a change to the server that opened up a backdoor. This exactly fits the trend reported in the Verizon Data Breach Investigations Report (DBIR) of hackers [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/it-security-data-protection/sony-psn-breach-fits-same-trend-seen-in-2011-verizon-dbir/feed/</wfw:commentRss>
		<slash:comments>2</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>True FIM—Tripwire FIM: Summary</title>
		<link>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-summary/</link>
		<comments>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-summary/#comments</comments>
		<pubDate>Tue, 06 Jul 2010 16:38:13 +0000</pubDate>
		<dc:creator>Ed Rarick</dc:creator>
				<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[File Integrity Management]]></category>
		<category><![CDATA[FIM]]></category>
		<category><![CDATA[PCI Compliance]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=1102</guid>
		<description><![CDATA[Summary Tripwire has the only true File Integrity Monitoring solution. All others do little more than just detect changes, whether the changes are good or bad—because they have no way of telling the difference. Tripwire FIM, with its unique ChangeIQ capabilities, provides multiple ways to determine low-risk change from high-risk change, and do so at [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-summary/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>True FIM—Tripwire FIM: Unauthorized vs. Undesired</title>
		<link>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-unauthorized-vs-undesired/</link>
		<comments>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-unauthorized-vs-undesired/#comments</comments>
		<pubDate>Thu, 01 Jul 2010 16:24:52 +0000</pubDate>
		<dc:creator>Ed Rarick</dc:creator>
				<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[File Integrity Monitoring]]></category>
		<category><![CDATA[FIM]]></category>
		<category><![CDATA[PCI]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=1077</guid>
		<description><![CDATA[Good News PCI DSS 11.5 requires merchants to “…alert on unauthorized modification of critical system, content or configuration files…”. That should be good news, right?  Alerting on unauthorized change requires more from a FIM than simply detecting change.  It requires the ability to analyze each detected change to determine if it is expected or unexpected.  [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-unauthorized-vs-undesired/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>True FIM—Tripwire FIM: Assessing Change and Maintaining a Desired State</title>
		<link>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-assessing-change-and-maintaining-a-desired-state/</link>
		<comments>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-assessing-change-and-maintaining-a-desired-state/#comments</comments>
		<pubDate>Thu, 24 Jun 2010 16:32:13 +0000</pubDate>
		<dc:creator>Ed Rarick</dc:creator>
				<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[File Integrity Monitoring]]></category>
		<category><![CDATA[FIM]]></category>
		<category><![CDATA[PCI]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=1073</guid>
		<description><![CDATA[Successful? Just because a change is proposed and scheduled does not mean that it was actually made or made correctly. Many changes are intended to make improvements, or to correct problems, so being able to confirm they have successfully been made is critical. Otherwise the improvements are not realized or the problems remain when you [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-assessing-change-and-maintaining-a-desired-state/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>True FIM—Tripwire FIM: Knowing What Changed</title>
		<link>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-knowing-what-changed/</link>
		<comments>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-knowing-what-changed/#comments</comments>
		<pubDate>Tue, 22 Jun 2010 14:00:41 +0000</pubDate>
		<dc:creator>Ed Rarick</dc:creator>
				<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[File Integrity Monitoring]]></category>
		<category><![CDATA[FIM]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=1071</guid>
		<description><![CDATA[What changed? Knowing only that a file has changed is of little use unless you know what about the file or what within the file has changed.  Each file has dozens of attributes that, if changed, could spell trouble.  Tripwire can capture any of those attributes providing essential information to help determine if the change [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-knowing-what-changed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>True FIM—Tripwire FIM: Monitoring Change</title>
		<link>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-monitoring-change/</link>
		<comments>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-monitoring-change/#comments</comments>
		<pubDate>Fri, 18 Jun 2010 14:00:29 +0000</pubDate>
		<dc:creator>Ed Rarick</dc:creator>
				<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[File Integrity Monitoring]]></category>
		<category><![CDATA[FIM]]></category>
		<category><![CDATA[PCI]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=1065</guid>
		<description><![CDATA[What to monitor The first step in FIM is controlling what is monitored.  There is no practical reason to monitor every file on every device or application all of the time. Tripwire provides a robust rules-based way to control which files are monitored for change and to what level they are monitored. Tripwire harvests more [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/it-security-data-protection/true-fim%e2%80%94tripwire-fim-monitoring-change/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FIM, You’ve Changed!</title>
		<link>http://www.tripwire.com/state-of-security/it-security-data-protection/fim-you%e2%80%99ve-changed/</link>
		<comments>http://www.tripwire.com/state-of-security/it-security-data-protection/fim-you%e2%80%99ve-changed/#comments</comments>
		<pubDate>Wed, 16 Jun 2010 16:54:47 +0000</pubDate>
		<dc:creator>Ed Rarick</dc:creator>
				<category><![CDATA[IT Security and Data Protection]]></category>
		<category><![CDATA[PCI]]></category>
		<category><![CDATA[Regulatory Compliance]]></category>
		<category><![CDATA[File Integrity Monitoring]]></category>
		<category><![CDATA[FIM]]></category>

		<guid isPermaLink="false">http://www.tripwire.com/blog/?p=1058</guid>
		<description><![CDATA[Once upon a time there was Change Audit. It was invented by Tripwire and it was good. Then along came VISA CISP (Cardholder Information Security Program) in June, 2001 and Change Audit had a makeover. It was renamed File Integrity Monitoring—or FIM for short—and referenced in requirements 10.5 and 11.5 of the CISP specification. So [...]]]></description>
		<wfw:commentRss>http://www.tripwire.com/state-of-security/it-security-data-protection/fim-you%e2%80%99ve-changed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

