> For the complete documentation index, see [llms.txt](https://quantixfinance.gitbook.io/quantixfinance-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quantixfinance.gitbook.io/quantixfinance-docs/security-and-operational-resilience/incident-response.md).

# Incident response

Security is also a property of how the protocol is run. Changes to production systems and contracts follow a controlled process: reviewed before release, deployed deliberately, and — for sensitive on-chain changes — subject to the multi-signature and timelock constraints described above. Access to production and administrative functions is granted on least-privilege lines, tied to role, and removed when a role ends.

The protocol and its infrastructure are monitored continuously. On-chain activity across the pool, loan, collateral, and token contracts is watched for anomalies, and infrastructure is monitored for availability and intrusion, so unusual behavior is detected and investigated rather than missed.

Quantix depends on external providers for identity verification and wallet screening, and each is treated as a managed dependency rather than an afterthought: identity verification is performed by SumSub and wallet-level screening by AMLBot, both named here and in the sections covering their specific function so they can be assessed directly. Custody is handled through **SafeHeron**, an institutional-grade MPC custody provider, rather than through self-custodied hot wallets for protocol-controlled funds. Settlement itself — the actual movement and accounting of funds between participants — is performed by Quantix's own infrastructure rather than outsourced to a third party, which means settlement risk sits with the protocol's own systems and controls described throughout this section, not with an external counterparty.