> For the complete documentation index, see [llms.txt](https://broker-docs.tiger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broker-docs.tiger.com/english-2/financial-operations/withdrawal/yubikey-security-key.md).

# YubiKey security key

It's a hardware security key that provides an additional layer of protection for the user. It can be used to confirm withdrawal operations.

### Key features

* Link up to **5 security keys** to your account.
* Confirm withdrawals using **any active key**.
* Signature timeout — **5 minutes**.
* Support for **YubiKey** and **PassKey**.

<figure><img src="https://3857619824-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fyw4jlbyXBiRSgCIsu0tg%2Fuploads%2FU2mQoIo6AsfIh8eI4pqb%2Fimage%20(3).png?alt=media&amp;token=9509d612-da13-4e02-95a9-5fcf573f4eef" alt=""><figcaption></figcaption></figure>

***

### How to add a security key

{% hint style="info" %}
**Important!** You must activate the **PIN code** feature before linking a security key.
{% endhint %}

1. Go to **Settings → Security Key**.
2. If no keys are linked, the status will display **“Not linked”**. The **“Link”** button is active only if the PIN code is enabled.
3. If at least one key is linked, the status will display **“Linked”**, and the **“Add key”** button will be available.
4. If 5 keys are already linked, the button becomes inactive, with the message: *“Maximum 5 keys”*.
5. The key list displays: number, name, creation date, last usage, and the **Delete** button.
6. When deleting a key, a confirmation modal opens (if the key was used before).

{% hint style="info" %}
**Recommendation:** Use at least **2 security keys** for extra protection.
{% endhint %}

To add a key:

Click **“Add key”** → a modal window opens → confirm via **PIN code**.

<figure><img src="https://3857619824-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fyw4jlbyXBiRSgCIsu0tg%2Fuploads%2FCSj3SBEWxa2Pd9Fcb38C%2Fimage%20(4).png?alt=media&amp;token=36b55a65-c12b-4aaf-8cf9-fdbd9beb67f8" alt=""><figcaption></figcaption></figure>

***

### How to delete a security key

1. In the key list, click the **delete (✖) icon**.
2. Follow the instructions in the confirmation modal.

***

### Confirming withdrawals with a security key

1. Go to the **Withdrawal** page and start the withdrawal process.
2. A confirmation modal will appear → connect your previously linked security key.
3. After successful signing, the next step opens → enter your **PIN code** and **2FA**.
4. If an error occurs, you’ll see the message **“Connection interrupted”**.

{% hint style="info" %}
**Important!**&#x20;

* Security key confirmation for withdrawals is **not available on the mobile site**. Please use the **full site version**.
* Security key confirmation is **not supported in the Tiger Control app**.
  {% endhint %}

***

### 24-hour withdrawal lock

Withdrawals are blocked for **24 hours** in the following cases:

* Linking a second or subsequent key (if confirmation is done with a new key).
* Deleting any key.

{% hint style="info" %}
**Important!** No withdrawal lock is applied when linking the **first key**.
{% endhint %}

***

### Lost access to security keys

* **If one key is lost:**
  * Deletion must be confirmed with another active key.
  * Withdrawals are blocked for **24 hours**.
* **If all keys are lost:**
  * Reset is possible only via **identity verification in Sumsub** (documents + selfie).
  * All keys are deleted.
  * Withdrawals are blocked for **24 hours**.


---

# 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://broker-docs.tiger.com/english-2/financial-operations/withdrawal/yubikey-security-key.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.