> 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/pam/da/concepts/dual-account-principle.md).

# Princippet om dobbelt konto

Princippet om dobbelt konto i Devolutions PAM adskiller daglige konti med lave privilegier fra administrative konti med høje privilegier for at begrænse risikoen for kompromittering.

I Devolutions PAM er **princippet om dobbelt konto** en bedste praksis, der øger sikkerheden ved at kræve, at privilegerede brugere arbejder med to forskellige [privilegerede konti](/pam/da/concepts/privileged-account.md). Den ene er en **konto med lave privilegier** til rutineopgaver som at læse e-mails og browse på nettet. Den anden er en **konto med høje privilegier**, der kun bruges til administrative handlinger, f.eks. at ændre systemindstillinger eller få adgang til følsomme ressourcer i infrastrukturen.

Denne adskillelse mindsker risikoen for kompromittering ved at begrænse eksponeringen af ophøjede privilegier under daglig brug. Hvis malware eller phishing kompromitterer kontoen med lave privilegier, kan angriberen ikke straks få adgang til kritisk infrastruktur.

I Devolutions PAM håndhæves dette princip ved at tildele specifikke roller og tilladelser til hver kontotype. Automatiserede arbejdsflows og adgangskontroller kan sikre, at ophøjede legitimationsoplysninger kun bruges, når det er nødvendigt, hvilket hjælper med at opretholde driftssikkerhed og [efterlevelse](/pam/da/concepts/compliance-reporting.md).

#### Aliasser for princippet om dobbelt konto

* Princippet om dobbelt identitet
* Konti med høje privilegier
  * Administratorkonto
  * Dash-konto

#### Relaterede emner

* [Roller og tilladelser (PAM) i Devolutions Server](/pam/da/pam-with-devolutions-server/pam-permissions.md)

#### Se også

* [Glossary of Common Privileged Access Management (PAM) Terms](https://blog.devolutions.net/2021/01/glossary-of-common-privileged-access-management-pam-terms/)
* [Need Cybersecurity Insurance? Then You Probably Need PAM, Too](https://blog.devolutions.net/2023/10/need-cybersecurity-insurance-then-you-probably-need-pam-too/)
* [Devolutions Academy – Make use of the dual account principal](https://internal-academy.devolutions.net/student/activity/2846797-make-use-of-the-dual-account-principle)


---

# 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/pam/da/concepts/dual-account-principle.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.