> For the complete documentation index, see [llms.txt](https://docs.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umh.app/management-console/security.md).

# Security

Access to the Management Console is decided in two layers: identity and company access first, then permissions within that company. [Authentication](/management-console/authentication.md) and [Users and Permissions](/management-console/users-and-permissions.md) cover how you set both up. This section covers the design behind them, for readers who have to sign off on it.

| Page                                                                           | Answers                                                                                 |
| ------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------- |
| [Threat Model](/management-console/security/threat-model.md)                   | Who this is designed to keep out, what it accepts as a risk, and what it does not cover |
| [Shared Responsibility](/management-console/security/shared-responsibility.md) | Which parts of security are ours and which are yours                                    |
| [Compliance](/management-console/security/compliance.md)                       | How the controls map to OWASP, NIST and IEC 62443, including where they fall short      |

Security on the instance itself is separate, because the instance runs on your hardware and inside your network. See [umh-core Security](/production/security/deployment-security.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.umh.app/management-console/security.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.