> For the complete documentation index, see [llms.txt](https://docs.tydro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tydro.com/vi.-security/security-overview/technical-security/operational-security.md). # Operational Security ## Operational security Operational security protects the keys and the people who operate Tydro. This page describes the key management, access controls, and operational posture behind the protocol. ### Key management The keys that hold protocol authority are the highest-value target in any deployment, so they are protected accordingly. * Multi-party computation, so no single party holds a complete key and no single device is a point of failure. * Dedicated, hardened signing devices rather than general-purpose machines. * Multi-factor authentication across the systems that operate the protocol. * Encryption of sensitive material at rest and in transit. These controls sit behind the governance roles, so the powers in Smart contract security can only be exercised through this protected path. ### Access control The protocol runs on role-based access control. Each role has a defined set of actions and clear limits, authority is separated so no individual can act alone where it matters, and access follows least privilege. The same model extends to vaults, where curator and allocator permissions are explicit. See [Governance](/ii.-core-concepts/protocol-governance.md) and [Vault Curation](/iv.-tydro-institutional/institutional-overview/vault-curation.md). ### Custody Where assets are held through Kraken qualified custody, they sit with a regulated custodian under institutional controls for segregation and operations, which removes much of the self-custody risk institutions carry elsewhere. See [Qualified Custody](/iv.-tydro-institutional/institutional-overview/qualified-custody.md). ### Personnel and physical security Operational security extends to people. Tydro applies controls around the identities and physical security of key personnel. ### Incident response If an incident occurs, the Guardian can pause an affected market or the protocol while a response is carried out, then resume once the threat clears. See [Smart Contract Security](/vi.-security/security-overview/technical-security/smart-contract-security.md). For the residual risk these controls reduce, see [Custody and Counterparty Risk](#custody). --- # 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.tydro.com/vi.-security/security-overview/technical-security/operational-security.md?ask=&goal= ``` `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.