> 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/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/sharefile.md).

# Sharefile

Use ShareFile data with Cortex XSIAM.

The capabilities and sub-capabilities listed for this connector are available with any active Cortex XSIAM or Cortex Cloud Posture Security license.

This connector includes the following capabilities and sub-capabilities (if applicable):

* **SaaS Posture Configuration Monitoring:** Detect, monitor and alert on settings of your SaaS application.
  * **saas-posture-config-remediation:** Help remediate the misconfigured security settings of your SaaS application.

### How to configure the ShareFile connector

Cortex XSIAM supports ShareFile accounts on an Advanced or Premium plan or higher. The connector uses the OAuth 2.0 Resource Owner Password Credentials grant to authenticate.

> **Important:** If your ShareFile administrator account has Two-Step Verification (2FA) enforced, the password grant will be rejected. Use a dedicated administrator account that is exempt from 2FA, or an account with an app-specific password if your tenant supports it.

To access ShareFile, Cortex XSIAM requires the following information, which you will specify during the connection process.

**Subdomain:** The unique subdomain of your ShareFile account URL. Cortex XSIAM uses this value to route API calls and build the token endpoint for your account.

**Client ID:** The unique identifier for your ShareFile OAuth client application, generated in the ShareFile Developer Portal.

**Client Secret:** The secret key for your ShareFile OAuth client application. Cortex XSIAM uses the Client ID and Client Secret together with the administrator credentials to authenticate to the ShareFile API.

**Username:** The email address of a ShareFile administrator account. The account must have the Master Administrator role, or an Employee user role with the **Manage account settings**, **Manage single sign-on**, and **Manage devices / device security** admin permissions. A non-admin account will authenticate successfully but return HTTP 403 on settings endpoints.

**Password:** The password for the ShareFile administrator account specified above.

Perform the following procedures in the order that they appear below.

#### Task 1: Identify Your ShareFile Subdomain

> **Important:** The subdomain cannot be changed after the instance is created. If you enter the wrong subdomain, you must delete the instance and create a new one.

1. Log in to your ShareFile account.
2. Look at your browser's address bar. Your subdomain is the portion of the URL that appears before `.sharefile.com`. For example, in `https://acme.sharefile.com`, the subdomain is `acme`.

   > Only alphanumeric characters and hyphens are permitted in the subdomain field.
3. Copy the subdomain and store it in a text file.

   > Do not continue to the next step unless you have copied the subdomain. You must provide this value to Cortex XSIAM during the onboarding process.

#### Task 2: Create a ShareFile OAuth Client

1. Navigate to the [ShareFile Developer Portal](https://api.sharefile.com) and sign in with your ShareFile administrator account.
2. Open **API Keys**.
3. Click **Create New**.
4. Complete the application registration form:

   * **Application Name:** for example, `PaloAlto_Cortex_Integration`

   * **Description:** for example, `Palo Alto Networks Cortex SSPM posture monitoring`

   * **Redirect URI:** Enter any valid HTTPS URL you control, for example `https://localhost/oauth/callback`.

   > The Cortex ShareFile connector uses the password grant and never performs a browser redirect. If the portal marks the Redirect URI field as mandatory, enter any valid HTTPS URL — it will not be used by Cortex XSIAM.
5. Click **Generate API Key**.

#### Task 3: Retrieve Your Client ID and Client Secret

1. Open the newly created application under **Get API Key**.
2. Locate the **Client ID** (also shown as **Key** in some portal versions).
3. Locate the **Client Secret** (also shown as **Secret**). Click **Show** if it is masked.
4. Copy both values and store them securely.

   > Do not continue to the next step unless you have copied both values. You must provide them to Cortex XSIAM during the onboarding process.

#### Task 4: Connect ShareFile to Cortex XSIAM

1. In Cortex XSIAM, navigate to **Settings** → **Data Sources & Integrations**.
2. Click **+ Add new**.
3. In the **Add Data Source** page, search for ShareFile.
4. Under **Recommended**, hover over the new ShareFile integration and click **Add Instance** to launch the configuration wizard.
5. Under the **Capabilities** tab, enter a name for your application.
6. Select **Security Posture** under **Default Capabilities**. Click **Next**.
7. Under the **Connection** tab, enter the **Subdomain**, **Client ID**, **Client Secret**, **Username**, and **Password** details.
8. Under the **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments.
9. A confirmation message shows that ShareFile is successfully connected. Confirm the **Summary** details and click **Save instance**.


---

# 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/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/sharefile.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.
