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

# Kryptering af forbindelser til SQL Server

Kryptér SQL Server-forbindelser til Devolutions Server ved at aktivere Force Encryption, installere et gyldigt certifikat og konfigurere verifikation på klientsiden.

Sikring af SQL Server-trafik er afgørende for at forhindre opsnapning af legitimationsoplysninger og man-in-the-middle-angreb. Devolutions Server bør altid kommunikere med SQL Server via krypterede kanaler.

### Aktivér SQL-kryptering

* Aktivér **Force Encryption** under SQL Server Network Configuration i SQL Server Configuration Manager.

{% hint style="info" %}
Se Microsofts artikel [Aktivér krypterede forbindelser til Database Engine](https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-encrypted-connections-to-the-database-engine?view=sql-server-ver15) for en udførlig vejledning.
{% endhint %}

### Brug et gyldigt certifikat

* Installér et betroet TLS-certifikat på SQL Server.
* Undgå selvsignerede certifikater i produktionsmiljøer.
* Sørg for, at certifikatet indeholder serverens FQDN, og at det er udstedt af en anerkendt CA.

### Verifikation på klientsiden

* Når SQL Server-miljøet er konfigureret korrekt, er den eneste ændring, der kræves i Devolutions Server, at aktivere ***Brug krypteret SQL Server-forbindelse*** i afsnittet ***Database*** – ***Avancerede indstillinger*** under instansindstillingerne.

### Overvejelser om kompatibilitet

* Ældre klienter, der ikke understøtter kryptering, kan muligvis ikke oprette forbindelse.
* Test, før De aktiverer **Force Encryption** i produktion.

### Bemærkninger om efterlevelse

Krypterede SQL-forbindelser er i overensstemmelse med krav fra standarder som PCI DSS og NIST og bør betragtes som obligatoriske i ethvert miljø, der håndterer følsom godkendelse eller boksdata.


---

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