> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cymph.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Real Incident Handling and Coordination

> Handle a real incident in one place: agree in advance who decides and who gets called, open a war room, run the response under clear command and keep a complete record.

When a real incident starts, the procedure is rarely what fails first. Coordination is. Nobody is sure who is in charge. The analyst who is ready to isolate a production server does not know whether they are allowed to. The person who can approve it does not pick up, and nobody knows who to call next. Leadership asks for a status every ten minutes, and three weeks later the insurer asks for a timeline that has to be rebuilt from chat threads and memory.

Cymph answers those questions in two places. **Ownership & Escalation** is where a workspace writes down, before the incident, who takes each decision, how far the response team may go on its own and who gets called in what order. A **war room** is where the incident itself is handled: the people, the playbooks they execute, the evidence, the updates to stakeholders and a timestamped history of everything that happened. The two are connected, so the rules agreed in advance show up at the moment they matter.

This use case walks through the full loop:

1. [Agree who decides before the incident](#1-agree-who-decides-before-the-incident) with contacts, decision roles, the ownership matrix and escalation ladders, approved by the person accountable for them.
2. [Open a war room and establish command](#2-open-a-war-room-and-establish-command) with the right people, one incident commander and the right visibility.
3. [Run the response from the room](#3-run-the-response-from-the-room) by executing playbooks that stay attached to the incident.
4. [Take decisions on agreed authority](#4-take-decisions-on-agreed-authority) through the approval gate and the escalation ladder.
5. [Keep stakeholders informed](#5-keep-stakeholders-informed) with broadcasts and a promise of when the next one comes.
6. [Keep the record](#6-keep-the-record) of activity, evidence and communication, ready to export.
7. [Review and feed the lessons back](#7-review-and-feed-the-lessons-back) into the playbooks.

The mechanics of each feature are documented in [War Rooms](https://docs.cymph.io/key-features/war-rooms.md) and [Ownership & Escalation](https://docs.cymph.io/key-features/ownership-escalation.md). This page focuses on how to use them together when the incident is real.

> [!NOTE]
>
> War Rooms are a licensed feature. If the section does not appear in your navigation menu, your license does not include it. Contact us to enable it.

# Why ownership and escalation come first

The questions that stall a response are the same in every organisation, but who has to answer them differs:

| | Enterprise | MSSP |
| - | - | - |
| **Who decides** | Authority is spread across security, IT operations, legal, communications and the business. The person who can approve a shutdown is rarely in the SOC. | Authority is split between the provider and the customer. The provider's analysts act on systems they do not own. |
| **How far the team may go alone** | Usually unwritten. Analysts wait for an approval that nobody knew was needed, or act and are questioned afterwards. | Usually buried in a contract annex that nobody on shift has read, and different for every customer. |
| **Who to call** | An on-call list in a document that was last updated before the last reorganisation. | One contact list per customer, each in a different format, with numbers nobody has verified. |
| **What the workspace holds** | One matrix per business unit or environment, with the retainer, outside counsel and the insurer as external contacts. | One matrix per customer, with the customer's staff and advisers as external contacts and the provider's staff as Cymph users. |

In both cases the answer has to exist before the incident, be approved by the person accountable for it, and still be correct on the day. That is what step 1 sets up, and it is why this use case starts well before the first alert.

# 1. Agree who decides before the incident

Open **Workspaces**, select the workspace and choose the **Ownership & Escalation** tab. Build the four parts in order, because each one uses the one before it:

* **Contacts**: the people who can be named or called. Members of the workspace are added as Cymph users and follow their profile; a customer's staff, an incident response retainer, outside counsel or a cyber insurer are added as external contacts with up to three phone numbers in the order to try them.
* **Decision roles**: the positions that take decisions, such as *Client CISO* or *MSSP SOC shift lead*. Each role has one holder and one deputy. The matrix points at roles, never at people, so when someone changes job you name a new holder and everything that uses the role follows.
* **Ownership matrix**: one row per decision that may have to be taken, such as *Isolate a critical server*, *Shut down a production system* or *Notify the regulator*. Each decision names the role that takes it, the roles that are informed, and whether the **response team may act without approval**: **No**, **Out of hours only** or **Yes**.
* **Escalation ladders**: one per severity level, saying which roles to reach, in what order, and how long to wait before moving to the next one.

![Ownership Matrix](https://mintcdn.com/cymph/1MTV0IxKvgbDA5Dt/images/ownership_matrix.png?fit=max\&auto=format\&n=1MTV0IxKvgbDA5Dt\&q=85\&s=5bd83019897bd12e5ea337afb2b4ea1a)

Three things turn this from a document into something the response can rely on:

* **It is approved.** Export the matrix as a PDF, have it approved by the person accountable for the workspace's incident response (in an MSSP workspace, usually the customer's CISO), and record the **sign-off** with the approver, the date, the next review date and the signed copy as evidence. Executions and war rooms follow the rules of the latest sign-off. Replacing the holder of a role or correcting a phone number never needs a new one. See [Sign-off](https://docs.cymph.io/key-features/ownership-escalation.md#sign-off).
* **It is checked continuously.** Risk signals flag a decision nobody owns, a role without a deputy, a contact nobody can call, an external contact whose details have not been verified for 90 days, a ladder that stops after one step and rules that changed after they were approved. They appear on the tab's Overview and in the Readiness Overview on the home page. See [Risk signals](https://docs.cymph.io/key-features/ownership-escalation.md#risk-signals).
* **It is on the playbooks.** In the playbook editor, set the **Decision** field on the steps that call for one, for example *Isolate a critical server* on the step that takes a server off the network. This is what brings the agreed rule in front of the responder in step 4. See [Decisions on playbook steps](https://docs.cymph.io/key-features/ownership-escalation.md#decisions-on-playbook-steps).

![Decision Field in the Playbook Editor](https://mintcdn.com/cymph/ayzy-3qR-r22TdfT/images/ownership_editor_decision.png?fit=max\&auto=format\&n=ayzy-3qR-r22TdfT\&q=85\&s=1af8e86319c7235aca826fe90d08e113)

> [!TIP]
>
> If you run one workspace per customer or per business unit, define the roles, decisions and ladders once in **Organisation → Settings → Ownership & Escalation**. Every workspace takes them over with **Add organisation defaults**, and what is left per workspace is naming who holds each role, adjusting what differs and getting the result signed off. **Add standard decisions** gives you ten common incident decisions to start from. See [Organisation defaults](https://docs.cymph.io/key-features/ownership-escalation.md#organisation-defaults).

# 2. Open a war room and establish command

When the incident is declared, press **Start War Room**. Choose **Operational** as the purpose: it is set once, and every execution started from the room inherits it. Then give the room what it needs to be useful from the first minute:

* **Severity**, **incident type**, **affected assets** from the workspace inventory and **affected services**.
* **Participants**: members of the workspace and teams from your organisation.
* **One Incident Commander.** Every room has exactly one, and it cannot be started without one. Only the commander starts the room, moves it through its phases, sends broadcasts, archives it and gives roles to the others. Scribe, Comms Lead and Technical Responder say who does what. Command changes hands only by naming a successor, so a room is never without it.
* **A time target** for the incident as a whole, measured from the moment the room is started until it is resolved.

![Start War Room People](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_new_step3_people.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=e39efe83bdb71a667c8161e651f203e7)

The room is created in the **Preparing** state. Seat the people and attach what you already have, then the Incident Commander presses **Start the room** and the incident clock starts. From then on the room moves through the NIST incident response phases: Detection and Analysis; Containment, Eradication and Recovery; and Post-Incident Activity.

Two settings matter for who gets in:

* **Visibility.** A **Workspace** room can be opened by everyone with access to the workspace. A **Restricted** room is visible only to the people added to it, administrators included. Use it when someone in the workspace may be the subject of the incident. The executions started from the room follow its visibility.
* **Guests.** People from outside the workspace, such as the incident response retainer, outside counsel, the cyber insurer or a customer's representative, are added as guests of this room only, until a date you set. They read the room, upload files and log activity, and never see files labelled TLP:AMBER+STRICT or TLP:RED. See [Guests](https://docs.cymph.io/key-features/war-rooms.md#guests).

![War Room Page Overview](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_page_overview.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=e57f9a14e152f1bd8a784ae75d3aba32)

# 3. Run the response from the room

Press **Start an execution** and pick the playbook that covers the incident. The execution is linked to the room: it runs as Operational, follows the room's visibility, appears on the room's timeline, and its outcome lands in the Activity History. With **Add assignees to the war room** on, everyone who gets a step joins the room automatically, so the people doing the work and the people coordinating it are in the same place.

![War Room Executions](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_executions.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=f6ab8313606f487a57dcb073b878bd13)

From there the room answers the questions a coordinator keeps asking:

* **What is everyone working on?** The Executions card on the Overview shows each run with its status, who it is waiting on and for which step, its completion and its elapsed time against its own target.
* **What is mine?** Each participant's **My Tasks** tab lists the steps assigned to them across every execution of the room.
* **Are we on time?** The header shows the time left against the incident target, and the timeline shows the phases, the executions and their deadlines on one axis.
* **What happened outside Cymph?** **Log activity** records a host isolated by hand, a decision taken on a call or a finding from forensics, with a category and the time it actually happened.

The room thread on the right keeps the conversation next to the work instead of in a separate chat tool. See [The war room page](https://docs.cymph.io/key-features/war-rooms.md#the-war-room-page) and [Executions](https://docs.cymph.io/key-features/war-rooms.md#executions).

# 4. Take decisions on agreed authority

This is where the preparation of step 1 pays off. When a responder reaches a step that calls for a decision, Cymph applies the rule of the signed-off matrix:

* If the decision is pre-authorised (**Yes**), the step goes ahead and the execution records that it was pre-authorised. Nobody has to be found.
* Otherwise the **Approval required** dialog opens. It names the decision, the role that decides, and the holder and deputy with their phone numbers, so the responder can call them straight away.

![Approval Required Dialog](https://mintcdn.com/cymph/ayzy-3qR-r22TdfT/images/ownership_execution_approval.png?fit=max\&auto=format\&n=ayzy-3qR-r22TdfT\&q=85\&s=ee2a0ec7ba2c6771c1c387a43b8c16ab)

The responder then records on what authority the step goes ahead: **Approval obtained** from the holder or the deputy, with an optional note and evidence such as the approving e-mail; **Pre-authorised out of hours**, when the matrix allows it; or **Proceed without approval**, with a mandatory reason.

> [!NOTE]
>
> The gate is a soft gate. It never blocks the response: whoever may start the step may pass it. What it guarantees is that the authority each step went ahead on is on record, in the execution log, on the war room timeline and in the reports. See [The approval gate in executions](https://docs.cymph.io/key-features/ownership-escalation.md#the-approval-gate-in-executions).

When the person who decides does not answer, open **Escalation ladder** in the *About War Room* sidebar. It opens on the ladder for the room's severity and shows who to call next, their current phone number and how long to wait before moving on. The steps and waits are those of the latest sign-off; the people and numbers are always the current ones.

![Escalation Ladder in a War Room](https://mintcdn.com/cymph/ayzy-3qR-r22TdfT/images/ownership_warroom_ladder.png?fit=max\&auto=format\&n=ayzy-3qR-r22TdfT\&q=85\&s=0e8aef8ce056a65bbbcc2699b98ac89a)

> [!NOTE]
>
> Escalation ladders are a reference for the people handling the incident. Cymph does not page anyone or start a timer. Guests of a war room do not see the ladder.

For an MSSP this replaces the most uncomfortable moment of an incident: the analyst deciding at three in the morning whether the contract allows them to act. The customer agreed the answer in advance, and the record shows it was followed.

# 5. Keep stakeholders informed

People outside the room need to know what is going on without joining it. The Incident Commander sends a **broadcast** from the room: a subject and a message, through in-app notifications and, when your organisation has set them up, email and SMS. Recipients can be the participants, the guests, people and teams in your organisation who are not in the room, and external email addresses or phone numbers such as leadership, a customer's management, the insurer or a regulator.

![War Room Send Update Step 1](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_send_update_step1.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=21cf3a323d8ad743775d5908ed4124f3)

Each broadcast answers **When is the next update?** That answer is a promise. The room counts down to it, shows when it is overdue and notifies the lead of the room once when it is missed. Stakeholders who know when the next update arrives stop asking for one, and the team gets its time back.

Room moments such as the room being opened, a severity change or a phase change can also be announced in Slack and Microsoft Teams. See [Broadcasts](https://docs.cymph.io/key-features/war-rooms.md#broadcasts) and [Notification settings](https://docs.cymph.io/key-features/war-rooms.md#notification-settings).

# 6. Keep the record

Nobody has to write the timeline afterwards, because the room writes it while the incident happens:

* **Activity History** records who did what and when: the room being started and moved between phases, people added and named to roles, executions and their outcomes, step approvals, broadcasts and the entries people logged by hand. Entries are never edited or deleted; a correction is added as an amendment with a reason, and the original stays on the record.
* **Files** are the evidence locker. Every file gets a SHA-256 fingerprint at upload, a TLP level and a classification, and every upload, download and deletion is recorded as its chain of custody.
* **The matrix in force** is recorded when the room is started, so it is clear afterwards which version of the rules the team was working under.

![War Room Activity](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_activity.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=671ead76d1436c7aea2f911051659116)

**Export War Room** downloads the whole incident as one archive: a timeline report with the participants, the executions, the full activity history, the escalation ladders and the post-incident review; every file with an integrity list that states whether it is still exactly the file that was uploaded; a report per execution; and the room thread. It is suitable for the insurer, the regulator, auditors or, for an MSSP, the customer. See [Exporting a war room](https://docs.cymph.io/key-features/war-rooms.md#exporting-a-war-room).

# 7. Review and feed the lessons back

When the response is done and no execution is still running, the Incident Commander moves the room into **Post-Incident Activity**. This marks the incident as resolved, stops the incident clock and opens the post-incident review:

* **Summary**: what happened, what was affected, what the team did and how it was resolved. **Draft with Cymph AI** writes a first version from the room's activity history.
* **Impact**: affected systems and services, whether personal data was involved, business impact, downtime, and who was notified and when. This is the material for a regulatory final report.
* **Lessons**: root cause, what went well, what could be improved and lessons learned.

![War Room Review Tab](https://mintcdn.com/cymph/g6MtkyAYj2I9svLO/images/warroom_review_tab.png?fit=max\&auto=format\&n=g6MtkyAYj2I9svLO\&q=85\&s=83d64324206b6cde06dfd94c6ea8045a)

Then close the loop:

1. **Turn the review into playbook changes.** Ask [Cymph AI](https://docs.cymph.io/key-features/cymph-ai.md) about the room, for example "What should we learn from the ransomware war room?". The assistant reads the review together with the improvements recorded on the room's executions and proposes updates to the playbooks that were run, or a new playbook when none covered the incident. Every proposal is reviewed before it is applied. See [Turn operational context into better response](https://docs.cymph.io/use-cases/operational-learning.md).
2. **Fix the matrix.** Every step that went ahead with **Proceed without approval**, and every escalation that reached the wrong person, is a finding about the rules. Adjust the pre-authorisation, the role holders or the ladder, and have the changes signed off.
3. **Archive the room.** An archived room is read-only and keeps the version of the matrix that was in force. It can still be exported, and reopened if the incident comes back.
4. **Rehearse it.** Start the next room with the purpose **Exercising & Testing**. It behaves exactly like an operational room, so the team trains on the real tool, and everything it sends out is marked as an exercise. See [Test and train your response](https://docs.cymph.io/use-cases/test-and-train.md) and [Exercise rooms](https://docs.cymph.io/key-features/war-rooms.md#exercise-rooms).

A real incident is the hardest test your response will get. Agree who decides before it starts, handle it in one place under clear command, and come out of it with a complete record and better playbooks.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.