Recovering lost passwords
How do you recommend an ASP enable customers to recover lost passwords? Letting them request their password by e-mail is vulnerable to sniffing. Letting them request their password by phone with "safeword" is vulnerable to social engineering. Any sage advice?


    Requires Free Membership to View

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

The eternal usability/security tension. The easiest is the "mother's maiden name" level of security. . . which is fairly poor security for many applications, but fine for very low risk ones.

In general, not knowing anything else, I suggest a moving scale:

High security -- No recovery. User has to re-register.

Medium security -- User encrypts passphrase on floppy keyed for local security officer. Stores in user's desk. Goes to security officer to decrypt when forgets. Floppy can be examined to ensure owned by individual.

Low security -- Combination of info gleaned during registration on secure connection (any two randomly asked questions: favorite pet's name, last four digits of SSN, mother's maiden name, etc.). Can be over SSL connection.


This was first published in April 2001