Make reset requests hard to abuse

Use the same general response whether an account exists or not. Apply rate limits to reset requests and avoid revealing whether an email address is registered.

Generate reset tokens with strong randomness. Give them a short lifetime, allow one use and bind them to the account and purpose.

Protect the recovery channel

Send reset links only to a verified recovery address. Use HTTPS and avoid including private data in the URL. After a password change, invalidate active sessions or let the user review and revoke them.

Do not treat knowledge-based questions as strong proof of identity. For high-risk accounts, use a second trusted factor or a reviewed support process.

Notify and test account changes

Notify the account owner when recovery details or credentials change. Make a report path available if the user did not request the change.

Test expired tokens, repeated requests, concurrent resets and account enumeration. Include recovery flows in web application testing.