> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/security-and-governance/user-and-account-policies/account-lockout.md).

# Account Lockout

Learn about account lockout in Couchdrop

## Overview

SFTP and SCP services exposed to the internet can be targeted by repeated login attempts. Couchdrop enables an account lockout policy by default to help protect user accounts from brute-force attacks.

When the policy is enabled, a user is locked out for **15 minutes** after **5 failed login attempts within 5 minutes**.

{% hint style="info" %}
Account administrators can unlock a user immediately if required.
{% endhint %}

## Configure the lockout policy

Use **Lock Out Policy** to control whether Couchdrop temporarily locks users after repeated failed authentication attempts.

* **Lock users from logging in after multiple failed attempts** — Enables the account lockout policy.
* When enabled, users are locked for **15 minutes** after **5 failed login attempts within 5 minutes**.

The lockout policy can be disabled globally, but we recommend leaving it enabled to reduce the risk of brute-force attacks against SFTP and SCP accounts.


---

# 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.couchdrop.io/security-and-governance/user-and-account-policies/account-lockout.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.