> For the complete documentation index, see [llms.txt](https://takes.gitbook.io/takes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://takes.gitbook.io/takes-docs/security-and-trust/threats-and-mitigations.md).

# Security controls

| Threat                                     | Control and detection                                                   | Recovery and remaining risk                                                                                   |
| ------------------------------------------ | ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Compromised authority                      | Separate roles, restricted contract calls, visible role and fee changes | Replace eligible keys. Trading losses and incorrect permanent pairing may be irreversible.                    |
| Invalid or repeated transfer               | Attestation, route, recipient, and request checks                       | Reconcile and retry valid messages. Circle and chain failures can still stop progress.                        |
| Source-chain reorganization after delivery | Configured finality and repeated-request checks                         | Operators reconcile the source and destination. A completed destination action is not automatically reversed. |
| Incorrect payout accounting                | Separate escrow balances, credit matching, and proceeds checks          | Investigate failed settlement. A contract defect can still freeze or lose funds.                              |
| Poor trade execution                       | Price limits, reduction-first trading, and account/fill checks          | Retry from updated positions. Partial fills, slippage, and funding costs remain.                              |
| Rapid losses or liquidation                | Leverage monitoring and rebalancing                                     | Reconcile remaining funds. Automation cannot guarantee it acts before liquidation.                            |
| Stale data or service outage               | Recorded progress, freshness checks, and resumable processing           | Restore services and rebuild available history. Displays and settlement can remain delayed.                   |
| Malicious interface or stolen session      | Wallet authorization and wallet-scoped creator access                   | Revoke exposed access and inspect transactions. Harmful signatures can still move funds.                      |

These controls do not guarantee principal, liquidity, or settlement time. API limits also do not prevent someone from calling public contracts directly.

Read [Risks](/takes-docs/start-here/risks.md#risks), [Permissions](/takes-docs/security-and-trust/roles-and-permissions.md#roles-and-permissions), and [Audits](/takes-docs/security-and-trust/audits.md#audits).


---

# 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://takes.gitbook.io/takes-docs/security-and-trust/threats-and-mitigations.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.