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

# Security Council Satuchain

The SATUCHAIN Security Council is responsible for coordinating security-critical decisions and incident response procedures that protect network integrity, users, and ecosystem infrastructure. The council exists to ensure that high-risk issues are handled with clear authority, minimal delay, and transparent operational discipline.

### Scope

The Security Council covers security matters related to:

* protocol and consensus safety
* validator operations and network availability
* critical infrastructure (RPC endpoints, explorer, and indexing)
* emergency mitigations for active exploitation or severe network instability
* coordinated vulnerability response and disclosure processes

### Responsibilities

* **Incident Response Coordination**\
  Lead triage, containment, mitigation, and recovery during security incidents.
* **Risk Assessment and Severity Classification**\
  Evaluate reported issues and determine priority, impact scope, and response requirements.
* **Emergency Actions**\
  Approve and execute time-sensitive mitigation steps when required to protect the network.
* **Patch and Upgrade Oversight**\
  Coordinate security patches, release timing, and upgrade readiness across operators.
* **Communication and Transparency**\
  Publish incident summaries and mitigation notes when appropriate, while avoiding disclosures that increase active risk.

### Operating Principles

* **Safety-first execution**\
  Protecting users and chain integrity takes priority over feature delivery.
* **Minimum necessary change**\
  Emergency actions must be limited to what is required to mitigate risk.
* **Reproducibility and auditability**\
  Security decisions should be documented and verifiable, with clear timelines and actions.

### Reporting Vulnerabilities

Security issues should be reported responsibly through an official channel defined by SATUCHAIN. Reports should include:

* affected component (node, RPC, explorer, contract, etc.)
* reproduction steps and expected vs actual behavior
* impact analysis (funds at risk, chain safety, denial of service, etc.)
* suggested mitigation (if available)

### Disclosure Policy

SATUCHAIN follows a coordinated disclosure process:

* acknowledge receipt of report
* triage and severity assessment
* patch development and validation
* coordinated release and operator rollout
* post-incident summary when safe to publish

### Notes

The Security Council’s role is operational and technical. It does not replace independent audits, secure development practices, or responsible operator behavior.