<?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: Windows 7&#8242;s security &#8216;time bomb&#8217;</title>
	<atom:link href="http://lastwatchdog.com/windows-7s-security-time-bomb/feed/" rel="self" type="application/rss+xml" />
	<link>http://lastwatchdog.com/windows-7s-security-time-bomb/</link>
	<description>on Internet security by Byron Acohido</description>
	<lastBuildDate>Fri, 03 Feb 2012 18:38:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Johan Vansevenant</title>
		<link>http://lastwatchdog.com/windows-7s-security-time-bomb/#comment-871</link>
		<dc:creator>Johan Vansevenant</dc:creator>
		<pubDate>Sun, 01 Nov 2009 10:36:13 +0000</pubDate>
		<guid isPermaLink="false">http://lastwatchdog.com/?p=3314#comment-871</guid>
		<description>Russ Cooper is absolutely right but there is a problem. The first account (admin in aproval mode) in Vista/W7 is VISIBLE. As a systembuilder/retailer i know most users - even if they are the only user  - they won&#039;t create a second user that&#039;s defaults as a standard user. It&#039;s all coming down to user-skill i think.</description>
		<content:encoded><![CDATA[<p>Russ Cooper is absolutely right but there is a problem. The first account (admin in aproval mode) in Vista/W7 is VISIBLE. As a systembuilder/retailer i know most users &#8211; even if they are the only user  &#8211; they won&#8217;t create a second user that&#8217;s defaults as a standard user. It&#8217;s all coming down to user-skill i think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Byron Acohido</title>
		<link>http://lastwatchdog.com/windows-7s-security-time-bomb/#comment-869</link>
		<dc:creator>Byron Acohido</dc:creator>
		<pubDate>Fri, 30 Oct 2009 15:35:24 +0000</pubDate>
		<guid isPermaLink="false">http://lastwatchdog.com/?p=3314#comment-869</guid>
		<description>Russ:
Thanks for laying out your strong stance. Realistically, though, the horse is out of the barn, don&#039;t you think? Can you -- or anyone -- conceive of a plausible scenario by which Microsoft would reverse its rationale defending the current Win7 UAC default setting and move to configure the world&#039;s dominant client OS along the lines you suggest?</description>
		<content:encoded><![CDATA[<p>Russ:<br />
Thanks for laying out your strong stance. Realistically, though, the horse is out of the barn, don&#8217;t you think? Can you &#8212; or anyone &#8212; conceive of a plausible scenario by which Microsoft would reverse its rationale defending the current Win7 UAC default setting and move to configure the world&#8217;s dominant client OS along the lines you suggest?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ Cooper</title>
		<link>http://lastwatchdog.com/windows-7s-security-time-bomb/#comment-868</link>
		<dc:creator>Russ Cooper</dc:creator>
		<pubDate>Fri, 30 Oct 2009 10:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://lastwatchdog.com/?p=3314#comment-868</guid>
		<description>Thinking that users need not be involved in security, or that somehow itâ€™s not their responsibility, is where we continue to fail in securing systems. Of course they have a role.

Where Byron, and others, get it wrong is in recommending that consumers set their UAC level to high. Instead, consumers should be recommended (and the installation should ensure) that they create two accounts. The first is their Administrator account, and the second is their User account. The Administrator account environment should not allow tools like IE, Media Player, Windows Live, etc. The environment should not be customizable (i.e. you cannot have wallpaper, change the colors, or otherwise personalize it. IOWs make it so it is totally undesirable to use the Administrator account for day-to-day computer use.

In this way you may end up with far more consumers using UACâ€™s default settings as Standard User rather than Administrator. As such, the issue described by Leo becomes far less an issue. If I canâ€™t access my email while logged on as Administrator, I canâ€™t double-click on the criminal attachment or linkâ€¦can I.</description>
		<content:encoded><![CDATA[<p>Thinking that users need not be involved in security, or that somehow itâ€™s not their responsibility, is where we continue to fail in securing systems. Of course they have a role.</p>
<p>Where Byron, and others, get it wrong is in recommending that consumers set their UAC level to high. Instead, consumers should be recommended (and the installation should ensure) that they create two accounts. The first is their Administrator account, and the second is their User account. The Administrator account environment should not allow tools like IE, Media Player, Windows Live, etc. The environment should not be customizable (i.e. you cannot have wallpaper, change the colors, or otherwise personalize it. IOWs make it so it is totally undesirable to use the Administrator account for day-to-day computer use.</p>
<p>In this way you may end up with far more consumers using UACâ€™s default settings as Standard User rather than Administrator. As such, the issue described by Leo becomes far less an issue. If I canâ€™t access my email while logged on as Administrator, I canâ€™t double-click on the criminal attachment or linkâ€¦can I.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Sutton, Zscaler</title>
		<link>http://lastwatchdog.com/windows-7s-security-time-bomb/#comment-858</link>
		<dc:creator>Michael Sutton, Zscaler</dc:creator>
		<pubDate>Tue, 27 Oct 2009 03:29:43 +0000</pubDate>
		<guid isPermaLink="false">http://lastwatchdog.com/?p=3314#comment-858</guid>
		<description>Leaving security decisions to end users is never a solution, it simply â€˜passes the buckâ€™ in a effort to transfer the responsibility for security from vendor to consumer. End users are not security experts and cannot be expected to understand when they are at risk. 

Consumer level security functionality needs to be as transparent as possible. If it isnâ€™t, it will be disabled. Microsoft has realized that placing security in the hands of end users with Windows Vista was a failed approach. While adding more granular settings for UAC in Windows 7 and â€˜auto-elevateâ€™ functionality may limit this scenario, it does not change the overall approach.   

UAC is not a solution to prevent malware, it is merely a band-aid to encourage software developers to adopt secure programming practices. Technical solutions such as DEP and ASLR will do far more to prevent the spread of malicious content. Fortunately, Microsoft continues to pursue such technical approaches which remain transparent to end users as they should.</description>
		<content:encoded><![CDATA[<p>Leaving security decisions to end users is never a solution, it simply â€˜passes the buckâ€™ in a effort to transfer the responsibility for security from vendor to consumer. End users are not security experts and cannot be expected to understand when they are at risk. </p>
<p>Consumer level security functionality needs to be as transparent as possible. If it isnâ€™t, it will be disabled. Microsoft has realized that placing security in the hands of end users with Windows Vista was a failed approach. While adding more granular settings for UAC in Windows 7 and â€˜auto-elevateâ€™ functionality may limit this scenario, it does not change the overall approach.   </p>
<p>UAC is not a solution to prevent malware, it is merely a band-aid to encourage software developers to adopt secure programming practices. Technical solutions such as DEP and ASLR will do far more to prevent the spread of malicious content. Fortunately, Microsoft continues to pursue such technical approaches which remain transparent to end users as they should.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Kaminsky, doxpara.com</title>
		<link>http://lastwatchdog.com/windows-7s-security-time-bomb/#comment-857</link>
		<dc:creator>Dan Kaminsky, doxpara.com</dc:creator>
		<pubDate>Mon, 26 Oct 2009 23:02:56 +0000</pubDate>
		<guid isPermaLink="false">http://lastwatchdog.com/?p=3314#comment-857</guid>
		<description>UAC&#039;s goal was to finally wean Windows software developers off of requiring administrative access for every day applications.  For that goal, it was very effective....and whatever issues happen to be found, have no impact on whether well-behaved Windows applications are written one way or another.  UAC makes well behaved applications require fewer privileges to operate.</description>
		<content:encoded><![CDATA[<p>UAC&#8217;s goal was to finally wean Windows software developers off of requiring administrative access for every day applications.  For that goal, it was very effective&#8230;.and whatever issues happen to be found, have no impact on whether well-behaved Windows applications are written one way or another.  UAC makes well behaved applications require fewer privileges to operate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger Thompson, AVG</title>
		<link>http://lastwatchdog.com/windows-7s-security-time-bomb/#comment-856</link>
		<dc:creator>Roger Thompson, AVG</dc:creator>
		<pubDate>Mon, 26 Oct 2009 20:49:46 +0000</pubDate>
		<guid isPermaLink="false">http://lastwatchdog.com/?p=3314#comment-856</guid>
		<description>When weâ€™re dealing with the most widely used operating system in the world, hackers are going to show up in droves to infect and cause problems. Thatâ€™s why Iâ€™ve always advocated that security needs to happen in a layered fashion. If you only have one layer such as Microsoftâ€™s own security suite Essentials, there are holes that wonâ€™t be covered. If you add layers to that, then youâ€™re going to have protection and the bad guys wonâ€™t have an open door policy to hack your system. In depth defense is what is needed because the OS, whether itâ€™s Windows 7 or Vista or whateverâ€™s next, is always going to be the target and the bad guys will find a way through.</description>
		<content:encoded><![CDATA[<p>When weâ€™re dealing with the most widely used operating system in the world, hackers are going to show up in droves to infect and cause problems. Thatâ€™s why Iâ€™ve always advocated that security needs to happen in a layered fashion. If you only have one layer such as Microsoftâ€™s own security suite Essentials, there are holes that wonâ€™t be covered. If you add layers to that, then youâ€™re going to have protection and the bad guys wonâ€™t have an open door policy to hack your system. In depth defense is what is needed because the OS, whether itâ€™s Windows 7 or Vista or whateverâ€™s next, is always going to be the target and the bad guys will find a way through.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Byron Acohido</title>
		<link>http://lastwatchdog.com/windows-7s-security-time-bomb/#comment-855</link>
		<dc:creator>Byron Acohido</dc:creator>
		<pubDate>Mon, 26 Oct 2009 20:16:55 +0000</pubDate>
		<guid isPermaLink="false">http://lastwatchdog.com/?p=3314#comment-855</guid>
		<description>Patrick:
I don&#039;t believe it is. Microsoft did fix a couple of UAC bugs, including that one, I believe, in response to feedback from the security community. This issue has to do with the auto-elevate function itself. Instead of UAC on vs. off, as per the Vista mode, Windows 7 has a medium and medium-high setting, that automatically elevates some functions to administrator level access. Leo&#039;s exploit shows how auto-elevate can be accessed an injection attack. That&#039;s my non-technical understanding. Hopefully, Leo himself will comment here.
Thanks,
Byron</description>
		<content:encoded><![CDATA[<p>Patrick:<br />
I don&#8217;t believe it is. Microsoft did fix a couple of UAC bugs, including that one, I believe, in response to feedback from the security community. This issue has to do with the auto-elevate function itself. Instead of UAC on vs. off, as per the Vista mode, Windows 7 has a medium and medium-high setting, that automatically elevates some functions to administrator level access. Leo&#8217;s exploit shows how auto-elevate can be accessed an injection attack. That&#8217;s my non-technical understanding. Hopefully, Leo himself will comment here.<br />
Thanks,<br />
Byron</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick Dickey</title>
		<link>http://lastwatchdog.com/windows-7s-security-time-bomb/#comment-854</link>
		<dc:creator>Patrick Dickey</dc:creator>
		<pubDate>Mon, 26 Oct 2009 19:45:04 +0000</pubDate>
		<guid isPermaLink="false">http://lastwatchdog.com/?p=3314#comment-854</guid>
		<description>Is this bug the one that will lower (or turn off) UAC without prompting the user at all?  The change level setting bug, I mean?

If so, then I would ask how hard it would be to make changing the level into an item that requires you to be prompted?  The OK button already has a UAC shield, so it obviously falls into the UAC realm.  It shouldn&#039;t be an issue to require that prompt regardless of whether I do it, or a program does it.

Have a great day:)
Patrick.</description>
		<content:encoded><![CDATA[<p>Is this bug the one that will lower (or turn off) UAC without prompting the user at all?  The change level setting bug, I mean?</p>
<p>If so, then I would ask how hard it would be to make changing the level into an item that requires you to be prompted?  The OK button already has a UAC shield, so it obviously falls into the UAC realm.  It shouldn&#8217;t be an issue to require that prompt regardless of whether I do it, or a program does it.</p>
<p>Have a great day:)<br />
Patrick.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

