<?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>Account lockout tools....</title><link>http://blogs.technet.com/brucecowper/archive/2004/12/29/343896.aspx</link><description>One of the challenges I always came up against, both as a security consultant and as an network administrator was account lockouts... I kept coming up against this in a number of ways: - Accounts being locked out because of attempts to brute force the</description><dc:language>en-CA</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Account lockout tools....</title><link>http://blogs.technet.com/brucecowper/archive/2004/12/29/343896.aspx#343911</link><pubDate>Thu, 30 Dec 2004 00:22:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:343911</guid><dc:creator>Gregor Suttie</dc:creator><description>Many Thanks for this as I was getting locked out a lot at work and can now use these links to find out why I was being locked out.&lt;br&gt;&lt;br&gt;Cheers&lt;br&gt;Gregor</description></item><item><title>re: Account lockout tools....</title><link>http://blogs.technet.com/brucecowper/archive/2004/12/29/343896.aspx#343942</link><pubDate>Thu, 30 Dec 2004 01:15:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:343942</guid><dc:creator>Lurker 1138</dc:creator><description>How about a self-serve website for users to recover forgotten passwords, change passwords, and update other info in AD like phone number? </description></item><item><title>re: Account lockout tools....</title><link>http://blogs.technet.com/brucecowper/archive/2004/12/29/343896.aspx#343995</link><pubDate>Thu, 30 Dec 2004 02:32:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:343995</guid><dc:creator>Drew</dc:creator><description>I'll disagree with you, Bruce.  IMHO password lockout is evil.  It's an excuse to forego the use of strong passwords (or &amp;quot;passphrases&amp;quot;) or smartcards and it creates the possibility for a nasty DOS attack.  Even if you use IPSEC to limit logons to come from only your forest's machines you have the possibility of malicious disgruntled employees DOSing one another.  Auditing can catch the culprit after the DOS has happened, but that is more administrative overhead and it still means that some innocent was locked out and lost productivity.  Even auditing might not help if the attack were spread virally to lots of machines.&lt;br&gt;We have an account lockout policy on ntdev (the domain I'm in at work) and I also know that if I tried to lock someone out (for 30 minutes according to what rsop tells me now, but I could attack again 30 mins later) someone would porbably figure out that I did it and that would be the end of me at Microsoft.  Then again, there are a few shared test accounts I know of in ntdev and we have some debuggers in our lab that are joined to the domain, so . . .  I doubt I'd get away with it now that you know my evil plans.  Drat!</description></item><item><title>Account Lockout Tools</title><link>http://blogs.technet.com/brucecowper/archive/2004/12/29/343896.aspx#344024</link><pubDate>Thu, 30 Dec 2004 04:15:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:344024</guid><dc:creator>Kent J. Chen's Weblog</dc:creator><description /></item><item><title>Account Lockout Tools</title><link>http://blogs.technet.com/brucecowper/archive/2004/12/29/343896.aspx#344026</link><pubDate>Thu, 30 Dec 2004 04:16:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:344026</guid><dc:creator>Kent J. Chen's Weblog</dc:creator><description /></item></channel></rss>