> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/authentication/passwordless-for-web-apps/login-methods/behavioral-authentication.md).

# Behavioral Authentication

Behavioral Authentication in 1Kosmos analyzes how a user interacts with their device, specifically their typing pattern, and compares it against their enrolled behavioral profile to verify identity.

***

### Overview

**Behavioral Authentication** is particularly useful in environments requiring complex passwords (14–16 characters for PCI DSS compliance). With Behavioral Authentication and a PIN enrolled, users can log in without repeatedly typing long passwords. It is also ideal for workplaces where cameras are unavailable for LiveID Selfie authentication or where users cannot carry personal devices to use authentication methods such as QR codes, Push notifications, TOTP, or Security Keys.

For more information see [Behavior Authentication](/authentication/windows-workstation-mfa/authentication-methods/behavior-authentication.md).


---

# 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.1kosmos.com/authentication/passwordless-for-web-apps/login-methods/behavioral-authentication.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.