<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/MU" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Death of the DMZ &#8212; Redux</title>
	<link>http://blogs.windowsecurity.com/shinder/2008/07/23/death-of-the-dmz-redux/</link>
	<description>Dr. Tom Shinder's Security Space will cover all topics related to security on Microsoft networks. We will focus on Microsoft's security products and technologies, such as NTFS, access controls, permissions, network security, IPSec, EFS, BitLocker, System Hardening, Service Hardening, ISA Server, IAG, Forefront Security products, and more! This blog will focus on how the Microsoft admin can take a defender's approach to network security, rather than the more typical hacker's view - in this way we can dedicate our time to our core competency - defending our networks against attack.</description>
	<pubDate>Thu,  8 Jan 2009 12:53:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>

	<item>
		<title>by: Stefaan Pouseele</title>
		<link>http://blogs.windowsecurity.com/shinder/2008/07/23/death-of-the-dmz-redux/#comment-1900</link>
		<pubDate>Tue, 05 Aug 2008 12:48:20 +0000</pubDate>
		<guid>http://blogs.windowsecurity.com/shinder/2008/07/23/death-of-the-dmz-redux/#comment-1900</guid>
					<description>Hi Tom, 

I've listened to &quot;The fortified data center in your future: Build it now and they will come&quot; (http://www.microsoft.com/belux/technet/nl/chopsticks/default.aspx?id=449), given by Steve Riley in Brussels. I like very much his way of presenting that stuff because it forces you to think about what we are doing in the IT business. 

First of all I like to point out a typo in your blog: &quot;TCP protocol 50&quot;. IPSec in de IPv6 world uses IKE (UDP 500) en ESP (IP protocol 50). 

At our customers I don't see much difference between mobile and fixed corporate assets either. The most important point is that both should be well managed before you can trust them. 

Now, the point of outbound access control is a little bit nasty. From my experience it is very hard to do it well, unless you are willing to invest a lot of time and money, or you can work with a white list concept. In practice, I don't see neither of them at our customers. I mean that a knowledgeable user can in most cases easily circumvent the implemented controls. 

Moreover, when the mobile corporate asset is outside the corporate building and not connected through the VPN, the user can inherently access the Internet freely. So, in this case there is no outbound access control possible at all. Maybe we should solve that problem in a complete other way and make the user legally responsible for his actions, even if it is with the help of a corporate asset. 

Kindly,
Stefaan</description>
		<content:encoded><![CDATA[<p>Hi Tom, </p>
<p>I&#8217;ve listened to &#8220;The fortified data center in your future: Build it now and they will come&#8221; (http://www.microsoft.com/belux/technet/nl/chopsticks/default.aspx?id=449), given by Steve Riley in Brussels. I like very much his way of presenting that stuff because it forces you to think about what we are doing in the IT business. </p>
<p>First of all I like to point out a typo in your blog: &#8220;TCP protocol 50&#8243;. IPSec in de IPv6 world uses IKE (UDP 500) en ESP (IP protocol 50). </p>
<p>At our customers I don&#8217;t see much difference between mobile and fixed corporate assets either. The most important point is that both should be well managed before you can trust them. </p>
<p>Now, the point of outbound access control is a little bit nasty. From my experience it is very hard to do it well, unless you are willing to invest a lot of time and money, or you can work with a white list concept. In practice, I don&#8217;t see neither of them at our customers. I mean that a knowledgeable user can in most cases easily circumvent the implemented controls. </p>
<p>Moreover, when the mobile corporate asset is outside the corporate building and not connected through the VPN, the user can inherently access the Internet freely. So, in this case there is no outbound access control possible at all. Maybe we should solve that problem in a complete other way and make the user legally responsible for his actions, even if it is with the help of a corporate asset. </p>
<p>Kindly,<br />
Stefaan
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
