Skip to content

Write it before you need it

Incident Response Plan
Development & Review

We build or review your incident response plan around the people who will use it under pressure: who declares an incident, who calls counsel and the insurer, who talks to customers, and who decides on shutdown. The result follows NIST SP 800-61 Rev. 3 and reads like instructions your team can follow at three in the morning.

From binder to working plan

A plan people
actually open.

The plan follows NIST SP 800-61 Rev. 3, which ties incident response to the NIST CSF 2.0 functions. We start from your current plan if one exists, interview the people named in it, and test the draft in a walkthrough before it is final.

Phase 01 · Discovery

Learn how your organization would really respond.

A gap list comparing your current plan, contracts and tooling with how incidents actually unfold.

  • Read the existing plan, policies, cyber insurance policy and major vendor contracts.
  • Interview IT, legal, communications and executive leadership.
  • Confirm what logging, backups and outside help you can count on.

Phase 02 · Roles & authority

Decide who decides, before it matters.

A roles and authority matrix naming who declares, who approves and who speaks.

  • Define severity levels and who can declare each one.
  • Set decision rights for shutdown, ransom questions and disclosure.
  • Name a backup for every role, with contact details kept outside your main systems.

Phase 03 · Plan & playbooks

Write the plan, then the playbooks that sit under it.

A plan and scenario playbooks written as steps, with checklists for the first decisions.

  • Draft the core plan to NIST SP 800-61 Rev. 3.
  • Write playbooks for ransomware, business email compromise and data theft.
  • Add notification paths for counsel, the insurer, law enforcement and regulators.

Phase 04 · Walkthrough

Test the draft with the people named in it.

A revised plan that reflects what the walkthrough exposed.

  • Walk a realistic scenario through the plan with the response team.
  • Find the steps nobody owns and the contacts nobody has.
  • Revise the plan before it goes for approval.

Phase 05 · Hand over

Hand over a plan your team owns.

An approved plan, a review trigger list and a short list of follow up work.

  • Present the plan for leadership approval.
  • Set review triggers: major changes, new vendors, or any real incident.
  • Recommend a tabletop exercise to keep the plan current.

Learn how your organization would really respond.

A gap list comparing your current plan, contracts and tooling with how incidents actually unfold.

  • Read the existing plan, policies, cyber insurance policy and major vendor contracts.
  • Interview IT, legal, communications and executive leadership.
  • Confirm what logging, backups and outside help you can count on.

Key benefits

A plan that works when the network does not.

Decisions made in advance

Shutdown authority, ransom questions and disclosure calls are settled in the plan ahead of time, so nobody is debating who is in charge while the incident spreads.

Built on current NIST guidance

The plan follows NIST SP 800-61 Rev. 3 and maps to NIST CSF 2.0, which gives auditors, insurers and customers a standard they recognize when they ask to see it.

Counsel and insurer written in

Notification paths for your lawyers, your cyber insurer and law enforcement are part of the plan, along with the evidence and privilege steps counsel will expect from the start.

What you get

What lands on
your desk.

Everything the response team needs, in the form they will reach for during an incident.

The document

The incident response plan

Scope, severity levels, roles and authority, response phases, communication paths and evidence handling, written to NIST SP 800-61 Rev. 3 and approved by your leadership team.

The working file

Playbooks and contact sheet

Scenario playbooks as step checklists, plus a contact sheet for internal roles, counsel, insurer and vendors, built to be printed and stored away from your network.

The conversation

The walkthrough session

A working session with the response team that runs a realistic scenario through the draft plan, finds the gaps, and agrees the changes before the plan goes for approval.

Client case studies

Real engagements.
Documented outcomes.

YHB | CPAs & Consultants testimonial

In their words

"ForgePath has become a trusted security partner for YHB. Their team understands how a CPA firm operates and has helped us build a security program that’s both practical and sustainable."

Cyrus Kapadia
Chief Technology & Information Officer, YHB | CPAs & Consultants

Trusted by industry leaders.

Before we start

Questions about
the plan.

Straight answers from the practitioners who do the work. If yours is not here, ask us directly.

Not necessarily. We review what you have against NIST SP 800-61 Rev. 3 and against how your organization actually works. If the plan holds up, we fix the gaps. If it describes a company you no longer are, we rewrite it.

Interviews with IT, security, legal, communications and an executive sponsor, plus copies of your current plan, cyber insurance policy and major vendor contracts. The walkthrough needs the people who would respond to a real incident.

The plan follows NIST SP 800-61 Rev. 3 and maps to NIST CSF 2.0, which auditors and insurers recognize. We read your policy's incident terms so the plan reflects them. Acceptance is their decision, so we do not promise it.

No. This service builds the plan. If you want a senior responder to lead a real incident, that is our Incident Response Leadership service, scoped separately. If you have an active incident now, go to our Under Attack page.

Ready?

Bring us
the problem.

One conversation with a senior practitioner who has carried this responsibility before. We will tell you what we would do, and whether it is us.