> 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/server/concepts/advanced-concepts-md/security.md).

# Security

Security in Devolutions Server combines hardened deployment practices with built in features for access control, encryption, and auditing. The security checklist and hardening guidance cover topics such as TLS configuration, database encryption, service accounts, and backup strategy, while the security dashboard highlights configuration gaps and recommended mitigations. (docs.devolutions.net)

On top of that, vault security levels, conditional access policies, multifactor authentication, and detailed logs help enforce least privilege and detect suspicious activity. Many teams periodically review the dashboard, implement suggested changes, and record accepted risks in an administrative vault to keep the security posture transparent.

#### Related topics

* [Devolutions Server security hardening](https://docs.devolutions.net/server/getting-started/security-checklist/dvls-security-hardening/)
* [Devolutions Server security dashboard](https://docs.devolutions.net/server/kb/knowledge-base/server-security-dashboard/)
* [System settings](https://docs.devolutions.net/server/web-interface/administration/configuration/system-settings/)


---

# 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:

```
GET https://docs.devolutions.net/server/concepts/advanced-concepts-md/security.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.