Ransomware playbooks must include OFAC sanctions screening before any payment. Learn the three legal functions every incident response playbook must serve.
Incident Response Playbooks: Write Out Your Game Plan
The ransomware playbook sitting on most general counsel’s servers has one critical omission: it does not tell anyone whether the ransom payment is legal.
Incident response playbooks are the operational layer of a legal compliance program. A playbook for ransomware, cloud breach, or insider threat attack specifies the sequence of decisions, notifications, and containment steps the response team will execute when the incident occurs. From a legal perspective, the playbook performs three distinct functions: it establishes the standard of care the organization held itself to before the incident, it creates a contemporaneous record of decision-making during the incident, and it defines the trigger points for attorney-client privileged communications. Each function has a direct connection to how the organization will be treated by regulators, courts, and insurers after the incident ends.
The ransom payment question illustrates the legal gap that most playbooks leave open. The Office of Foreign Assets Control has issued guidance, most recently updated in October 2020, stating that ransom payments made to sanctioned entities or to persons in sanctioned jurisdictions may violate the International Emergency Economic Powers Act, 50 U.S.C. Sections 1701 through 1707, and the Trading With the Enemy Act, 50 U.S.C. Section 4305. OFAC has assessed civil monetary penalties against organizations that paid ransoms without conducting a sanctions screening. The civil penalty does not require proof that the organization knew the recipient was sanctioned: strict liability applies. A ransomware playbook that does not include a mandatory legal review step, with outside counsel engaged to conduct OFAC analysis before any payment decision, has left the organization exposed to federal enforcement that has nothing to do with the original breach.
The attorney-client privilege architecture of a playbook is equally consequential and equally underappreciated. Courts have distinguished between forensic investigation reports prepared primarily for operational business purposes and those prepared at the direction of counsel in anticipation of litigation. In a frequently cited example, a forensic report was ruled unprivileged in part because it was shared with numerous executives across the organization, establishing that the primary purpose of the report was business decision-making rather than legal advice. The dual-track model has become the standard response to this risk: one operational track for the technical response team, conducting containment, eradication, and recovery, and a separate privileged track, initiated and directed by outside counsel, for the legal investigation that will support the defense of anticipated litigation and regulatory proceedings.
Most playbooks document the operational track in detail. They specify who calls the incident response retainer, who isolates affected systems, who preserves logs, and who drafts the initial customer notification. Far fewer playbooks document the privileged track with equivalent specificity: at what point in the incident timeline outside counsel is formally engaged to direct the legal investigation, how communications from the legal investigation track are labeled and segregated from operational communications, who is permitted to receive privileged communications, and how the handoff between the operational and legal tracks is documented. This structural gap in playbook design is the gap that plaintiffs’ counsel exploits in post-breach litigation when challenging privilege assertions over forensic investigation reports.
The Defend Trade Secrets Act, 18 U.S.C. Section 1836, and the Computer Fraud and Abuse Act, 18 U.S.C. Section 1030, provide civil and criminal remedies for trade secret theft and unauthorized computer access respectively. Both statutes require the organization to demonstrate that it took reasonable measures to protect the information at issue and that the organization promptly took steps to identify and preserve evidence of the attack. An insider threat playbook that addresses only the immediate containment steps, without specifying evidence preservation protocols and chain of custody requirements consistent with federal evidentiary standards, may inadvertently destroy the evidence necessary to pursue civil or criminal remedies. Deleting logs, reimaging systems, or taking other remediation steps before forensic imaging is complete can constitute spoliation of evidence if litigation is reasonably anticipated.
The Electronic Communications Privacy Act, 18 U.S.C. Sections 2510 through 2523, adds another layer of legal complexity to insider threat playbooks. Accessing an employee’s communications during an insider threat investigation requires careful compliance with ECPA’s restrictions on interception and access to stored communications. The employer exception under ECPA allows access to communications on employer-provided systems for legitimate business purposes, but the scope of that exception has been litigated in multiple circuits without uniform results. A playbook that specifies the conditions under which HR, legal, and IT are authorized to access an employee’s communications, and that requires legal review before any such access is conducted, provides both operational clarity and a legal record demonstrating that the organization’s access was authorized under the applicable standard.
Cloud breach playbooks introduce a further complication: the contracts with cloud service providers. Most cloud service agreements include contractual incident notification obligations that run in parallel with regulatory notification requirements, often on different timelines and with different content specifications. A cloud breach playbook that does not account for the contractual notification obligations to the cloud provider, and the cloud provider’s own notification obligations to the organization under the shared responsibility model, will produce a notification timeline conflict that is difficult to resolve under pressure during an active incident. Outside counsel should review the cloud service provider agreements as part of the playbook drafting process and identify every contractual trigger that the playbook must incorporate.
The playbook itself is discoverable in subsequent litigation and regulatory investigations, and its contents will be used to evaluate whether the organization’s actual incident response met the standard it set for itself. A playbook that specifies a four-hour containment timeline but an incident in which containment took 72 hours creates a gap that plaintiffs’ counsel will highlight as evidence of failure to follow the company’s own procedures. Playbooks should set aspirational but achievable timelines, include escalation procedures for scenarios in which timelines cannot be met, and document the reasons for any deviation from specified procedures during an actual incident.
Boards that approve incident response plans should specifically require board-level review of the playbook for each category of high-impact threat that the organization has identified as a material cybersecurity risk in its Form 10-K. A board that discloses ransomware as a material risk but has not reviewed and approved a ransomware playbook has created a gap between its disclosure and its oversight. Both the 2023 SEC cybersecurity rules and the Caremark-Marchand oversight structure expect consistency between the risks disclosed and the organizational response to those risks.
The most pressing unresolved legal question in this area concerns the interaction between the OFAC sanctions compliance obligation and the four-business-day SEC disclosure timeline during an active ransomware attack. If a ransomware payment is required to restore operations essential to the company’s financial reporting system, and the OFAC analysis requires more than four business days to complete, the company may face an irresolvable conflict between regulatory timelines. This scenario has not been addressed by either OFAC or the SEC in published guidance, and the organizations that face it first will be working through it in real time without a regulatory map.
The securities law dimension of a ransomware response playbook extends beyond OFAC into insider trading territory. During an active ransomware incident, the company’s senior executives and other insiders may possess material nonpublic information about the breach before any public disclosure has been made. An executive who sells company stock after learning of a material ransomware attack but before the Form 8-K Item 1.05 disclosure is filed has committed insider trading under Securities Exchange Act Section 10(b) and Rule 10b-5(a) and (c). A ransomware playbook should include an immediate trading window suspension provision that activates at the moment a material incident is declared, prohibiting all covered persons from transacting in company securities until the public disclosure has been made and any associated quiet period has expired. The failure to include this provision in the playbook is not merely a compliance omission: it is an open invitation to insider trading liability during exactly the period of maximum information asymmetry.
Cloud breach playbooks must address the contractual notification obligations that run between the organization and its cloud service providers. Most cloud service agreements, including agreements with the major hyperscale providers, include provisions requiring the cloud customer to notify the provider of any incident affecting the provider’s infrastructure and requiring the provider to notify the customer of any incident affecting customer data or workloads. These contractual notification obligations run on timelines specified in the contract, which may differ from the regulatory notification timelines. A cloud breach playbook that addresses only the regulatory notification timeline without addressing the contractual notification timeline will produce a breach of contract claim alongside the regulatory enforcement exposure. Outside counsel should review each material cloud service agreement as part of the playbook drafting process and identify every contractual trigger, timeline, and content requirement that the playbook must incorporate.
The Defend Trade Secrets Act and Computer Fraud and Abuse Act remedies available following a data theft incident are frequently forfeited because the organization’s playbook does not preserve the evidence necessary to establish the statutory elements of these claims. The DTSA, 18 U.S.C. Section 1836(b)(1), requires the plaintiff to demonstrate that the trade secret is related to a product or service used in, or intended for use in, interstate or foreign commerce. The CFAA, 18 U.S.C. Section 1030(a), requires the plaintiff to demonstrate unauthorized access to a protected computer. Both claims require contemporaneous evidence of what data was accessed, how it was accessed, and the timeline of the unauthorized activity. A playbook that prioritizes rapid remediation over forensic evidence preservation may result in the loss of the log data, network traffic records, and system images necessary to establish these statutory elements, permanently foreclosing the organization’s ability to pursue civil or criminal remedies against the attacker.
The interaction between the playbook’s privilege architecture and the organization’s cyber insurance coverage is a tension that few organizations resolve before an incident occurs. Most cyber insurance policies include a cooperation clause requiring the policyholder to cooperate with the insurer’s investigation of the covered incident. Some insurers interpret this cooperation obligation as including access to the forensic investigation reports generated during the response. An organization that has directed its forensic investigation through outside counsel and asserted attorney-client privilege over the resulting reports may find itself in a dispute with its insurer over whether the cooperation clause requires disclosure of privileged materials. This tension should be addressed in the playbook’s privilege protocol section, which should specify how the organization intends to cooperate with insurer investigations without waiving privilege over materials generated under counsel’s direction.
Director and officer insurance policies frequently include a cyber exclusion or a professional liability exclusion that may apply to securities claims arising from cybersecurity disclosure failures. The SolarWinds litigation, in which the SEC named CISO Timothy Brown personally, highlighted the importance of understanding which D&O policy provisions apply to individual executives named in SEC enforcement actions arising from cybersecurity disclosure failures. An incident response playbook that includes a provision requiring immediate notice to the D&O insurer upon the declaration of a material incident, and a review of applicable D&O coverage by outside insurance coverage counsel, ensures that individual executives understand their coverage position before the investigation and litigation phase begins. This provision costs nothing to include and may save individual executives from personally funding their own defense in SEC enforcement proceedings.
For analysis at the intersection of corporate law, securities regulation, technology, artificial intelligence, and public policy, visit The Innovation Attorney on Substack.