Incident Readiness and Recovery

Know who decides, what happens first and how you get back to work, and rehearse it.

Already have an IT provider? Here's how we work together.

A design firm, Friday evening

The weekend restore

The challenge. On Friday at six, the firm’s file server stops opening drawings and a note appears on the screen. The partners call the IT provider, who is willing but asks who is allowed to approve shutting down the network, whether the backups are good, and whom the firm has to tell. Nobody has the answers written down.

The insight. A bad weekend is mostly a question of decisions made in advance. Recovery speed depends on three things: backups that have been restored on purpose, a short list of who decides what, and a record of which systems matter most and in what order they come back.

The decision. After the weekend, the partners decided to write the plan, test it, and give it a yearly date, rather than hope the next one would go better.

The action. We listed the firm’s systems in the order the business needs them, set a recovery time for each and wrote one-page roles for the partners, the IT provider and the office manager. The IT provider moved a backup copy somewhere the network cannot change it and ran a full restore, which we timed and recorded. We then ran a two-hour tabletop with the partners using a made-up Friday evening, and fixed the six places where the plan was unclear.

The result. The firm now knows how long its drawings take to come back, who calls whom first, and which notices it owes under its contracts and the law. The plan is shorter than before and has been used in rehearsal.

What Security Medic does

Incident response plan

Roles, first-hour steps, contact lists, decision points and the notice duties that apply to you, written to fit a small team.

Recovery planning

Systems ranked by importance, recovery times set, and backups (including a copy the network cannot change) restored on a schedule with the results recorded.

Tabletop exercises

A realistic scenario walked through with the people who would make the decisions, ending in a short list of fixes to the plan.

Coordination during an event

We help the client keep decisions and evidence in order while the IT provider leads the technical work. We do not give legal advice; the client’s counsel does.

Where this sits in the cycle

Every client goes through the same six steps, from a town office to a family at home. The Security Medic method

  1. 1. Govern
  2. 2. Design
  3. 3. Assess
  4. 4. Review
  5. 5. Conform
  6. 6. Improve
  • Govern. Who decides, what risk the firm accepts, and how long it can be without each system.
  • Design. The recovery design: backups, copies, and the order systems return.
  • Assess. A restore test and a tabletop that show what actually works.
  • Review. The fixes ranked and reported to leadership.
  • Conform. The IT provider builds the fixes; we check the result.
  • Improve. A yearly rehearsal, and a re-check whenever systems or people change.

The standards we draw on

The Respond and Recover functions of the NIST Cybersecurity Framework 2.0, NIST SP 800-61 Revision 3 for incident response, NIST SP 800-34 for contingency planning, and the notice rules that apply to the client, such as HIPAA, NYDFS Part 500 or New York’s breach notification law.

Insurance readiness →Cloud security →Training and coaching →

Getting ahead of it

Each new system, vendor or remote-access tool changes the plan. Put a plan check into the steps for adding any of them, and rehearse once a year.

Book a free 30-minute call about incident readiness

Tell us what you would need back first. We will talk through the plan and the test that would tell you the most.

Book a free 30-minute call