> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/cyberark-sia.md).

# CyberArk SIA

Configure CyberArk SIA entries in Remote Desktop Manager, including the SIA subdomain, MFA caching, and the optional username and password for SSH.

This article details the many settings and options available for ***CyberArk SIA*** entries in Remote Desktop Manager.

{% hint style="info" %}
A valid CyberArk license is required. Without it, the settings are unavailable and the message "License key is required" is displayed. To link this entry to a session, see [CyberArk SIA entry](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/cyberark-sia-entry.md).
{% endhint %}

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr><tr><td><strong>Display</strong></td><td>How the entry is displayed. This entry type supports only the external display mode, so the selection is locked.</td></tr><tr><td><strong>Credentials</strong></td><td>The source of the credentials. When the credentials come from another source, the <em><strong>Username</strong></em> and <em><strong>Password</strong></em> fields of the <em><strong>General</strong></em> tab are unavailable.</td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Subdomain</strong></td><td>The subdomain of your CyberArk SIA instance. Required.</td></tr><tr><td colspan="2"><strong>Optional (SSH only)</strong></td></tr><tr><td><strong>Use MFA caching</strong></td><td>Use CyberArk MFA caching instead of a username and password. When selected, the <em><strong>Username</strong></em> and <em><strong>Password</strong></em> fields are unavailable and are not saved.</td></tr><tr><td><strong>Username</strong></td><td>The username used for SSH sessions. It is ignored when launching anything else.</td></tr><tr><td><strong>Password</strong></td><td>The password used for SSH sessions. It is ignored when launching anything else.</td></tr></tbody></table>


---

# 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.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/cyberark-sia.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.
