Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: Secure Password Policy? |
|---|---|
| Date: | Fri, 20 Jan 2006 10:03:02 +0100 |
Sulaiman, Wilmar [mailto:wsulaiman@siddharta.co.id] asked
I noticed that "best practice" for Minimum password length policy is either 6 or 8 characters. I guess SANS institute considered a weak password if it is less than 8 characters.
Isn't there an explanation of those magic numbers somewhere nearby, or an assumption about how the passwords are selected, or the login situation? If not, the author should probably be considered suspect.
Is there any documentation to backup it up why the best practice for minimum password length is set to 6?
Pick a log-in service you're interested in. Say FTP. Pick a login-testing program, such as THC Hydra, and set it up to talk to the FTP service. Feed a big password list do it, so that it keeps working for a reasonable time. How many password guesses can it do per second, with various tweaks (I have an old figure of 120 attempts per second, sustained. But this was more than 12 months ago, and for another program on a loopback connection. Find out *your* guessing rate.) Next, how long will it take, worst case, before this guessing is discovered, and actually stopped, for instance by blocking your IP in the firewall? An hour? A day? A week? (Say 14 days - IT department is off on very long Xmas vacation, or whoever is responsible for reading security logs gets his hands full with more pressing work, but after 14 days log space will be full, and system will halt...). 14 days * 120 attempts / second make approx 150Mattempts. You want a password that resists that many guesses with a decent probability margin -- as you don't know the order in which the guesses will be made. Assuming A-Za-z0-9 (62 character) truly random password, length 5 gives about 10% chance for a crack in 14 days, length 6 0.3% and so on. I'm not sure what to go for here, but I'd try to get below 0.01%, at least. As should be obvious, the most important security measure in this kind of situation is to limit the guessing rate. I'd say 100 guesses per hour is acceptable, except perhaps in high-security installations. 14 days * 100 attempts / hour make approx 34kattempts. Much nicer. A length 6 password is now quite difficult to guess in the stipulated time, even without special characters. Still, it doesn't mean much unless passwords are truly random. Users tend to find the password of least effort -- and those are often easy to guess. I've seen 'Volvo-V70' (or very close relatives) as a password more often than I care to remember -- but it is long, has both upper and lower case letters, digits and even a special character. It is still probably among the first 100000 passwords to be guessed in an attack (locally). So length 6 = 0.3% is rather optimistic ... passwords won't be random unless you ensure it in some way. I don't know any password length calculations that tries to take 'easy passwords' into account. The only way I know to estimate if a password is 'easily guessed' is to let John the Ripper generate passwords ... if the password is in the first million produced or so, it's probably easily guessed. Anders Thulin anders.thulin@tietoenator.com 040-661 50 63 TietoEnator Telecom & Media AB, Box 85, SE-201 20 Malmö ------------------------------------------------------------------------------ Audit your website security with Acunetix Web Vulnerability Scanner: Hackers are concentrating their efforts on attacking applications on your website. Up to 75% of cyber attacks are launched on shopping carts, forms, login pages, dynamic content etc. Firewalls, SSL and locked-down servers are futile against web application hacking. Check your website for vulnerabilities to SQL injection, Cross site scripting and other web attacks before hackers do! Download Trial at: http://www.securityfocus.com/sponsor/pen-test_050831 -------------------------------------------------------------------------------
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Secure Password Policy?, Marek Isalski |
|---|---|
| Next by Date: | RE: Secure Password Policy?, Shenk, Jerry A |
| Previous by Thread: | Re: Secure Password Policy?, Marek Isalski |
| Next by Thread: | RE: Secure Password Policy?, Shenk, Jerry A |
| Indexes: | [Date] [Thread] [Top] [All Lists] |