Not urgent? [email protected]410 Lantern Street, Floor 3, Eastport, ME

§1 Case studiesIncident register / Sample data

Incident reports, client names removed
Six of 2,300 calls since 2017

Six calls.How eachone ended.

Median time to contain, these six
1 hr 9
Fastest 34 min, slowest 3 hr 10

Each one is our real report layout with a fictional client: what was hit, the findings by severity, how long containment took, and what changed after.

1
Critical
11
High
30
Low
Every finding across the six reports below. Clients are fictional.

§2 ReportsFilter by sector

§3 RegisterSix reports / Sample data

All six on one sheet.

Critical, High and Low counts as each report lists them. Open a row for the full timeline.

Report

Sector

C / H / L

Contained

Result

IR-2240

0 / 1 / 5

58 min

Tool removed, lines kept running

IR-2263

0 / 2 / 3

34 min

Payroll checked, no funds moved

IR-2276

0 / 1 / 7

1 hr 20

Account closed, VPN now asks for a second factor

IR-2291

1 / 2 / 5

3 hr 10

No ransom paid, dispatch back by Sunday

IR-2304

0 / 2 / 4

41 min

Payment held before it left

IR-2317

0 / 3 / 6

1 hr 52

Link cut first, both networks stayed up

Sample data. Clients are fictional.

§4 Public copyHow these are redacted

Incident responder on a desk phone at night, facing a dark monitor with green log lines and an attack path graph

What comes out, and what stays in.

A public copy is the client's own report with anything that points at them taken out. The client signs it off before we publish.

Stays

Every timestamp, severity and containment step

Stays

What the client fixed afterwards, and by when

Removed

Client names, sites, hostnames and addresses

Removed

Anything that points at a member of staff

§5 End of registerSix reports / Sample data

Read a full report before you ever need one.

24/7 incident line