<?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>"Using a Least-Privileged User Account" OR "Woohoo, I've been published on microsoft.com!"</title><link>http://blogs.technet.com/strawberryjamm/archive/2005/01/18/355654.aspx</link><description>An article I wrote, "Using a Least-Privileged User Account (LUA)", was published on TechNet as part of the monthly Microsoft Security Newsletter for January 2005. It takes a brief look at a few of the key issues around the principle of "least-privilege"</description><dc:language>en-CA</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: "Using a Least-Privileged User Account" OR "Woohoo, I've been published on microsoft.com!"</title><link>http://blogs.technet.com/strawberryjamm/archive/2005/01/18/355654.aspx#356336</link><pubDate>Wed, 19 Jan 2005 21:27:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:356336</guid><dc:creator>Will</dc:creator><description>My company has a software product that's running on kiosk-type equipment out in the field during its beta testing.  These are XP machines, and the program is run under a user who is a member of the Power user's group (we did that because of some of the system access it required).  We just found that one of the units had gotten infected with a virus that's working its way through the network of the location where the unit was installed.  We're not sure which virus it is, but I was surprised the amount of damage that could be done to an operating system by a power user.</description></item><item><title>re: "Using a Least-Privileged User Account" OR "Woohoo, I've been published on microsoft.com!"</title><link>http://blogs.technet.com/strawberryjamm/archive/2005/01/18/355654.aspx#360558</link><pubDate>Wed, 26 Jan 2005 01:50:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:360558</guid><dc:creator>Jenni Merrifield (strawberryJAMM)</dc:creator><description>Will:&lt;br&gt;&lt;br&gt;  You're absolutely right, the Power User group has far too many rights to be that useful from a security restriction point of view.  It's also childishly easy for bad code to elevate to Admin from an account with Power User rights.&lt;br&gt;&lt;br&gt;  Over here, we generally suggest that you forget Power User even exists because it just gives you a false sense of security.  Either use Admin or User, and if you don't need to be Admin but you do need more than a traditional User, start with User rights and then add just the permissions that the process actually needs.</description></item></channel></rss>