<?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/"><channel><title>Microsoft Security Initiatives in SP1 and SP2 - nothing but a complex toy?</title><link>http://blogs.technet.com/b/industry_insiders/archive/2005/06/14/406324.aspx</link><description>Microsoft Security Initiatives in SP1 and SP2 - nothing but a complex toy? By Dennis Lundtoft Thomsen 
 I recently read Kevin Day's book " Inside a Security Mind " - not because I pretend or intend to be a security guru but because I'm aware of the fact</description><dc:language>en-GB</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Microsoft Security Initiatives in SP1 and SP2 - nothing but a complex toy?</title><link>http://blogs.technet.com/b/industry_insiders/archive/2005/06/14/406324.aspx#406842</link><pubDate>Fri, 24 Jun 2005 17:49:53 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:406842</guid><dc:creator>Richard M. Conlan</dc:creator><description>I am a graduate student in Northeastern University CC&amp;amp;IS and am interested in HCISEC issues. HCISEC concerns the design and implementation of UI elements such that a general user can make informed security decisions.&lt;br&gt;&lt;br&gt;The outbound firewall issue is one of the examples I tend to use regarding the need for HCISEC research. WHY do users just click Yes? For the personal firewalls I've used (ZoneAlarm and Sygate Personal Firewall) the reason is pretty clear:&lt;br&gt;&lt;br&gt;1) The typical user cannot tell from the information presented whether it is safe to allow the outbound connection because the data presented to enable the choice is confusing/opaque. &lt;br&gt;&lt;br&gt;How is a typical user supposed to know what to say when they get something like &amp;quot;Would you like to allow WINWORD.EXE to make an outbound connection?&amp;quot;&lt;br&gt;&lt;br&gt;2) The typical user does not necessarily understand the security ramifications of allowing an outbound connection. Popular understanding of security risks tend to focus around hackers, viruses, and the like trying to get IN.&lt;br&gt;&lt;br&gt;Extended the above example...what harm could allowing WINWORD.EXE an outbound connection possibly do?&lt;br&gt;&lt;br&gt;3) If the user does say NO and things break it tends to take a series of rather complex steps to reverse the decision. This gives the user an incentive to say YES just to avoid the hassle of trying to fix it.&lt;br&gt;&lt;br&gt;To a degree these are user education issues, but to an even greater degree they are a question of how well the technology presents the user with security options and facilitates the users making informed decisions amongst those options.&lt;br&gt;&lt;br&gt;SSL suffers from all of the same problems as the personal firewalls. So do MOST things that are content to prompt the user on the assumption that the user will always make an informed and appropriate decision.&lt;br&gt;&lt;br&gt;To reuse the quote from Day's book:&lt;br&gt;&lt;br&gt;“.. a security device, no matter how expensive or complex, is nothing more than a toy if it does not function within a greater security framework.”&lt;br&gt;&lt;br&gt;MANY MANY security devices are reduced to toys because they do not function within the greater security framework that is the user's security experience.&lt;br&gt;&lt;br&gt;Feel free to contact me with any thoughts on these issues.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=406842" width="1" height="1"&gt;</description></item><item><title>re: Microsoft Security Initiatives in SP1 and SP2 - nothing but a complex toy?</title><link>http://blogs.technet.com/b/industry_insiders/archive/2005/06/14/406324.aspx#406576</link><pubDate>Mon, 20 Jun 2005 17:15:04 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:406576</guid><dc:creator>Dennis Lundtoft Thomsen</dc:creator><description>Hi Susan,&lt;br&gt;&lt;br&gt;Sorry for the late answer, here it goes -&lt;br&gt; &lt;br&gt;According to my references / testing it is enabled by default during a clean Windows Server 2003 SP1 installation (Although PSSU isn't invoked after an upgrade). But as soon as you press &amp;quot;Finish&amp;quot; in the PSSU Wizard the Firewall is disabled. It is a big step forward but IMHO it should still be enabled after this point and then by using SCW you would open only the necessary ports for your specific server role(s). I do agree that the way outbound filtering mechanisms are handled today in most Personal Firewalls isn’t perfect as non-IT users are inclined to use the &amp;quot;sure I want to go outbound&amp;quot; button – so we need to find a better way to handle this (E.g. open outgoing ports as part of a “SCW” workstation role tool and as part of MSI installation packages for each application).&lt;br&gt;&lt;br&gt;Btw. keep up the good work with your SBS blog ;-)&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=406576" width="1" height="1"&gt;</description></item><item><title>re: Microsoft Security Initiatives in SP1 and SP2 - nothing but a complex toy?</title><link>http://blogs.technet.com/b/industry_insiders/archive/2005/06/14/406324.aspx#406393</link><pubDate>Wed, 15 Jun 2005 09:06:50 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:406393</guid><dc:creator>Susan</dc:creator><description>Are you sure about the statement &amp;quot;Furthermore, I think it’s disappointing that Microsoft didn’t have the nerve to enable the firewall by default in a slipstreamed Windows Server 2003 SP1 installation&amp;quot; as it is enabled until our SBS boxes go out and get patches as least.  I thought this was true for normal server as well?  As far as not allowing outbound filtering of connections, that's discussed in the TechNet Radio and the found that users would just click &amp;quot;sure I want that go outbound&amp;quot; and it served no purpose.&lt;br&gt;&lt;br&gt;SBS 2003 doesn't need it because we're pretty tweaked as it is, but I do have to &amp;lt;sigh&amp;gt; sometimes when someone says &amp;quot;oh I'm secure I have a firewall and I don't need them inside the network.&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=406393" width="1" height="1"&gt;</description></item><item><title>Microsoft Security Initiatives in SP1 and SP2 - nothing but a complex toy?</title><link>http://blogs.technet.com/b/industry_insiders/archive/2005/06/14/406324.aspx#406362</link><pubDate>Tue, 14 Jun 2005 23:04:12 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:406362</guid><dc:creator>msgoodies</dc:creator><description>I've written an essay on the security initiatives in SP1 and SP2 for the Industry insiders forum and it can be found here ...&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=406362" width="1" height="1"&gt;</description></item><item><title>Microsoft Security Initiatives in SP1 and SP2 - nothing but a complex toy?</title><link>http://blogs.technet.com/b/industry_insiders/archive/2005/06/14/406324.aspx#406328</link><pubDate>Tue, 14 Jun 2005 13:04:34 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:406328</guid><dc:creator>The Industry Insiders</dc:creator><description>Dennis has written an article which examines the role of Service Pack 1 for Windows Server 2003 and Service...&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=406328" width="1" height="1"&gt;</description></item></channel></rss>