> 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/getting-started/security-checklist.md).

# Security checklist

This security checklist for Devolutions Server outlines guidelines for Windows Authentication, encrypted SQL connections, and securing the web server with SSL.

To achieve the highest level of security, you should adhere to the following guidelines.

Feel free to go over [Devolutions Server security hardening](/server/getting-started/security-checklist/devolutions-server-security-hardening.md) for more security mesures.

{% hint style="danger" %}
These recommendations are valid ONLY if the Devolutions Server instance is hosted on an intranet EXCLUSIVELY. You must involve a person with knowledge of Internet security to safely host any application on the Internet. You need to protect the site from Denial of Service attacks using an appliance or a security module that is external to Devolutions Server.
{% endhint %}

### General

* Use Windows Authentication exclusively.
* Ensure all LDAP communication uses [LDAP over SSL](/server/getting-started/security-checklist/ldap-over-ssl-ldaps.md).

### SQL Server

* Enable only the ***Windows Authentication Mode***.
* Create a domain account that will be used to create the database (VaultDBOwner), as well as another account that will be used by the web server to connect to the database (VaultDBRunner). The latter must have only the minimal set of permissions to perform its tasks.
* Communicate ONLY through an encrypted connection, please see [Encrypting Connections to SQL Server](/server/getting-started/security-checklist/encrypting-connections-to-sql-server.md).

### Web Server

* Configure the application pool to use domain credentials. This account will be added to the SQL Server as a login and be granted only the permissions that are needed (VaultDBRunner).
* Serve content through SSL (https). See [Configure SSL](/server/knowledge-base/how-to-articles/configure-ssl.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/server/getting-started/security-checklist.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.