> 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/encrypting-connections-to-sql-server.md).

# Encrypting connections to SQL Server

Securing SQL Server traffic is critical to preventing credential interception and man-in-the-middle attacks. Devolutions Server should always communicate with SQL Server using encrypted channels.

### Enable SQL encryption

* In SQL Server Configuration Manager, enable **Force Encryption** under the SQL Server Network Configuration.

{% hint style="info" %}
Consult Microsoft's [Enable encrypted connections to the Database Engine](https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine?view=sql-server-ver15) article for detailed instructions.
{% endhint %}

### Use a valid certificate

* Install a trusted TLS certificate on SQL Server.
* Avoid self-signed certificates in production environments.
* Ensure the certificate includes the server’s FQDN and is issued by a recognized CA.

### Client-side verification

* After the SQL Server environment is properly configured, the only change required in Devolutions Server is to enable ***Use SQL Server encrypted connection*** in the ***Database*** – ***Advanced settings*** section of the instance settings.

### Compatibility considerations

* Legacy clients that do not support encryption may fail to connect.
* Perform testing before enabling **Force Encryption** in production.

### Compliance notes

Encrypted SQL connections align with requirements from standards such as PCI DSS and NIST, and should be considered mandatory for any environment handling sensitive authentication or vault data.


---

# 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/getting-started/security-checklist/encrypting-connections-to-sql-server.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.