<?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>Least privilege for services</title><link>http://blogs.technet.com/voy/archive/2007/03/21/least-privilege-for-services.aspx</link><description>This is part 2 of our series of posts on service hardening. "Need to have" and least privilege principle Executing with least privilege is a good practice of computer security. As with the "need to know" principle for information access, there should</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Least privilege for services</title><link>http://blogs.technet.com/voy/archive/2007/03/21/least-privilege-for-services.aspx#1327697</link><pubDate>Sat, 23 Jun 2007 01:08:14 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1327697</guid><dc:creator>Ashutosh B</dc:creator><description>&lt;p&gt;I set required privilege for my service to SeBackupPrivilege and then restarted the service. I dumped process's token using my own enumtoken tool and I see that along with SeBackupPrivilege, SeChangeNotifyPrivilege privilege is also present there in the token. Why didn't SCM remove my service's SeChangeNotifyPrivilege? Does system keep this by default for performance reason (for file system traversal) ?&lt;/p&gt;
</description></item><item><title>Windows 2008/vista service hardening</title><link>http://blogs.technet.com/voy/archive/2007/03/21/least-privilege-for-services.aspx#2834771</link><pubDate>Wed, 06 Feb 2008 03:35:02 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2834771</guid><dc:creator>The Security Wizard</dc:creator><description>&lt;p&gt;From the cold winter of Seattle, i&amp;amp;#39;ve managed to gather a small bunch of guides that explain the&lt;/p&gt;
</description></item></channel></rss>