4 ms·
You don't need to make a system that's perfect. You just need to make a system in which checks are required to make _any_ change the credentials on an account.
by slavik81 9y ago
You don't need to make a system that's perfect. You just need to make a system in which checks are required to make _any_ change the credentials on an account. Once those checks are complete, it makes no difference if the change is from john.doe@example.com to johndoe@example.com or to jonathan.doe@example.com.
- Alex3917 9y agoIt’s not just password resets that are the issue. It’s also things like: - Functions to get the account based on the email address - Internal tools - Stored procedures and other SQL stuff that happens outside the main code base - Third-part integrations (Mailgun, Sailthru, ZenDesk, SalesForce, etc.) That’s a huge attack surface where if there is even a minor mistake by a junior dev that no one noticed then everyone is going to lose their assets under protection.