Solved

AD Account Lockout duration

Posted on 2012-03-09
4
1,019 Views
Last Modified: 2012-08-13
Hello, I have a quick question one of you folks may be able to answer.  

I need to find out what the current ISO, etc industry standard AD lockout duration recommendations are.  Ive found that NIST and the NSA recommend 15 minutes and SANS recommends 240 minutes but I would like to have another source (hopefully in black and white terms) so that I can bring that info to my CIO.  

Currently we have it set to 0, this requires me to unlock every locked account manually.
0
Comment
Question by:SSNYT
  • 2
4 Comments
 
LVL 51

Accepted Solution

by:
Keith Alabaster earned 250 total points
ID: 37704217
There is no industry standard on this setting becuase there is no standard security policy that would meet the security requirements of every organisation. In truth, the only likely 'starting standard' in use are the settings Microsoft put out during the initial deployment of AD.

Some installers may change the number of attempts before lockout occurs, some may change the time duration before new attempts can be made etc; the fact is though that 99 times out of 100 an installer - or the admins that take over the installed environment - will change one or more settings based upon their specific security policy needs to something other than the MS defaults. It is almost a ritual.

The reality is that each organisation will set their own standard based upon their specific documented security policy. Without a security policy document, what would be the basis of setting any of the parameters to a particular value?
0
 
LVL 16

Assisted Solution

by:santoshmotwani
santoshmotwani earned 250 total points
ID: 37704249
Its depends on your industry and enviroment . I manage call centre and we have lock out time of 10 mins.
0
 
LVL 1

Author Comment

by:SSNYT
ID: 37709822
Thanks Keith, that was the answer I found as well.
0
 
LVL 51

Expert Comment

by:Keith Alabaster
ID: 37709828
Welcome :)
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
Note: This is the second blog post in a series on email clearinghouses (https://www.xmatters.com/alert-management/blog-email-has-failed-us?utm_campaign=70138000000ydLoAAI&utm_source=exex&utm_medium=article&utm_content=blog-post).   Every month t…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

910 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now