> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/users-and-roles-management/configure-a-password-policy.md).

# Configure a password policy

Configure and edit the password policy in Cortex XSOAR 8.10 On-prem.

To define your password policy, go to **Settings & Configurations** → **Settings** → **Access Management** → **Password Policy**.

You can define your password policy using the following parameters:

* Minimum number of characters
* Minimum number of lowercase letters
* Minimum number of uppercase letters
* Minimum numbers of digits or symbols

In addition, you can require users to change their password every X number of days or months. By default, this setting is not enabled and passwords do not automatically expire. You can also prevent users from reusing previous passwords.

The lock settings enable you to lock a user out of Cortex XSOAR after a set number of failed login attempts within one minute. You can either have the user automatically unlocked after a set number of minutes or hours, or you can only allow the user to be unlocked by an administrator. To unlock a user, go to **Settings & Configurations** → **Settings** → **Access Management** → **Users**, right-click on the username, and select **Unlock**.

Users can change their passwords by clicking the username at the bottom of left hand main menu and selecting **User Preferences** → **Details**.


---

# 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/users-and-roles-management/configure-a-password-policy.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.