> 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/technical-library/nl/zakelijke-services/zoom-contact-center/zoom-customer-experience/overview/security-standards.md).

# Beveiligingsnormen

De volgende secties schetsen de beveiligingsstandaarden van Zoom voor het web, realtime media en ondersteunde integraties.

### Web

Alle gebruikersverbindingen met de Zoom-website gebruiken TLS 1.2- of 1.3-encryptie en PKI-certificaten uitgegeven door een vertrouwde commerciële certificaatautoriteit. De sterkte van de encryptie en de specifieke coderingsalgoritmen die voor verbindingen met de website worden gebruikt, zijn afhankelijk van de Browser die wordt gebruikt om de locatie te openen en van de resultaten van de onderhandelde gemeenschappelijke encryptiemethode.

### Realtime media

Zoom contactcenter realtime media (audio, video en scherm delen) wordt beschermd met 256-bits AES-GCM-encryptie tussen ondersteunde Zoom-clients en binnen de datacenters van Zoom. Gesprekken die via PSTN verlopen, vallen onder de discretie van de onderliggende aanbieder en zijn mogelijk niet versleuteld.

### Integraties

Alle integraties van derden met Zoom contactcenter moeten TLS 1.2- of 1.3-encryptie ondersteunen.


---

# 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://library.zoom.com/technical-library/nl/zakelijke-services/zoom-contact-center/zoom-customer-experience/overview/security-standards.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.