> 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-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/miro.md).

# Miro

Use Miro data with Cortex Cloud.

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 Miro connector

Cortex Cloud supports Miro accounts on an Enterprise plan with Company Admin privileges.

> **Note:** If you need to connect the same Miro team again, you must use either a different user account or a different app (Client ID and Client Secret).

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

* **Client ID:** The public identifier for your Miro application, generated when you create an app in Miro. Cortex Cloud uses this value to identify your integration with the Miro authorization server.
* **Client Secret:** The confidential secret key for your Miro application. Cortex Cloud uses the Client ID and Client Secret to verify your application's identity during the OAuth 2.0 workflow.

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

#### Task 1: Create a Miro App

1. Log in to Miro using your Company Admin credentials.
2. Click the profile icon in the top-right corner and navigate to **Profile**.
3. Select the **Your apps** tab and click **Create new app**.
4. Enter your application details.
5. Check the **Expire user authorization token** checkbox.
6. Click **Create app**.

#### Task 2: Configure Scopes and Retrieve Credentials

1. Under **Redirect URI for OAuth2.0**, enter the Redirect URL provided on the Cortex Miro posture onboarding page.
2. Under **Permissions**, select the following required scopes:
   * `auditlogs:read` — Retrieve audit log data and track changes across companies, teams, and boards.
   * `organizations:teams:read` — Retrieve team details, settings, and team members.
   * `organizations:read` — Retrieve organization settings, plan info, and members.
3. Copy the generated **Client ID** and **Client Secret** and store them securely.

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

#### Task 3: Connect Miro to Cortex Cloud

1. In Cortex Cloud, navigate to **Settings** → **Data Sources & Integrations**.
2. Click **+ Add new**.
3. In the **Add Data Source** page, search for Miro.
4. Under **Recommended**, hover over the new Miro 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 **Client ID** and **Client Secret** details.
8. Under the **Configuration** tab, select a **Sync Interval**. Choose a meaningful **Tag** to distinguish between various applications in different environments.
9. Click **Connect**. Cortex Cloud redirects you to Miro to authorize the integration.
10. Log in with your Miro Company Admin credentials if prompted.
11. Review the requested permissions (`auditlogs:read`, `organizations:teams:read`, `organizations:read`) and click **Allow** to grant access.
12. A confirmation message shows that Miro 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-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/miro.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.
