> For the complete documentation index, see [llms.txt](https://docs.caf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caf.io/caf-docs/our-solutions/smart-auth.md).

# Account Takeover Prevention

### What is Caf. Account Takeover Prevention?

Caf's Account Takeover Prevention has the main purpose of analyzing whether a user is who he says he is, preventing account takeover attacks (ATO) through Smart Auth, a multi-factor authentication product.

Our solution can perform dozens of under-the-hood analyses (depending on the client's settings) to allow or deny an authentication attempt.

You can find a Overview at [Smart Auth Overview](https://docs.caf.io/caf-docs/user-guide/smart-auth.md).

### Key benefits

1. **Real-time detection:** We use advanced technology for agile detection and immediate action to mitigate fraud risks.
2. **Risk-based authentication:** Ability to create custom authentication rules based on access context and risk level.
3. **Long-term protection :** Continuous monitoring to ensure security throughout the endless customer journey.

### Starting with Caf. Smart Auth

You can learn more about this solution at: [Smart Auth Overview](https://docs.caf.io/caf-docs/user-guide/smart-auth.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.caf.io/caf-docs/our-solutions/smart-auth.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.
