6 Password Security Essentials For Developers

Solving the weak password challenge requires more than having consumers create strong passwords. Many businesses also need to get a clue about what counts as safe, weak, encrypted, or secure.

Does one of the worlds largest grocery chains have a clue when it comes to online password security?
Thats one obvious question after London-based Web developer Dan Blows
tweeted
his discovery that grocery and merchandising retailer Tesco--based on its revenue, the fourth-largest retailer in the world--stores their website passwords unsalted, and emails them unencrypted.
Whats wrong with that? In the eyes of information security experts, emailing plaintext passwords to customers undercuts any other password security mechanisms that might be in place. Plaintext passwords can be intercepted by wireless data sniffers, retrieved from PC hard drives, often
intercepted using Firesheep
, or lifted from hacked email accounts.
Other Tesco website password sins, according to an analysis published by software architect Troy Hunt on his
blog
, include limiting users to passwords containing only up to 10 characters and not differentiating between upper-case and lower-case letters. In addition, based on the fact that a password-retrieval request returns a password in entirely capital letters, Hunt said its obvious that the Tesco website doesnt hash passwords, because that would fail the case sensitivity test, and also means its extremely unlikely that the website encrypts passwords when stored.
[ People lose passwords. Learn
5 Ways To Solve The Password Reset Problem
. ]
An alleged Tesco support email
uploaded to Pastebin
further suggests that the company doesnt encrypt passwords. Although the information is not encrypted the level of security surrounding the password means that only the senior technical positions could access the information, reads the email.
But when it comes to password security, Tesco is the kind of multi-billion dollar brand that should know how to get Web security basics right, particularly when theyre providing online shopping services and handling your payment info, said Hunt. Accordingly, what should Tesco--or any other business with
password security problems
--do better?
Hunt offered these six tips for developers:
1. Always hash passwords.
Use a hashing algorithm designed for passwords, and also use a cryptographically random salt, said Hunt.
2. Prohibit password retrieval.
Password retrieval should never happen, said Hunt, and if hashing has been implemented correctly,
retrieving passwords
wont be possible. Instead, always implement a secure password reset process, he said.
3. Dont limit password length or variety.
There should never be restrictions on password entropy, said Hunt. Dont exclude special characters, dont chop the length at a short, arbitrary limit--if you have to, make it 100 chars or so-and definitely dont implement a system which is case-insensitive.
4. Dont mix HTTP and HTTPS.
One common password-related error developers make is to use HTTP content on HTTPS pages, as well as to provide credentials via HTTP. Credentials--and arguably entire sessions in the wake of Firesheep--should not be transferred over unencrypted networks,
said Hunt
. Its just too easy to get hold of them.
5. Keep systems updated.
Beyond poor password practices, Hunt also found--via the
Fiddler Web debugging proxy
--that the Tesco Web server that runs its Web applications rates as very out of date. In particular, its running IIS 6, which is seven years old and twice--nearly thrice--superseded, as well as ASP.NET 1.1, which Hunt noted is now nine years old. While such systems were fine in their day, the security landscape has changed significantly since these technologies were launched and ongoing improvements in newer generations of the breed make continued progress in ensuring a more secure app by default, he said.
6. Educate the customer service team.
In response to security experts questioning Tescos website security prowess, the companys customer care team
tweeted
, We know how important Internet security is to customers and the measures we have are robust.
Later, in response to specific criticisms from Hunt,
Tesco tweeted
, Let me assure you that all customer passwords are stored securely & in line with industry standards across online retailers. Hunt responded: Let me assure you that if you are emailing passwords to customers, you are well short of industry standards on a number of fronts.

Last News
▸ DHS-funded SWAMP scans code for bugs. ◂ Discovered: 23/12/2024 Category: security	▸ Debunking Machine Learning in Security. ◂ Discovered: 23/12/2024 Category: security	▸ Researchers create BlackForest to gather, link threat data. ◂ Discovered: 23/12/2024 Category: security

**Cyber Security Categories**
Google Dorks Database	Exploits Vulnerability	Exploit Shellcodes

CVE List

Tools/Apps

News/Aarticles

Phishing Database

Deepfake Detection

Trends/Statistics & Live Infos

Tags:
6 Password Security Essentials For Developers