<?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 NoAH Blog &#187; microsoft</title>
	<atom:link href="http://blogs.fp6-noah.org/noah/tag/microsoft/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.fp6-noah.org/noah</link>
	<description>an ark of honeypot knowledge...</description>
	<lastBuildDate>Tue, 07 Jul 2009 14:35:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>WIT: Write Integrity Testing</title>
		<link>http://blogs.fp6-noah.org/noah/wit-write-integrity-checking/</link>
		<comments>http://blogs.fp6-noah.org/noah/wit-write-integrity-checking/#comments</comments>
		<pubDate>Wed, 23 Apr 2008 14:19:43 +0000</pubDate>
		<dc:creator>Vrije Universiteit, Amsterdam</dc:creator>
				<category><![CDATA[papers]]></category>
		<category><![CDATA[cool]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[paper]]></category>

		<guid isPermaLink="false">http://blogs.fp6-noah.org/noah/wit-write-integrity-checking/</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p align="justify">Cool stuff from the people at <a href="http://research.microsoft.com/cambridge/">MSR Cambridge</a>.  Their latest <a href="http://research.microsoft.com/~manuelc/MS/WIT-Oakland.pdf">Oakland paper on write integrity checking</a> provides a nice solution for various memory exploits that may otherwise lead to a machine being compromised. Their method uses point-to-analysis at compile time to generate the control flow graph as well as the set of objects that can be written by each instruction. It then instruments these instructions to make sure that they do not write into with objects that are not in the set (and also to ensure that indirect control flow transfers are valid). Runtime overhead is very small. I guess the main catch is that you have to sit on the source code &#8211; which is not the case for anyone other than Microsoft. Nevertheless, very good work.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.fp6-noah.org/noah/wit-write-integrity-checking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

