> 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/application-security.md).

# Application security

The contracts can be sound and a participant can still be harmed at the application layer. Quantix secures the marketplace interface, the services behind it, and the software supply chain that builds them.

Access to the application is wallet-based: participants authenticate by controlling their wallet rather than by a password Quantix stores, which removes an entire category of credential theft. Permissioned actions are enforced server-side and on-chain, not only in the interface, so the boundaries of a role cannot be bypassed by manipulating the front end. Third-party dependencies and the build pipeline are treated as an attack surface and are controlled accordingly, because a compromised dependency can undermine an otherwise sound application.

Front-end integrity is a specific priority for any on-chain application: a hijacked interface can ask a user to sign a malicious transaction even when the contracts are untouched. Quantix protects the interface and its distribution, and pairs that with the user-side habits described next, since the last line of defense is what a participant signs.