Incident response · Under attack?

Think you have been breached? Call now.

The first hour decides how much you can prove and recover. Call or email first, then work through the checklist below while we get on the line.

If we cannot pick up, leave a message and send the email: incident messages come before everything else. Retainer clients, use the escalation route in your agreement.

The first hour

Do these now, in this order.

  1. Isolate. Do not power off.

    Disconnect affected machines from the network (unplug the cable, turn off Wi-Fi) but leave them running. Memory holds evidence that a shutdown destroys.

  2. Move to a channel the attacker cannot read.

    Assume email and chat are compromised. Coordinate by phone or a separate, clean account until we know what is affected.

  3. Call your cyber insurer’s breach line.

    Most policies set a deadline for notice, and many require approved (panel) firms. Calling late or out of panel can leave costs unpaid. We work alongside panel firms and your counsel.

  4. Bring in legal counsel early.

    Investigations directed through counsel can help keep findings privileged, and counsel decides who must be told and when.

  5. Preserve logs before they roll over.

    Export firewall, VPN, endpoint, email and cloud audit logs now, and pause any automatic clean-up. Some platforms keep logs for a limited time only.

  6. Start a written timeline.

    Who noticed what, when, and every action taken since. Investigators, insurers and regulators will all ask for it.

Notification clocks

Some deadlines start the moment you know.

The most common regimes for organisations in the US and EU. More than one can apply to the same incident, and each has its own trigger.

Breach and incident notification deadlines by regime
RegimeApplies toDeadline
GDPR / UK GDPRPersonal-data breach, any organisation handling EU or UK personal dataSupervisory authority without undue delay, within 72 hours of becoming aware where feasible
NIS2Significant incident at an essential or important entity in the EUEarly warning within 24 hours, notification within 72 hours, final report within one month
DORAMajor ICT-related incident at an EU financial entityInitial notification within 4 hours of classifying it as major (24 hours of awareness at most), then 72 hours, then one month
HIPAABreach of unsecured PHI at a covered entity or business associateIndividuals within 60 days of discovery; HHS within 60 days if 500 or more people, otherwise in the annual log
SECMaterial cybersecurity incident at a US-listed companyForm 8-K (Item 1.05) within four business days of determining it is material
NYDFS Part 500Cybersecurity incident at a New York-regulated financial services companySuperintendent within 72 hours; any extortion payment within 24 hours
US state lawsBreach of residents’ personal informationEvery state has one. Deadlines vary, and several are 30 days
How we help

From the first call to the last report.

Forensics and response are run under the founder’s direction, with vetted specialists engaged per incident, so one accountable lead holds the whole picture.

Contain

  • Ransomware and email-compromise containment
  • Scoping: which systems, accounts and data
  • Coordination with your IT team or MSP

Investigate

  • Root cause, scope and dwell time
  • Evidence handled to stand up with counsel, insurer and regulator
  • Clear findings, not a raw log dump

Report and recover

  • HIPAA/HITECH, GDPR and NIS2 notification analysis with your counsel
  • Board and insurer briefings
  • Fixes so it does not happen the same way twice
Not under attack today?

Rehearse the worst day before it happens.

A two-hour tabletop with your leadership and IT shows who decides what, and where the plan breaks, while it is still a rehearsal. An incident-response retainer puts named responders on call.

  • Founder-led
  • ISACA CISM
  • US & EU
  • Reply within one business day