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 19:08:30 +1100 |
A couple of general comments. For many people, 6 characters 'has a nice feel to it', minimises password guessing in a ~30 day change window _when_ 5 failures == account lock. I don't understand why people would use annual or 90-day change windows, personally. In other words, password length, complexity, change period and failure thresholds need to be considered as one security control, not individually, imho. Lots of banks only require 6 characters for online banking, or even just 6 digits. RACF-enabled IBM mainframes (os/390, zOS etc) are typically limited to 8 characters maximum length. Rainbow tables make password up to around 8 characters easy to crack, if the attacker has the time to pre-compute the tabes. Making rainbow tables beyond 8 is long term planning, and somewhat disk intensive for script-kiddy level attacks. NTLM hases are trivial - effective max password length is 7, or 2x7 'passwords' Seriously motivated attacks will be internal, and have other ways to get/guess passwords imho, or get in via other means (local access the escalate or remote access then escalate), since it's probably quicker to attack via means other than password cracks/guesses at 8+ character lengths. If your threat model includes being up against government/fortune500 resources, then passwords are the least of your problems since they are after information, not system access. Lyal -----Original Message----- From: Mike Dieroff [mailto:michael@bluescreenit.co.uk] Sent: Friday, 20 January 2006 4:39 AM To: Sulaiman, Wilmar Cc: pen-test@securityfocus.com Subject: Re: Secure Password Policy? Hi there, As far as I remember, the NTLANMAN hash maxed at 8 and LM hashes at 13 characters... could be corrected... I have not really heard of any 'secure' implementation with 6 character passwords - The minimum today would be: 1.) Password length: 8 characters 2.) Full complexity: Upper and lower case, numerals, alphanumerics <---- Don't forget the spacebar here!!always a good one! 3.) Max age average of around 40 - 60 days dependant 4.) History of around 10 passwords Hope this helps, Mike ---------------------------------------------------------------------------- -- 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 ---------------------------------------------------------------------------- --- ------------------------------------------------------------------------------ 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?, Tim |
|---|---|
| Next by Date: | Re: Secure Password Policy?, Marek Isalski |
| Previous by Thread: | Re: Secure Password Policy?, Mike Dieroff |
| Next by Thread: | RE: Secure Password Policy?, Petr . Kazil |
| Indexes: | [Date] [Thread] [Top] [All Lists] |