> For the complete documentation index, see [llms.txt](https://docs.ipor.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ipor.io/fusion-for-depositors/why-fusion/security-features.md). # Security Features ## Siloed Risk Management IPOR Fusion's modular architecture isolates risks within individual vaults, ensuring that potential losses in one vault do not affect others. Risks are siloed to the particular markets and assets a vault is connected with via Fuses and substrates. This design bolsters security by preventing risk spillover across the ecosystem, empowering investors to choose strategies that match their risk appetite. ## Balance Fuses Fusion's accounting uses [Balance Fuses](/build-on-fusion/developer-guide/balance-fuses.md). That means the vaults account for them self. While other vaults require "trust me bro" accounting fed from offchain by the curator, Fusion vaults known their own balance. ## Audits Fusion is [audited](/build-on-fusion/developer-guide/security-and-audits.md). ## Active Risk Monitoring To ensure ongoing security, the IPOR Fusion infrastructure supports Guardian roles that can be assigned to specialized security firms such as smart contract exploit detectors. These entities actively monitor onchain risks and can take immediate protective actions, such as pausing strategies if anomalies are detected. An [Atomist](/build-on-fusion/architecture-overview/what-is-an-atomist.md) could also delegate a special Alpha role to recall funds from external protocols to the vault in case of threats. Other risk modules can be built and customized, such as monitoring for things like asset depegs, economic risks, and more. This proactive approach reduces the likelihood of loss, reinforcing the integrity of vault assets. --- # 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.ipor.io/fusion-for-depositors/why-fusion/security-features.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.