<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"><channel><title>VPN Is Dead - here's your new killer app</title><link>http://blogs.technet.com/b/keithcombs/archive/2006/07/08/440752.aspx</link><description>One of my favorite features of all time is RPC Over HTTP. Most of you are familiar with it because it allows Outlook to encapsulate RPC calls inside a HTTP packet or frame. That frame must of course travel across the internet to your &amp;ldquo;Front-End&amp;rdquo;</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>HTTP over HTTP! (No joke!)</title><link>http://blogs.technet.com/b/keithcombs/archive/2006/07/08/440752.aspx#444363</link><pubDate>Tue, 01 Aug 2006 21:03:18 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:444363</guid><dc:creator>(e)Mail Insecurity</dc:creator><description>&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=444363" width="1" height="1"&gt;</description></item><item><title>re: VPN Is Dead - here's your new killer app</title><link>http://blogs.technet.com/b/keithcombs/archive/2006/07/08/440752.aspx#443540</link><pubDate>Wed, 26 Jul 2006 22:48:40 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:443540</guid><dc:creator>spatie25</dc:creator><description>I am quite concerned about the way things are moving with remote communication in all its aspects. &amp;nbsp;It shows over the last few years that more and more vendors are adopting the approach to encapsulating all sorts of protocols in HTTP. &amp;nbsp;Of course this is a very tempting solution, as HTTP in many cases is about the only protocol that is allowed to travel across a company’s firewall.&lt;br&gt;&lt;br&gt;I remember a presentation on security, hosted by MS employees, were it was stated bluntly : don’t use VPN, it is a hole in your firewall, which is quite fair to me.&lt;br&gt;&lt;br&gt;Now, I wonder what the advice would be from the MS security experts on protocols that are ported over HTTP. &amp;nbsp;I try to understand what the risks could be, or why I should be rest assured that this is under control. &amp;nbsp;The way I understand it is that there is no defence against malicious code, encapsulated in an HTTP protocol other than a very performant firewall with state of the art statefull inspection and even then, I am told, it still is risky business. &amp;nbsp; On the why’s, I get various explanations that do not always comply with one another. &lt;br&gt;&lt;br&gt;Now, I understand that this IPsec solution, offered by ISA2006, is pretty nice in terms of setting up a secure P2P connection without the hassle of a VPN client. &amp;nbsp;But this is not the discussion. &amp;nbsp;What to think about an employee, trying to access the OWA servers from a public computer : no VPN, no IPsec, just a certificate and a password. &amp;nbsp;Once compromised, you can only but imagine what could go wrong. &amp;nbsp;And in this case we are ‘talking’ HTTP, plain simple (for the firewall that is). &amp;nbsp;&lt;br&gt;What if that employee tries to do RDP over HTTP or whatever other traffic that could be routed over HTTP. &amp;nbsp;I am making to much fuzz out of nothing, or should we be careful in how we ‘adopt’ these new features?&lt;br&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=443540" width="1" height="1"&gt;</description></item><item><title>Interesting Finds: July 8, 2006</title><link>http://blogs.technet.com/b/keithcombs/archive/2006/07/08/440752.aspx#440806</link><pubDate>Sat, 08 Jul 2006 18:32:19 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:440806</guid><dc:creator>Jason Haley</dc:creator><description>&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=440806" width="1" height="1"&gt;</description></item><item><title>re: VPN Is Dead - here's your new killer app</title><link>http://blogs.technet.com/b/keithcombs/archive/2006/07/08/440752.aspx#440792</link><pubDate>Sat, 08 Jul 2006 14:28:05 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:440792</guid><dc:creator>Hugo Batista</dc:creator><description>Hi Keith,&lt;br&gt;&lt;br&gt;I agree with you that time is money and productivity can be increased using a solution like this. I would use it for some internal apps i would like to expose, but definitely not to some LoB apps which could expose my internal secrets. &lt;br&gt;&lt;br&gt;IPSEC took its time to be trusted by the community, and even if there is easier ways to get connected, those ways will have to proof its credibility before being considered a replacement for it. That's why i don't think this would be a killer app for VPN..&lt;br&gt;&lt;br&gt;Although, this is a very interesting improvement and solution to expose some non-critical apps, like expense reporting, project reporting, knowledge bases, etc...&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=440792" width="1" height="1"&gt;</description></item><item><title>VPN Is Dead - here's your new killer app (Artigo muito interessante)</title><link>http://blogs.technet.com/b/keithcombs/archive/2006/07/08/440752.aspx#440764</link><pubDate>Sat, 08 Jul 2006 11:38:01 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:440764</guid><dc:creator>Chaves</dc:creator><description>&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=440764" width="1" height="1"&gt;</description></item></channel></rss>