<?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: Integrated Application Security Logging?</title>
	<atom:link href="http://www.thummy.com/roodee/2007/06/14/integrated-application-security-logging/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thummy.com/roodee/2007/06/14/integrated-application-security-logging/</link>
	<description>My Wrong Opinions..</description>
	<lastBuildDate>Thu, 08 Jan 2009 19:47:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: roodee</title>
		<link>http://www.thummy.com/roodee/2007/06/14/integrated-application-security-logging/comment-page-1/#comment-2256</link>
		<dc:creator>roodee</dc:creator>
		<pubDate>Thu, 14 Jun 2007 21:04:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.thummy.com/roodee/2007/06/14/integrated-application-security-logging/#comment-2256</guid>
		<description>Yes, I agree. I wanted to ensure that there was no confusion about the shortcomings and difficulty of building security instrumentation into applications for the purpose of detection and/or prevention. Sure it can be done and works perhaps in many cases any yet there is this uneasiness with that solution because it is so tightly coupled to the application.</description>
		<content:encoded><![CDATA[<p>Yes, I agree. I wanted to ensure that there was no confusion about the shortcomings and difficulty of building security instrumentation into applications for the purpose of detection and/or prevention. Sure it can be done and works perhaps in many cases any yet there is this uneasiness with that solution because it is so tightly coupled to the application.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Bejtlich</title>
		<link>http://www.thummy.com/roodee/2007/06/14/integrated-application-security-logging/comment-page-1/#comment-2255</link>
		<dc:creator>Richard Bejtlich</dc:creator>
		<pubDate>Thu, 14 Jun 2007 20:45:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.thummy.com/roodee/2007/06/14/integrated-application-security-logging/#comment-2255</guid>
		<description>Hello,

I&#039;m glad you liked my post.  Did you read this part?

&lt;em&gt;So why isn&#039;t security application instrumentation sufficient? The problem is one should not place one&#039;s trust entirely in the hands of the target. One of Marcus Ranum&#039;s best pieces of wisdom for me was the distinction between &quot;trusted&quot; and &quot;trustworthy.&quot; Just because you trust an application doesn&#039;t make it worthy of that trust. Just because you have no alternative but to &quot;trust&quot; an application doesn&#039;t make it trustworthy either. Trustworthy systems behave in the manner you expect and can be validated by systems outside of the influence of the target.&lt;/em&gt;

For most of my career my mechanism for determining whether systems are trustworthy has been network sensors. That&#039;s why they sit at the top of my TaoSecurity Enterprise Trust Pyramid. In a host- and application-centric world I might consider a second system with one-way direct memory access to a target to be the most trusted source of information on the target, followed by a host reporting its own memory, then other mechanisms including application state, logs, etc.

You can&#039;t entirely trust the target because it can be compromised and told to lie. Of course all elements of my trust pyramid (or any trust pyramid) can be compromised but the degree of difficulty (should) increase as isolation from the target is achieved.</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>I&#8217;m glad you liked my post.  Did you read this part?</p>
<p><em>So why isn&#8217;t security application instrumentation sufficient? The problem is one should not place one&#8217;s trust entirely in the hands of the target. One of Marcus Ranum&#8217;s best pieces of wisdom for me was the distinction between &#8220;trusted&#8221; and &#8220;trustworthy.&#8221; Just because you trust an application doesn&#8217;t make it worthy of that trust. Just because you have no alternative but to &#8220;trust&#8221; an application doesn&#8217;t make it trustworthy either. Trustworthy systems behave in the manner you expect and can be validated by systems outside of the influence of the target.</em></p>
<p>For most of my career my mechanism for determining whether systems are trustworthy has been network sensors. That&#8217;s why they sit at the top of my TaoSecurity Enterprise Trust Pyramid. In a host- and application-centric world I might consider a second system with one-way direct memory access to a target to be the most trusted source of information on the target, followed by a host reporting its own memory, then other mechanisms including application state, logs, etc.</p>
<p>You can&#8217;t entirely trust the target because it can be compromised and told to lie. Of course all elements of my trust pyramid (or any trust pyramid) can be compromised but the degree of difficulty (should) increase as isolation from the target is achieved.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

