> For the complete documentation index, see [llms.txt](https://city-protocol.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://city-protocol.gitbook.io/docs/vault-as-a-service/vault-architecture/security-governance-layer.md).

# Security governance layer

VaaS uses a security governance layer to reduce operational and key-person risk.

**The governance layer include:**

<table data-header-hidden><thead><tr><th width="216.046875">Control</th><th>Purpose</th></tr></thead><tbody><tr><td>3-of-5 Multisig</td><td>Prevents single-key compromise for sensitive governance actions.</td></tr><tr><td>Execution Timelock</td><td>Gives LPs and monitoring systems time to observe high-impact changes before they take effect.</td></tr><tr><td>NAV Signer Quorum</td><td>Requires multiple authorized parties to validate NAV updates.</td></tr><tr><td>Strategy Whitelisting</td><td>Restricts capital deployment to approved strategies and venues.</td></tr><tr><td>Emergency Pause</td><td>Allows deposits, withdrawals, allocation, or redemption to halt during extreme market or security events.</td></tr><tr><td>Role-Based Permissions</td><td>Assigns limited privileges to curators, strategy managers, signers, guardians, and operators.</td></tr></tbody></table>

These controls create a more professionally managed vault environment than an unrestricted contract or discretionary offchain account.