> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/protect-your-endpoints/endpoint-security/install-and-manage-endpoints/manage-endpoint-protection/retrieve-support-file-password.md).
# Retrieve support file password
Retrieve the Cortex XSIAM support file password for endpoint troubleshooting.
The Cortex XDR agent generates the Tech Support File (TSF) as a password-protected zip archive. The TSF is packaged inside an outer archive that also contains a metadata file with the encrypted token used to retrieve the password. Follow the steps below to retrieve the password and unzip the file.
The TSF is generated in either of two ways:
* **Remotely from Cortex XSIAM -** The **Retrieve Support File** action is initiated from the **Action Center** or from an endpoint's page. The resulting archive is downloaded from the Action Center.
* **Locally from the endpoint** - The `cytool log collect` command is run on the endpoint's command line. The resulting archive is saved on the endpoint's local filesystem.
{% stepper %}
{% step %}
### Locate the token
Find the encrypted token inside the archive.
1. Open the outer archive that contains the TSF. This is either the file you downloaded from the **Action Center** or the file saved locally on the endpoint.
2. Locate and open the metadata file (typically named `_CRYPTO-INFO`).
3. Copy the encrypted token string it contains.
{% endstep %}
{% step %}
### Retrieve the TSF file password
The next steps depend on how the TSF was generated.
From the Action Center
Follow these steps if the TSF was downloaded from the **Action Center**.
1. Go to **Action Center** → **All Actions**.
2. Locate your **Support File Retrieval** action.
3. Right-click the action and select **Retrieve Support File Password**.
4. In the **Retrieve Support File Password** dialog box, in the **Encrypted Password** field, paste the token that you copied in Step 1.
5. Click the copy button to copy the displayed password and then click **Ok**. Use the password to unzip the TSF file.
From the endpoint
Follow these steps if the TSF was collected locally by running the `cytool log collect` command on the endpoint's command line.
1. Go to **Inventory** → **Endpoints** → **All Endpoints**.
2. At the top of the page, click the key icon 
(**Tokens and Passwords**) and select **Retrieve Support File Password**.
3. In the **Retrieve Support File Password** dialog box, in the **Encrypted Password** field, paste the token that you copied in Step 1.
4. Click the copy button to copy the password displayed and then click **Ok**. Use the password to unzip the TSF file.
{% endstep %}
{% endstepper %}
---
# 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://cortex-docs.paloaltonetworks.com/cortex-xsiam/protect-your-endpoints/endpoint-security/install-and-manage-endpoints/manage-endpoint-protection/retrieve-support-file-password.md?ask=&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.