<?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/"
		>
<channel>
	<title>Comments on: Memory Protection is an Important Component of Application Whitelisting Solutions</title>
	<atom:link href="http://www.coretraceblogs.com/2009-10/memory-protection-is-an-important-component-of-application-whitelisting-solutions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.coretraceblogs.com/2009-10/memory-protection-is-an-important-component-of-application-whitelisting-solutions/</link>
	<description>The Application Whitelisting and Security Weblog</description>
	<lastBuildDate>Wed, 01 Feb 2012 15:10:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Microsoft&#8217;s Windows 7 AppLocker, a watershed moment for application whitelisting</title>
		<link>http://www.coretraceblogs.com/2009-10/memory-protection-is-an-important-component-of-application-whitelisting-solutions/#comment-287</link>
		<dc:creator>Microsoft&#8217;s Windows 7 AppLocker, a watershed moment for application whitelisting</dc:creator>
		<pubDate>Tue, 10 Nov 2009 16:52:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.coretraceblogs.com/?p=656#comment-287</guid>
		<description>[...] whitelisting should handle memory based attacks &#8211; I recently posted on the importance of preventing memory based attacks. The essence of this is that a simple whitelist of approved applications isn&#8217;t enough to stop [...]</description>
		<content:encoded><![CDATA[<p>[...] whitelisting should handle memory based attacks &#8211; I recently posted on the importance of preventing memory based attacks. The essence of this is that a simple whitelist of approved applications isn&#8217;t enough to stop [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

