> For the complete documentation index, see [llms.txt](https://docs.defguard.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.defguard.net/2.1/in-depth/architecture/security-concepts.md).

# Security concepts

Defguard's **fundamental secure processes**:

* Secure remote user enrollment (self-service)
* User self-service to manage their own data, change passwords, add/remove VPN devices, connect securely to networks
* For administrators to easily setup, manage and monitor multiple VPN networks (with access control) to provide a secure connection to applications that should not be visible on the internet
* Deploy an Identity Provider to have one place to manage all users
* That Identity Provider should provide SSO functionality to enable users to log in to all systems with one login/password
  * Have 2FA/MFA functionality to harden security
* Setup YubiKey Hardware keys to enable the best 2FA security, secure SSH login with private keys on a secure hardware
* Integrate all your systems with API, and Webhooks (to access Defguard functionalities or users' 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, and the optional `goal` query parameter:

```
GET https://docs.defguard.net/2.1/in-depth/architecture/security-concepts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.