> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/saas-data-monitoring/inventory/inventory-assets/zoom-recordings.md).

# Zoom recordings

With DoControl's inventory, you can discover all your Zoom recordings and monitor Zoom events:

* Expose a full inventory and monitor Zoom users and assets, including every individual user, cloud-based recording, meeting, chat, closed caption, and audio transcript
* Leverage metadata about users, such as role, status, and manager
* Slice and dice your data in a meaningful way; for example to analyze publicly shared recordings related to a specific user

You can use using different [filtering options](#filter-options) to view Zoom recordings for specific [use cases](#use-cases), such as recordings that are publicly shared or aren't passcode protected. 

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FaBESNFFBd4CDKfnfb8Aj%2FZoom%20assets.png?alt=media&amp;token=23e9c92a-55ba-4de5-8329-65fa56b03b23" alt=""><figcaption></figcaption></figure>

Data for Zoom recordings is displayed according to these columns:

<table><thead><tr><th width="248.33333333333331">Zoom recording column</th><th>Description</th></tr></thead><tbody><tr><td>Topic</td><td>Name of Zoom recording</td></tr><tr><td>Host</td><td>Email address of recording host</td></tr><tr><td>Sharing status</td><td>Indicates if the recording is publicly shared</td></tr><tr><td>Passcode protection</td><td>Indicates if the recording is restricted with a passcode</td></tr><tr><td>Start time</td><td>Date and time when recording started</td></tr><tr><td>Total views</td><td>Number of times the recording was accessed and watched</td></tr><tr><td>Total downloads</td><td>Number of times the recording was downloaded</td></tr></tbody></table>

## Filter options

Filter options for Zoom recordings include the following:

<table><thead><tr><th width="180">Filter</th><th width="144">Comparator</th><th>Description</th></tr></thead><tbody><tr><td>Topic</td><td>String</td><td><p>Name of Zoom recording:</p><p>Equals, doesn't equal, starts with, ends with, contains, doesn't contain, includes, excludes</p></td></tr><tr><td>Host</td><td>String</td><td><p>Host who initiated Zoom meeting:</p><p>Equals, doesn't equal, starts with, ends with, contains, doesn't contain, includes, excludes</p></td></tr><tr><td>Sharing status</td><td>Includes or excludes</td><td><p>How Zoom recording is shared:</p><p>Publicly, internally, none </p></td></tr><tr><td>Passcode protection</td><td>Boolean</td><td><p>If Zoom recording has a passcode:</p><p>Protected or not protected</p></td></tr><tr><td>Start time</td><td>Date</td><td><p>Time that Zoom recording began:</p><p>Equals, after, before, is between</p></td></tr></tbody></table>

## Use cases

Common use case filtering examples for Zoom include publicly shared files that are not passcode-protected:

`Sharing status includes Publicly`

`Passcode protection equals Not protected`

{% hint style="info" %}

* Zoom recordings that are shared on the cloud but **not** passcode-protected **increase** the risk of data exfiltration from your organization.&#x20;
* You can leverage DoControl workflows to detect Zoom recordings that are **not** passcode-protected.
  {% endhint %}

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FSwRP0OIcgw6gyXKM0ENJ%2FZoom%20use%20case.png?alt=media&amp;token=e259a007-a1aa-450a-9944-c7a431fd86db" alt=""><figcaption></figcaption></figure>

## Zoom passcode protection limitation

For DoControl to detect shared recordings as passcode-protected, you must enable the passcode protection security setting across the organization **before** you generate a recording.&#x20;

If you don't apply this security setting on the organizational level, or you apply the setting **after** the recording was generated, the Zoom API will **not** detect the recording as passcode-protected.

This limitation affects the way Zoom recordings are displayed in DoControl.

{% hint style="info" %}

* To maintain data integrity, we recommend enabling the Zoom passcode protection setting across your organization.
* Even after you enable this setting, users can still change or remove the passcode.
  {% endhint %}

### CIS compliance for passcode protection

If your organization is CIS-compliant, you are required to ensure that **passcode access to shared cloud recordings** is enabled.

{% hint style="success" %}
You can confirm if your organization passes this security check within DoControl's [Misconfiguration](https://app.docontrol.io/misconfigurations?misconfigurations.filters=JTVCJTdCJTIyYXBwJTIyJTNBJTdCJTIyb3BlcmF0b3IlMjIlM0ElMjJJTiUyMiUyQyUyMnZhbHVlJTIyJTNBJTVCJTIyWk9PTSUyMiU1RCU3RCU3RCUyQyU3QiUyMnNlY3VyaXR5Q2hlY2slMjIlM0ElN0IlMjJzaW5nbGUlMjIlM0ElN0IlMjJvcGVyYXRvciUyMiUzQSUyMkNPTlRBSU5TJTIyJTJDJTIydmFsdWUlMjIlM0ElMjJyZXF1aXJlJTIwcGFzc2NvZGUlMjIlN0QlN0QlN0QlNUQ%3D) module.
{% endhint %}

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F0AOBFSXM6lVLk3GbPOOd%2FCIS%20require%20passcode.png?alt=media&amp;token=33dd2221-ae98-4e50-b4e2-955ba1a3b2d0" alt=""><figcaption><p>DoControl's SPM misconfiguration module shows if this security check passes compliance standards</p></figcaption></figure>

## Zoom recording data

Click a specific Zoom recording in the inventory to view its recording metadata.

View data points for these Zoom recording parameters:

<table><thead><tr><th width="288.84375">Zoom parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Zoom meeting</strong></td><td>Name of Zoom recording</td></tr><tr><td>Sharing status</td><td><p>How Zoom recording is shared:</p><p>Publicly, internally, none </p></td></tr><tr><td>Host</td><td>Email of host who initiated the Zoom meeting</td></tr><tr><td>Start time</td><td>Date and time when Zoom recording began</td></tr><tr><td>Registration needed</td><td><ul><li><strong>Yes</strong> - Zoom requires users to authenticate before viewing the recording. </li><li><strong>No</strong>- Zoom does not require users to authenticate before viewing the recording. This setting might not be accurate since global system settings override the file setting, so registration for this recording is actually required.</li></ul></td></tr><tr><td><strong>App</strong></td><td></td></tr><tr><td>Passcode-protection</td><td>If Zoom recording has a passcode: Yes or No</td></tr><tr><td>Downloadable</td><td>If Zoom recording can be downloaded: Yes or No</td></tr><tr><td>Recording files</td><td><p>Download any files associated with the recording:<br></p><ul><li><strong>Audio only</strong> - Download an audio transcript of the recording</li><li><strong>Shared screen</strong> - Download image of shared screen</li><li><strong>Active speaker</strong> - Download recording with focus on the active speaker</li></ul></td></tr><tr><td>Meeting participants</td><td>Names and emails of Zoom meeting participants</td></tr><tr><td>Events</td><td>View all events associated with this Zoom recording</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.docontrol.io/docontrol-user-guide/saas-data-monitoring/inventory/inventory-assets/zoom-recordings.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.