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

# Security and trust index

### Choose a product security path

This page routes readers to product-specific security evidence. It does not replace a product threat model, audit page, or release record.

| Product                  | Start here                                                                                                                    | Use it to review                                                                                                                                               |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| CBTC                     | [CBTC security](/cbtc-1/concepts-and-reference/security.md)                                                                   | Bitcoin custody, Attestor verification, Canton authorization, package integrity, client integration, reserve evidence, and operational controls.               |
| Decentralization Manager | [Decentralization Manager security architecture](/decentralization-manager/operations-and-reference/security-architecture.md) | Operator authentication, Canton rights, peer identity and transport, persistent state, DAR handling, governance controls, deployment boundaries, and recovery. |

### Evaluate security evidence

Review the complete control system, not one claim or report.

1. **Architecture and trust boundaries.** Identify protected assets, privileged actors, data flows, external dependencies, and the boundary between product controls and operator responsibilities.
2. **Source and supported release.** Match documentation, source code, packages, images, and configuration to an Engineering-approved release. A commit or repository review baseline is not automatically a supported production release.
3. **Controls and configuration.** Confirm authentication, authorization, key and secret handling, network exposure, package provenance, monitoring, backup, recovery, and change control for the deployed environment.
4. **Independent review.** Match every audit report to the reviewed commit, component scope, exclusions, findings, remediation status, and supported release.
5. **Product-specific evidence.** For CBTC, review custody and reserve evidence separately. For Decentralization Manager, review governance, peer, deployment, and operator controls separately.
6. **Known limitations and incidents.** Check current known issues, unsupported versions, unresolved findings approved for disclosure, and incident notices.
7. **Integrator responsibilities.** Verify the application configuration, credentials, party rights, package versions, inputs, retries, logs, and support process. Product controls cannot correct an authorized command with incorrect inputs.

### Product evidence

#### CBTC

* [CBTC architecture and trust boundaries](/cbtc-1/concepts-and-reference/architecture-and-trust-boundaries.md)
* [CBTC Attestor Network and FROST](/cbtc-1/concepts-and-reference/attestor-network-and-frost.md)
* [CBTC Proof of Reserve](/cbtc-1/concepts-and-reference/proof-of-reserve.md)
* [CBTC compatibility and release notes](/cbtc-1/concepts-and-reference/compatibility-and-release-notes.md)

#### Decentralization Manager

* [Decentralization Manager architecture overview](/decentralization-manager/concepts-and-development/architecture-overview.md)
* [Decentralization Manager authentication and operator roles](/decentralization-manager/operations-and-reference/authentication-and-operator-roles.md)
* [Decentralization Manager audit and design acknowledgements](/decentralization-manager/operations-and-reference/audit-and-design-acknowledgements.md)
* [Decentralization Manager backup, recovery, and mesh upgrades](/decentralization-manager/operations-and-reference/backup-recovery-and-upgrades.md)
* [Decentralization Manager compatibility, releases, and troubleshooting](/decentralization-manager/operations-and-reference/compatibility-releases-and-troubleshooting.md)

### Audits

Each audit entry states:

* Product and reviewed component.
* Report date and auditor.
* Reviewed commit, package, image, or release.
* Included and excluded components.
* Findings and auditor suggestions.
* Remediation status and the release that contains each approved fix.
* Link to the approved immutable report.

An audit is evidence about reviewed components at a point in time. It is not a guarantee that every deployment, configuration, integration, or later release is secure.

### Canton privacy

Canton uses configurable sub-transaction privacy. Entitled parties see the contract data required for their transactions.

This boundary does not make every connected system private. Bitcoin transactions remain visible on Bitcoin. Identity providers, participant infrastructure, application databases, logs, analytics, monitoring, support exports, and other external systems have separate access and retention controls. Operators and integrators must protect those systems according to their own requirements.

### Report a vulnerability

Use one approved private security channel. Do not disclose an unpatched vulnerability through a public issue, discussion, pull request, community channel, or support thread.

Include:

* Affected product, version, commit, package, or image.
* Deployment form and environment.
* Reproduction steps or a safe proof of concept.
* Potential impact and affected assets.
* Supporting logs or evidence with secrets and personal data removed.
* Safe contact details and any disclosure constraints.

Use the private reporting route listed for the relevant product. That route provides the current contact, acknowledgement target, response expectations, and coordinated-disclosure process.

### Next step

👉 **Choose the relevant security review:** [CBTC security](/cbtc-1/concepts-and-reference/security.md) or [Decentralization Manager security architecture](/decentralization-manager/operations-and-reference/security-architecture.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 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.bitsafe.finance/security-and-trust/security-and-trust-index.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.