> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cloud/concepts/advanced-concepts/security.md). # Security Protect Devolutions Cloud with encryption, IP allowlists, and a security dashboard that flags weak passwords and unhealthy vaults. Security in Devolutions Cloud combines encryption, access control, and monitoring features to protect shared secrets and connections. The encryption service keeps cryptographic keys outside the main application, IP allowlists restrict which networks can reach the service, and the Security dashboard surfaces issues such as weak passwords and unhealthy vaults. Operationally, administrators use Audit, Logs, and password-focused reports to monitor usage, while password policies and PAM rotation policies enforce strong, regularly changed credentials. This combination helps teams satisfy compliance requirements by showing that privileged secrets are strongly protected, tightly controlled, and continuously monitored. #### Related topics * [Security dashboard](/cloud/web-interface/administration/configuration-and-security/security-dashboard.md) * [Encryption service](/cloud/web-interface/administration/configuration-and-security/access-and-authentication/encryption-service.md) * [Audit](/cloud/web-interface/reports/audit.md) --- # 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.devolutions.net/cloud/concepts/advanced-concepts/security.md?ask=&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.