Frequently Asked Questions
Get answers to commonly asked questions
Strong password requirements may actually be part of the problem. The difficulty creating and remembering complicated passwords increases the temptation to reuse the same password. Read more about strong passwords.
Not so much. Having more security layers is definitely better, but neglecting to protect passwords just weakens an essential layer. If your organization is investing in multi-factor (and the added effort that imposes on your users), allowing them to use known compromised credentials just doesn’t make sense.
When we report a credential exposure, we share extensive details about what we found, including: the site where it was found, the total number of credentials in the exposure, what types of data we found (physical address, phone, etc), the format of passwords (clear text, MD5) and more. Read more in our Developer Docs.
PasswordPing is designed to exceed the most stringent requirements of enterprise security professionals. We offer both SaaS and On-Premises deployments of our solution. The credentials in our database are encrypted and only stored in a salted and strongly hashed format where we have absolutely no way of recovering the original data. And we never store submitted data; it is kept in memory on our servers only long enough to perform the database lookup and then the memory is zeroed out at the end of the call. Read more in our Security Overview