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

# Trust & Security

- [Trust overview](https://docs.algenta.ai/trust-and-security/overview.md): Who is responsible for what across Algenta's deployment modes, and exactly which parties ever see your data.
- [Governed execution](https://docs.algenta.ai/trust-and-security/governed-execution.md): The control statements behind every plan approval and execution — named denial codes, single-use approval binding, versioned receipts.
- [Data boundaries](https://docs.algenta.ai/trust-and-security/data-boundaries.md): Every outbound network call the engine can make is classified into one of five categories and gated by deployment mode — plus what the SSRF guard blocks unconditionally.
- [Audit and evidence](https://docs.algenta.ai/trust-and-security/audit-and-evidence.md): The audit log export carries a content hash you re-derive yourself — evidence you verify, not evidence you take on trust.
- [Identity and access](https://docs.algenta.ai/trust-and-security/identity-and-access.md): Four separate identity mechanisms, each scoped to one surface, none falling through to another.
- [Capability status](https://docs.algenta.ai/trust-and-security/capability-status.md): Every protocol surface and integration, labeled Available now, Validated integration, or In conformance testing — checked against the current code and tests, not restated from an announcement.
- [Protocol compatibility](https://docs.algenta.ai/trust-and-security/protocol-compatibility.md): MCP version negotiation, the Responses and Chat Completions surfaces, and the 12-scenario conformance suite's real results — 9 passed, 0 failed, 3 blocked with named reasons.
- [Architecture and trust boundaries](https://docs.algenta.ai/trust-and-security/architecture.md): Where the engine, your model, and your MCP clients run relative to each other — and the one boundary every deployment mode shares.
- [Evidence walkthrough](https://docs.algenta.ai/trust-and-security/evidence-walkthrough.md): The versioned execution-receipt envelope, the audited webhook-dispatch path, and the hash-verified audit export — three real artifacts, and an honest note on how they connect today.
- [Security questionnaire](https://docs.algenta.ai/trust-and-security/security-questionnaire.md): Answers to the questions a vendor security review actually asks — each one checked against this repository's code and tests, with the gaps stated as plainly as the controls.
- [Supply chain](https://docs.algenta.ai/trust-and-security/supply-chain.md): What's verifiable about an Algenta release today — SBOMs and a vulnerability scan per image — and what isn't yet, stated as plainly as what is.
- [Threat model](https://docs.algenta.ai/trust-and-security/threat-model.md): A public summary of what this engine defends against and how — asset by asset, control by control — without exploit-level detail that would only help an attacker.
- [Support policy](https://docs.algenta.ai/trust-and-security/support-policy.md): What support and long-term-support commitments exist today, and what is explicitly pending an owner decision rather than invented ahead of it.


---

# 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.algenta.ai/trust-and-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.