Every operator of consequence will eventually handle a security event. What distinguishes a mature operation is not the absence of incidents but whether the response is a prepared process with defined authority, or an improvisation under pressure by whoever is available.
SWSS maintains a standing incident response process owned by the SWSS Technology Team. This page describes what that process guarantees to a counterparty. It does not describe the procedures themselves, for the reason given at the end.
What the Process Guarantees
| Stage | What is assured |
| Detection | Infrastructure and services are observed continuously, and anomalous behaviour raises an alert into the response process rather than into a queue. Reports arriving from outside enter the same process at the same priority: see Reporting Vulnerabilities |
| Declared ownership | An incident has a single named owner with the authority to act, from the moment it is declared until it is closed. Response authority is not assembled during the incident |
| Containment before diagnosis | Limiting the reach of an event takes precedence over understanding it. A component whose integrity is in question is removed from a position of authority first and investigated afterwards |
| Settlement integrity is preserved | Consensus continues while a minority of the validator set is unavailable, so removing a component from the active set is a containment action that does not halt settlement. See BFTFA: Byzantine Fault Tolerant Finality Attestation |
| Recorded as it happens | Actions taken during an incident are recorded contemporaneously, so the account given afterwards is a record rather than a reconstruction |
| Review is mandatory | Every declared incident is reviewed after closure regardless of impact, and the review addresses why the condition was possible, not only how it was resolved |
What an Event Cannot Reach
The boundaries described in SWSS Ecosystem Security hold during an incident, which is the point of establishing them structurally rather than procedurally. An event affecting SWSS infrastructure does not confer authority over member holdings, because that authority is exercised by the member through SWSS App and does not exist in the affected domain. An event affecting one application does not confer authority over another. Containment is therefore bounded by the architecture before any responder takes an action.
Disclosure
Where an event affects counterparties, disclosure is co-ordinated: those affected are informed on a basis appropriate to the impact, and public description follows remediation rather than preceding it. Describing an unremediated weakness publicly converts a disclosure into an attack notice, which is the same reasoning applied to audit publication in Independent Assurance.
The procedures themselves are not published
Response thresholds, escalation paths, detection coverage and containment mechanics are not described on this page. A published response procedure tells an adversary what will be noticed, how quickly, and what will happen next, which is planning information, and of no use to a legitimate counterparty. Institutions requiring assurance over these controls should obtain it through a due diligence engagement with the SWSS Foundation, where it can be evidenced and appropriately scoped.