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

# Trust & Security Framework

NCC's security framework extends beyond smart contracts to cover governance, permissions, audits, risk control, oracles, asset isolation and Treasury management. The Trust & Security Framework is designed for long-term ecosystem collaboration. A multi-layered system of governance, auditing, risk control and infrastructure security.

## Multi-layered Security

Key contract upgrades, Treasury operations and asset-related permissions are managed through multi-signature and tiered permission systems. Roles in technology, operations, compliance, audit and governance have clearly defined permission boundaries, reducing single-point control and operational risk.

Smart contracts, cross-chain modules and core protocol components are subject to continuous auditing and monitoring. Oracle data sources, asset states and anomalous trading behavior are also monitored in real time by the risk-control system.

## Risk Response

When the system detects price anomalies, oracle data anomalies, liquidity volatility or asset-risk events, the risk framework can trigger alerts, parameter adjustments, temporary restrictions or protective mechanisms. Reducing systemic impact in extreme conditions.

The Trust & Security Framework is designed to make security part of ongoing ecosystem operation, not a one-time audit performed before launch.

As NCC integrates more assets, applications and partners, the security framework will continuously cover protocol upgrades, permission changes, fund flows, data-source quality and cross-chain interactions.

NCC's security governance is aligned with the Foundation structure. Key permissions, Treasury operations, asset-related decisions and protocol parameter adjustments are executed through traceable processes, uniting technical, governance and asset security in one system.


---

# 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://ncclabs.gitbook.io/ncc-docs/trust-security-and-compliance/trust-security-framework.md?ask=<question>&goal=<endgoal>
```

`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.
