---
title: "Security"
description: "How Outpost is built and operated. Identities, encryption, audit trails, and what each tier can and cannot see."
url: "https://support.outpostplatform.com/security/"
product: "platform"
type: "concept"
status: "stub"
ai_summary: "Overview of Outpost security. Covers the identity model for endpoints and people, mutual TLS between the Agent and Depot, encryption of sensitive fields at rest, tamper evident audit chains, what each tier can see, and how to report a vulnerability."
source: "https://gitlab.com/outpostplatform/docs/-/edit/main/src/content/docs/security/index.md"
license: "CC BY 4.0"
---

# Security

Outpost manages the machines an organisation runs on, so the question of what it
can see and who can make it act is the first one worth answering. This section
sets out the identity model, what is encrypted, what is audited and where the
boundaries between the tiers are. It is for a security reviewer, and for the
administrator who has to answer one.

<!-- TODO: write this page against the concept template.

Sections:

- The threat model, stated plainly: what Outpost defends against and what it
  does not.
- Identity: how an endpoint proves who it is, and how a person does.
- Transport: the connection between the Agent and Depot, and how it is
  authenticated in both directions.
- Encryption at rest, and which fields are encrypted rather than the whole
  database.
- Audit: what is recorded, and why parts of it are tamper evident.
- What each tier can see, as a table, including what leaves your
  infrastructure and what never does.
- Revocation: retiring an endpoint and removing a person's access.
- The build: signing, reproducibility and the cryptographic build flavour.
- Reporting a problem, linked to the reporting page.
-->

Follow the [concept template](https://gitlab.com/outpostplatform/docs/-/blob/main/templates/concept.md).