From 637746f2c0362c2f74972e8f3de8ebc6e1109a74 Mon Sep 17 00:00:00 2001 From: Bastian Hofmann Date: Tue, 26 Aug 2025 16:17:30 +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 9d6a0ad4f..6424b80bf 100644 --- a/qdrant-landing/content/documentation/cloud-security.md +++ b/qdrant-landing/content/documentation/cloud-security.md @@ -22,7 +22,7 @@ All storage volumes are encrypted at rest. [Premium customers](/documentation/cl Data in transit is protected with TLS. It is possible to restrict the [IP ranges](/cloud/configure-cluster/#client-ip-restrictions) that are allowed to access a cluster. -Infrastructure access is limited and audited according to the policies laied out in our [Trust Center](https://qdrant.to/trust-center). All infrastructure componets are regularly patched and updated to ensure security. +Infrastructure access is restricted and audited according to the policies described in our [Trust Center](https://qdrant.to/trust-center). All infrastructure components are regularly patched and updated to ensure up to date security. Access to Qdrant Cloud accounts can be configured with granular [Role-Based Access Control](/documentation/cloud-rbac/). [Premium customers](/documentation/cloud-premium/) can also enable Single Sign-On (SSO) with their identity provider.