> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/faqs/miscellaneous/protecting-against-password-reuse.md).

# Protecting against password reuse

This article describes how Perkville helps protects against credential stuffing, and what you can do to secure your account

Perkville helps protect your account from [credential stuffing](https://en.wikipedia.org/wiki/Credential_stuffing), a type of attack where previously-gathered credentials from other data breaches (at other products) are used in order to gain access to a different product. Why does this work? Because many users re-use the same passwords across multiple products and services.

The best way to protect yourself from credential stuffing is to use a password manager, such as iCloud Keychain or 1Password, to generate a secure, unique password at every product you or your staff use.

## Validating that your password has not been implicated in a prior data breach at a different company

Perkville helps protect your account by, every time you log in, verifying that your password has not previously been implicated in a data breach at another company. How can we verify this? With the help of web application security expert Troy Hunt's [Have I Been Pwned](https://haveibeenpwned.com/Passwords) (HIBP), a free and oft-updated database of passwords from known data breaches.

When you log in, we [hash](https://en.wikipedia.org/wiki/SHA-1) your password and send the first five bytes of the hash to HIBP's API. They return a list of matching hashes, and we look for a match to your hash. In this way, your password isn't sent to HIBP, but we are able to tell from HIBP if the password has appeared in a prior breach at another company (not Perkville!).

HIBP also returns the number of data breaches that have included each password, allowing us to generate a helpful message that includes that number.

These validation steps are sanctioned and [strongly recommended](https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html) by the Open Web Application Security project.

## What to do if your password has been compromised at another company

If you see a message like "Your current password has appeared in \[ ] data breaches," all you have to do is follow [the reset password flow](https://www.perkville.com/login/#reset) and select a new password.

We strongly recommend using a password manager, such as iCloud Keychain or 1Password, to generate a secure, unique password for every product you use.

If you use that password on any other service, we strongly recommend updating those other service passwords as well.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perkville.com/faqs/miscellaneous/protecting-against-password-reuse.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
