From db410cdee94f76e88c27656494da8ee89f051441 Mon Sep 17 00:00:00 2001 From: Bastian Hofmann Date: Tue, 26 Aug 2025 16:19:52 +0200 Subject: [PATCH] Update qdrant-landing/content/documentation/cloud-security.md Co-authored-by: William Godfrey --- qdrant-landing/content/documentation/cloud-security.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qdrant-landing/content/documentation/cloud-security.md b/qdrant-landing/content/documentation/cloud-security.md index de3bfd049..e60e16ba4 100644 --- a/qdrant-landing/content/documentation/cloud-security.md +++ b/qdrant-landing/content/documentation/cloud-security.md @@ -16,7 +16,7 @@ Qdrant is committed to maintaining high standards of security and compliance. We ### Managed Cloud -All Qdrant clusters running in Qdrant Managed Cloud are running isolated from each other in hardened containers running unprivileged. Every paid cluster has its own dedicated resources ensuring stable performance and security. Every cluster is sealed off with strict network policies, ensuring that no other customer can access your data. Outbound network access is also restricted to prevent data exfiltration. +All Qdrant clusters running in Qdrant Managed Cloud are isolated from each other in hardened, unprivileged containers. Each cluster is sealed off with strict network policies, ensuring that no other customer can access your data, and outbound network access is restricted to prevent data exfiltration. Paid clusters are running on their own dedicated resources to ensure stable performance and further security. All storage volumes are encrypted at rest. [Premium customers](/documentation/cloud-premium/) can also bring their own encryption keys for storage volumes.