Perimeter
1/29/2010
01:11 PM
Adrian Lane
Adrian Lane
Commentary
50%
50%

Wiping Out Wimpy Passwords

Recent breaches at Rockyou.com and Hotmail illustrate the consistency of human behavior: Since the dawn of access control systems, users continue to choose easily guessed passwords.

Recent breaches at Rockyou.com and Hotmail illustrate the consistency of human behavior: Since the dawn of access control systems, users continue to choose easily guessed passwords.From these exploited accounts (check out Dark Reading's coverage about Rockyou.com and Hotmail), we have substantial proof that weak passwords are the norm, and that compromised accounts are used to launch subsequent phishing and malware attacks. Most security researchers know that passwords are of limited use -- even with strong passwords, keystroke loggers and phishing attacks will divulge strong and weak passwords alike. Regardless, having a slightly better password reduces the common threat of password dictionary attacks.

So how do you go about it?

As with most applications, passwords are the front line of defense for databases. All databases have features to enforce the use of strong passwords. I could detail for you the wonderful ways your database will help enforce password length and complexity, lock accounts after failed login attempts, or require password rotation. But you probably already know this. Besides, password-strength enforcement is just the starting point. If you have not turned on password complexity checkers or login triggers to verify new passwords, then stop reading this right now and go do that right now! It's free, and it's easy. And no cheating: Apply the rules to DBA and service accounts used by applications, not just end users.

Now that password controls are in place, here's what else you should do:

Training: Teach people how to create more secure passwords. Send an email, post to your internal Website, or talk to them over lunch, but give them some simple guidelines. Teach them how to pick a word or phase that is easy to remember, such as something they see visually each day, or perhaps something from their childhoods. Now show them simple substitutions of the letters with special characters and numbers.

Logging: When attempting to guess a password, normally you will fail many times before you find the right password. Simple platform or database logging captures these failed attempts, and review of the log files makes it very apparent when an account is being attacked. Turn on simple logging and, more important, review the results.

Monitoring: If someone has gotten your password, through keystroke logger, phishing, or reading the Post-It note on your desk, then none of the steps mentioned above will help. If you are worried about this, you need to use activity monitoring. Monitoring can detect compromised accounts by comparing a user's current requests with a known behavioral profile, detecting account compromises when the patterns don't match and alerting to suspicious activity.

Human behavior is unlikely to change anytime soon, and people cannot resist clicking on embedded email links that result in their machines being compromised. But a combination of password checking, training, and logging makes your access controls far more effective.

Adrian Lane is an analyst/CTO with Securosis LLC, an independent security consulting practice. Special to Dark Reading. Adrian Lane is a Security Strategist and brings over 25 years of industry experience to the Securosis team, much of it at the executive level. Adrian specializes in database security, data security, and secure software development. With experience at Ingres, Oracle, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Title Partner’s Role in Perimeter Security
Title Partner’s Role in Perimeter Security
Considering how prevalent third-party attacks are, we need to ask hard questions about how partners and suppliers are safeguarding systems and data.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-3407
Published: 2014-11-27
The SSL VPN implementation in Cisco Adaptive Security Appliance (ASA) Software 9.3(.2) and earlier does not properly allocate memory blocks during HTTP packet handling, which allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCuq68888.

CVE-2014-4829
Published: 2014-11-27
Cross-site request forgery (CSRF) vulnerability in IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allows remote attackers to hijack the authentication of arbitrary users for requests tha...

CVE-2014-4831
Published: 2014-11-27
IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to hijack sessions via unspecified vectors.

CVE-2014-4832
Published: 2014-11-27
IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to obtain sensitive cookie information by sniffing the network during an HTTP session.

CVE-2014-4883
Published: 2014-11-27
resolv.c in the DNS resolver in uIP, and dns.c in the DNS resolver in lwIP 1.4.1 and earlier, does not use random values for ID fields and source ports of DNS query packets, which makes it easier for man-in-the-middle attackers to conduct cache-poisoning attacks via spoofed reply packets.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?