Respond to Leaked Credentials Events

there are several ways to respond to credential leaks, where flare discovers username and password pairs the options available depend on how flare integrates with your systems the key point is that before warning your users that their passwords have been leaked we recommend a few steps (and recommend those steps are automated for faster processing) check if the leaked credentials follow your company's password policy, hence validating whether this is a password your employee/client could have used in your login portal verify the date the breach happened this is different from the date it was leaked and we sent to you the breach date is the date the company data was stolen, and can sometimes date back many years passwords your employee/client might have been using 5 years ago is less critical than one they used this month check whether this is an email/password combination that has already been leaked (using a service such as have i been pwned) maybe you already warned this user and they aren't using this password anymore this step is optional but adds a lot of value; if the password is in clear text, use the hashing algorithm used in your accounts database to hash the passwords compare the hash you receive in output with the hashed password of this user in your system a match means this password is compromised and you should trigger a password reset right away if desired, inform the user by following the steps in the section below remember that flare is there to help you if you are interested in automating such actions we have assisted multiple clients in setting up automations and would be happy to work with you to do it moving forward informing users when leaked credentials are found for your employees, it is often important to let employees know here are some elements to keep in mind users may have already received notification if they are subscribed to a service such as have i been pwned or firefox monitor if you have a regular continuous process, you may already have alerted them for a similar or identical password if the user is not generally aware of it and cyber risks, they may not understand why or how you got access to their password in these cases, flare recommends disclosing only the first 3 characters of the password to the employee (providing "sum " instead of "summer1969") the employee will recognize the password types of credentials sources there are a number of ways leaked credentials are shared and re shared in the criminal underground they are detailed here related articles