> 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/cbtc-1/concepts-and-reference/security.md).

# Security

[CBTC architecture and trust boundaries](/cbtc-1/concepts-and-reference/architecture-and-trust-boundaries.md)

### Security model

CBTC combines Bitcoin threshold custody, independent event verification, Canton authorization and privacy, versioned Daml packages, authenticated service integrations, and reserve evidence. No single control should be presented as the entire security model.

### Security layers

| Layer              | Primary control                                              | Review focus                                                  |
| ------------------ | ------------------------------------------------------------ | ------------------------------------------------------------- |
| Bitcoin custody    | FROST threshold signing across independent operators         | Key lifecycle, signing policy, recovery, and correlated risk  |
| Event verification | Attestor Network policy and evidence                         | Duplicate prevention, transaction validity, and authorization |
| Canton contracts   | Daml authorization and party rights                          | Package versions, choices, privacy, and migration             |
| Client integration | Authentication, least privilege, validation, and idempotency | Secrets, wrong-party risk, retries, and logs                  |
| Backing evidence   | Proof of Reserve and reconciliation                          | Scope, cadence, stale data, and exclusions                    |
| Operations         | Monitoring, change control, incident response, and support   | Ownership, escalation, and recovery testing                   |

### Integrator responsibilities

Integrators must verify parties and Bitcoin destinations, pin compatible releases, protect credentials, validate contract state, reconcile ambiguous submissions, and use approved support channels. CBTC infrastructure cannot protect an application that sends an authorized command with incorrect inputs.

### Privacy boundary

Canton limits contract visibility through sub-transaction privacy. Bitcoin transactions remain visible on Bitcoin. Application logs, support exports, and external systems can reveal information if operators do not protect them.

### Audits

Each audit report identifies the contracts, services, release tags, and dates within its scope. An audit is evidence about reviewed components at a point in time. It is not a guarantee that every deployment or future release is secure.

### Vulnerability reporting

Report suspected vulnerabilities through the private security contact listed in [Security and trust index](https://docs.bitsafe.finance/security-and-trust/). Do not post unpatched vulnerabilities in public issues. Include the affected release, impact, reproduction steps, and safe contact details.

### Known limitations

Check [CBTC compatibility and release notes](https://app.notion.com/p/CBTC-compatibility-and-release-notes-public-documentation-draft-d283a9ea18994f1293086ff4913dc7f4?pvs=21) for supported versions, operational dependencies, known issues, and applicable audit scope.

### Related pages

* [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 authentication](/cbtc-1/get-started/authentication.md)
* [CBTC compatibility and release notes](/cbtc-1/concepts-and-reference/compatibility-and-release-notes.md)
* [Security and trust index](https://docs.bitsafe.finance/security-and-trust/)

### Next step

👉 **Confirm the evidence and reporting path:** [Security and trust index](https://docs.bitsafe.finance/security-and-trust/).


---

# 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/cbtc-1/concepts-and-reference/security.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.