> For the complete documentation index, see [llms.txt](https://docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intersectmbo.org/intersect-knowledge-base/cardano-facilitation-services/cardano-development/cardano-security-and-incident-response.md).

# Cardano security and incident response

Intersect facilitates Cardano's incident response capability through a structured framework of policies, roles, and processes maintained by its Security Council.

Intersect, in conjunction with its steering committees and executive, appoints the Security Council, which reports to the Technical Steering Committee. The Security Council oversees a security policy on behalf of ecosystem, manages incident response, and coordinates with contributing organizations when issues arise, across the repositories under its stewardship. It operates through a defined set of roles: a Security Manager who receives and triages reports, Responders who are the directly responsible individuals for resolving specific issues, and Insiders — vetted contributors granted access to sensitive information on a need-to-know basis. This structure is designed to contain sensitive information while enabling a fast, coordinated technical response.

Intersect also operates a Bug Bounty Program to encourage responsible disclosure of vulnerabilities before they can cause harm.

For extreme scenarios, Intersect's Security Council will invoke CIP-135, Cardano's formal disaster recovery framework. CIP-135 defines procedures for situations where the protocol's built-in recovery mechanisms are insufficient. The framework is exercised regularly through fire drills on the SanchoNet testnet. It was held on standby during the November 2025 chain partition incident. However, it was not needed, as the network recovered through coordinated node upgrades.

Further reading:

[OSC security policy](https://opensourcecommittee.docs.intersectmbo.org/policies/security-policy)

[TSC Security Council](https://technicalsteeringcommittee.docs.intersectmbo.org/about/security-council)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intersectmbo.org/intersect-knowledge-base/cardano-facilitation-services/cardano-development/cardano-security-and-incident-response.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.