> For the complete documentation index, see [llms.txt](https://tech.usual.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tech.usual.money/security-and-audits/monitoring-framework.md). # Monitoring Framework Our security operations provides 24/7/365 monitoring of the Usual protocol. This ensures that any potential issues or anomalies are detected and addressed promptly. ### Passive Monitoring This foundational level focuses on monitoring the critical components that form the backbone of our protocol's security: * **Critical Role Monitoring**: Continuous tracking of all accounts with elevated privileges within the system. * **Multisig Activity**: Real-time monitoring of all multisignature wallet activities to ensure proper authorization of significant actions. * **Key Event Tracking**: Vigilant observation of crucial events such as: * Changes in role assignments * Updates to proxy implementations * Administrative changes Any activity at this level triggers immediate notifications to our security team for verification and response. ### Active Monitoring This level involves monitoring the operational aspects of our protocol to detect any deviations from expected behavior: * **Contract State Changes**: Tracking significant state changes across all protocol contracts. * **Mechanism Monitoring**: Continuous oversight of key protocol mechanisms, including: * Collateral Backing Ratio (CBR) activations and deactivations * Pausing and unpausing of contract functionalities * Activities within the DaoCollateral and SwapperEngine contracts * **Threshold Alerts**: Notifications triggered by unusual transaction volumes, large token movements, or unexpected price fluctuations. Anomalies detected at this level prompt immediate investigation by our security and development teams. #### Automated defense mechanisms Our highest level of security involves automated circuit breakers that immediately pause contract operations in response to critical security events: * **Asset Protection**: Automatic pause triggers in response to suspicious movement of protocol funds * **Protocol Integrity**: Immediate response to unexpected changes in core protocol metrics, balances, and under collateralization. * **Access Security**: Detection and response to potential security access anomalies * **Smart Contract Safety**: Automated protection against suspicious contract interactions that could impact protocol security These automated defense mechanisms serve as the protocol's last line of defense, automatically pausing relevant contract operations when critical security thresholds are breached. This "circuit breaker" approach ensures the protocol can enter a safe state while our security team investigates and responds to potential threats. --- # 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://tech.usual.money/security-and-audits/monitoring-framework.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.