> For the complete documentation index, see [llms.txt](https://library.zoom.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://library.zoom.com/business-services/zoom-contact-center/zoom-customer-experience/overview/security-standards.md).

# Security Standards

The following sections outline Zoom’s security standards for the web, real-time media, and supported integrations.

### Web

All user connections to the Zoom website use TLS 1.2 or 1.3 encryption, and PKI certificates issued by a trusted commercial certificate authority. The strength of encryption and specific ciphers used for connections to the website depend on the browser used to access the site and the results of the common encryption method negotiated.

### Real-Time Media

Zoom Contact Center real-time media (audio, video, and screen sharing) is protected with 256-bit AES-GCM encryption between supported Zoom clients and within Zoom’s data centers. Any calls that traverse the PSTN are subject to the underlying carrier’s discretion and may not be encrypted.

### Integrations

All third-party integrations with Zoom Contact Center must support TLS 1.2 or 1.3 encryption.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://library.zoom.com/business-services/zoom-contact-center/zoom-customer-experience/overview/security-standards.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.