A runbook for the first hours that keeps its own log INCIDENT
In an incident the steps are known; the record is what never gets kept, because everyone is busy doing the incident. This runs the playbook and logs the run: times, decisions, evidence hashes and actions.
The incident
Where it stands
The steps
Actions
The timeline
The record
SHA-256 of everything above:
Questions people ask about INCIDENT
What playbooks are built in?
Six of the situations that need the first hour handled well: a device seized or found, a device or account that may be compromised, a cover identity that may be blown, a lost or stolen device, a phishing or social-engineering attempt, and a personal-data exposure. Each has its steps grouped into the phases they belong to, in a sensible order.
Are the steps official procedure?
No. They are a sound default order to work from, not law or your organisation’s policy, and they say so. Where your own procedure differs, follow it; the value here is that the record of what was actually done is kept as you do it, which is the thing that is otherwise never captured at the time.
How does hashing evidence work?
A step that preserves something offers to hash a file. The SHA-256 is computed here in the browser and recorded against the step with the file’s name and the time, so the exhibit can later be tied to the moment it was taken. The file itself is never stored in the tool.
What is the timeline?
Every timestamped thing in one place, in order: the declaration, each step as it was ticked or skipped, and each action as it was closed. It is assembled for you, because reconstructing the order of events afterwards from memory is exactly what the review cannot rely on.
Where is it kept?
In this browser only. Seal the record with a digest, export it, and clear it from the browser once it is filed. Related: BREACH runs the notification clock for a data breach, CHAIN keeps the continuity record for an exhibit, and RENDEZVOUS holds the extraction plan a blown cover needs.
Doing this often? The OBSCURA Sovereign Suite keeps the incident log with its timeline, and runs tabletop exercises to rehearse the next one. On its own, US$2 a month; with everything else, US$5 a month or US$48 a year.