Cybersecurity Incident Response Plan: Who Does What in an Attack
A cybersecurity incident response plan names who isolates systems, who decides on a ransom and who calls the insurer. This guide shows how to write, assign and test one before an attack.
A cybersecurity incident response plan names who can isolate systems, who handles a ransom decision, and who calls the insurer and breach counsel. It also tells your team how to communicate when company accounts are compromised. Assign a primary and an alternate, then test their authority before an attack forces the decision.
The executive accountable to the board needs more than a technical checklist. Your plan must give people authority to act when the network is unavailable and the facts are incomplete. A binder cannot make those decisions for you.
What Has to Be True in Each of the Six Phases?
NIST Special Publication 800-61 Revision 3 frames incident response through the Cybersecurity Framework 2.0 functions: Govern, Identify, Protect, Detect, Respond and Recover. The familiar six-phase lifecycle below remains a practical way to organize response work. Neither framework replaces named owners. IBM's Cost of a Data Breach research names phishing and stolen or compromised credentials as the two most prevalent initial attack vectors, so the account steps later in this plan matter as much as the hardware ones.
- Preparation means assigning authority. Name the plan owner, approve the decision tree and record where response tools and backups can be accessed if primary systems fail.
- Detection and analysis establish what happened. Define severity levels for your business and specify when a suspected incident requires escalation. Name an alternate if the decision-maker is unreachable.
- Containment limits the damage. Write numbered isolation steps and identify who can authorize and execute them.
- Eradication removes the attacker's access. Address compromised credentials and persistence mechanisms, rather than rebuilding infected machines alone.
- Recovery returns systems to operation. Validate backups and restored systems before reconnecting them to production.
- Post-incident activity corrects failures. Give each corrective action an owner and a due date.
Preserve evidence before wiping or rebuilding systems. Capture system images and retain logs with qualified technical support. That record helps establish how the attacker entered, what data was affected and which notification duties may apply.
Who Can Disconnect the Network, and Who Decides on a Ransom Question?
Authority to isolate systems and authority to consider a ransom demand are separate decisions. Name a primary and an alternate who can authorize isolation without waiting for a meeting. Assign ransom decisions to an executive, with legal advice and input from the insurer and finance.
The people stopping the spread should not wait for a payment discussion. Write containment actions as instructions with accountable owners:
- The designated technical responder isolates affected hosts, with a named alternate available if the primary cannot act.
- The identity administrator disables compromised accounts, including affected administrator or service accounts.
- The network lead blocks the specific ports or addresses identified during the response.
Confirm those people have the access needed to execute their assignments. A name in a document does not grant administrative access. A virtual CISO can maintain the decision tree and coordinate its approval; your organization must explicitly delegate operational authority. Total 360 Security's virtual CISO service includes incident response planning and cybersecurity program ownership.
Who Belongs on the Core Response Team Besides IT?
IT handles containment and restoration. Executives remain responsible for decisions about business interruption, spending and disclosure. Name a person for each function:
- Technical lead: directs containment and recovery.
- Legal counsel: advises on notification duties and privilege.
- HR: handles employee issues and staff communication.
- Communications: coordinates messages to customers and the public.
- Finance: evaluates financial exposure and spending approvals.
- Executive sponsor: makes business decisions and speaks for the company.
The executive owner should approve updates and review the roster after staffing changes. If an outside IT contractor is the only person who knows the plan, that contractor is a single point of failure. A virtual CSO can provide cross-functional security leadership and board reporting, while technical responders retain their assigned responsibilities.
How Does the Team Talk When Email and the Domain Are Compromised?
Assume company email and chat may fail together because they depend on the same login system. Establish communication that does not rely on that system:
- Maintain a call tree with personal mobile numbers rather than work extensions alone.
- Set up an encrypted messaging group in advance and confirm its access does not depend on compromised company accounts.
- Give the response team printed copies of essential contacts, including the executive owner's alternate.
Send a test message through each channel before relying on it. Check membership and phone numbers during plan reviews, and protect printed copies because they contain personal contact information.
When Must the Insurer and Breach Counsel Be Notified?
Many cyber policies require prompt notice of a suspected event. Late reporting can put coverage at risk, so do not assume the investigation must be complete before calling. Put the claim-reporting number and breach counsel's direct contact in the plan, outside any shared inbox.
Your policy determines the reporting trigger. Confirm its terms with your broker or carrier before an incident, then check the plan:
- Is the claim-reporting number current and accessible offline?
- Does breach counsel have a named contact and an alternate?
- Who makes the first call, and how will they distinguish confirmed facts from unanswered questions?
Correct missing contacts or unclear assignments before the next exercise.
Do not make a test claim-reporting call without arranging it with the carrier first.
How Should Texas Breach Notification Duties Be Built Into the Plan?
Texas breach notification requirements can include notice to the state attorney general. Have counsel confirm the current statutory threshold and deadline before recording them in your plan. Insurance reporting and statutory notification are separate obligations; completing one does not satisfy the other.
For a business holding records about people in more than one state, a Texas-only checklist may be insufficient. Ask counsel to map applicable requirements against your data inventory, including records vendors hold on your behalf. Assign responsibility for tracking deadlines and approving notices before an incident occurs.
How Often Should Tabletop Exercises Run, and What Must They Produce?
Run a tabletop at least annually, with more frequent exercises for high-exposure operations. Schedule one far enough before insurance renewal to correct the gaps it exposes. Walking through a ransomware scenario should produce a written action record:
- A dated description of each gap.
- One accountable owner for each correction.
- A retest date to verify the correction works.
Test decisions as well as technical procedures. Ask who authorizes isolation at 2 a.m., then make the team use the alternate contact route. Test how a ransom demand reaches the executive without delaying containment. Record where the exercise stalls rather than helping participants skip past the problem.
What Should a Blameless Post-Mortem Change?
After recovery, ask what the system allowed rather than stopping at who clicked. Examine the control that failed or the authority that was unclear. Assign each fix to an owner and keep it open until someone verifies it works.
Review the plan at least annually and after material changes to systems, vendors or staffing. A tested decision tree is more useful during an outage than a long document nobody has practiced.
At Total 360 Security, we run security programs across 13 risk domains, with board reporting. If your response plan lacks executive ownership, book a 30-minute consultation with Total 360 Security to discuss incident response planning within that operating model. You can also call 817-677-0515.
Frequently asked questions
Who has the authority to disconnect the network during an incident?
The plan should name a primary and an alternate with advance authority to isolate systems. Confirm they have the access and instructions to act without waiting for a meeting. Keep that authority separate from executive decisions about a ransom demand.
When must we notify our cyber insurance carrier and breach counsel?
Follow the reporting trigger and deadline in your cyber policy; many policies require prompt notice of a suspected event. Involve breach counsel early to assess legal duties while the investigation continues. Keep both contacts accessible outside company email.
How often should we run incident response tabletop exercises?
Run a tabletop at least once a year, and more often if your exposure warrants it. Schedule an exercise before insurance renewal with time to fix identified gaps. Record each gap, assign an owner and verify the correction through a retest.
How do we communicate if email and domain accounts are compromised?
Use an established channel that does not depend on company login credentials, supported by a mobile call tree and printed contacts. Set up and test the channel before an incident. Review access and membership whenever response personnel change.
What role does a virtual CISO play in incident response?
A virtual CISO can own incident response planning, coordinate tabletop exercises and track corrective actions. The role connects technical response with executive decisions and compliance obligations. Your organization still needs to approve decision authority and name the people who will execute the plan.
Total 360 Security provides virtual Chief Security Officer, vCISO, and Enterprise Security Risk Management programs for mid-market organizations. They design, run, and report security programs covering all 13 risk domains rather than just offering advisory decks or point solutions. The firm is Texas DPS-licensed with CPP, CISSP, and CISM credentials.
Serving Texas, California, Nevada, New Mexico.
More from the blog
10 min read
Identity Access Management Software: What to Govern First
A practical order for identity access management software: define privileged access, name an owner, inventory raw exports and review each quarter before buying a tool.
Read article7 min read
SOC 2 Audit: What Type II Requires and Who Owns Each Control
A SOC 2 audit is an independent CPA examination of your controls against the AICPA criteria. Here is what a Type II report requires, who owns each control and what evidence to keep.
Read article7 min read
Compliance Monitoring: What to Check Monthly and Quarterly
Compliance monitoring is the ongoing check that your operations follow the rules that apply to you. This guide sets a monthly evidence set, a quarterly sampling routine and clear ownership for every exception.
Read article