 




<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Will R2&#8242;s DirectAccess leave you vulnerable?</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/windows-server/will-r2s-directaccess-leave-you-vulnerable/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/windows-server/will-r2s-directaccess-leave-you-vulnerable/</link>
	<description>A SearchWindowsServer.com blog</description>
	<lastBuildDate>Thu, 11 Oct 2012 18:59:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Cmoorhead2</title>
		<link>http://itknowledgeexchange.techtarget.com/windows-server/will-r2s-directaccess-leave-you-vulnerable/#comment-3</link>
		<dc:creator>Cmoorhead2</dc:creator>
		<pubDate>Thu, 09 Jul 2009 15:24:59 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/windows-server/?p=128#comment-3</guid>
		<description><![CDATA[Of course security is always a concern, it never goes away.  And I am looking forward to evaluating Direct Access.  In discussions with Microsoft, I learned that Direct Access knows about the resources back at the office because the names and IP addresses of those resources are pushed down to the connecting client and are stored in memory on the client computer for the length of the connection session.  This information is unencrypted!  imagine some malware created to examine that information and learn about your internal network!  When asked, Microsoft&#039;s response was a long pause followed by a reminder that it was still in beta.]]></description>
		<content:encoded><![CDATA[<p>Of course security is always a concern, it never goes away.  And I am looking forward to evaluating Direct Access.  In discussions with Microsoft, I learned that Direct Access knows about the resources back at the office because the names and IP addresses of those resources are pushed down to the connecting client and are stored in memory on the client computer for the length of the connection session.  This information is unencrypted!  imagine some malware created to examine that information and learn about your internal network!  When asked, Microsoft&#8217;s response was a long pause followed by a reminder that it was still in beta.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
