> 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-posture-management/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/zoom.md).

# Zoom

Use Zoom 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 Zoom connector

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

* **Account ID:** A unique identifier for your Zoom account.
* **Client ID:** The client identifier generated when you create a Server-to-Server OAuth app in the Zoom Marketplace.
* **Client Secret:** The client secret generated when you create a Server-to-Server OAuth app in the Zoom Marketplace. Cortex Cloud uses the Client ID and Client Secret to authenticate to the Zoom API.

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

#### Task 1: Create a Server-to-Server OAuth App in Zoom

1. Navigate to <https://marketplace.zoom.us/> and sign in to your account.
2. Select **Developer** in the bottom-left corner to open the developer console.
3. In the top navigation bar, click the **Develop** dropdown and select **Build App**.
4. Locate the **Server-to-Server OAuth** app type and click **Create**.
5. Enter a name for your application and click **Create**.
6. Copy your **Account ID**, **Client ID**, and **Client Secret** and paste them into a text file.

   > Do not continue to the next step unless you have copied all three values. You must provide this information to Cortex Cloud during the onboarding process.
7. Click **Continue** and complete the required basic information fields.
8. Add the following scopes for SSPM scanning:
   * `account:read:lock_settings:admin`
   * `account:read:settings:admin`
   * `user:read:user:admin`
   * `user:read:user:master`
9. Activate the application.

#### Task 2: Connect Zoom 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 Zoom.
4. Under **Recommended**, hover over the new Zoom 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 **Account ID**, **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. A confirmation message shows that Zoom 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-posture-management/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/zoom.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.
