DOJ’s 2018 cyber report set out four lines of incident response, and the victim owned the fourth
The initial report of the Justice Department’s Cyber-Digital Task Force explained what the FBI does when an organization is hacked. Read against the policy it relied on, it also showed which line of effort no federal agency would carry for a bank or a hospital.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
The initial report of the Justice Department’s Cyber-Digital Task Force explained what the FBI does when an organization is hacked. Read against the policy it relied on, it also showed which line of effort no federal agency would carry for a bank or a hospital.
- The week On Thursday, July 19, 2018, the Department of Justice announced the public release of the report of the Attorney General’s Cyber-Digital Task Force.
- Threat response: what the FBI brings, and what it asks The report presented the FBI as the natural first call.
- Asset response: the line the FBI does not lead PPD-41 describes asset response as “furnishing technical assistance to affected entities to protect their assets, mitigate vulnerabilities, and reduce impacts of cyber incidents,” together with identifying other entities at risk, assessing risks to a sector or region and guiding the use of federal resources to speed recovery.
- Intelligence support: information that may not come back The third line is the least visible to a victim.
- What counts as an incident PPD-41’s definition of a cyber incident, which the report quoted, is broader than the word suggests.
- Matching federal products to the people who use them The report included a table of FBI product lines that is worth reading as a distribution list.
- Business response: the line no agency carries for you The report’s description of PPD-41 included a phrase that we think deserves close attention.
- When the FBI calls first An incident plan can easily assume that the organization detects the intrusion itself.
- Routine and significant: who decides the size of the response The report explained that the federal government had adopted a Cyber Incident Severity Schema, “a rubric for describing an incident’s significance and improving the federal government’s response.”
- When an incident becomes physical The report’s description of the FBI’s capabilities ended with a reminder that some cyber incidents do not stay inside computers.
- Preparation: the relationships the report asked for The chapter opened with a sentence that applies to all four lines: “When responding to cyber incidents, preparation is key.”
- How the four lines fall on banks, health systems and agencies The four-line structure is the same for every sector.
- Objections: cooperation, control and cost One objection is that calling the FBI means losing control of the response.
- What a leader can check The four lines translate into checks a CIO, CISO, general counsel or agency director can run now.
- With hindsight The years after the report did not move the business response line to the government.
The week
On Thursday, July 19, 2018, the Department of Justice announced the public release of the report of the Attorney General’s Cyber-Digital Task Force. The press release said the Deputy Attorney General formally issued it in remarks that day at the Aspen Security Forum in Aspen, Colorado. The Attorney General had established the task force in February 2018 and directed it to answer two questions: how the Department was responding to global cyber threats, and how federal law enforcement could accomplish its mission in the area more effectively. The release said the report answered the first question. The Deputy Attorney General’s letter presenting it to the Attorney General was dated July 2, 2018.
The report had six chapters. Chapter 1 covered malign foreign influence operations, described the Department’s efforts to protect the 2018 midterm elections and announced a new Department policy on disclosing foreign influence operations. Chapters 2 and 3 described cybercrime schemes and the Department’s tools for detecting, deterring and disrupting them; Chapter 2 sorted cyber-enabled schemes into five basic categories: damage to computer systems, data theft, fraud and carding schemes, crimes threatening personal privacy, and crimes threatening critical infrastructure. Chapter 4 covered the FBI’s role in responding to cyber incidents. Chapter 5 dealt with recruiting and training the Department’s own staff, and Chapter 6 identified priority policy matters and the task force’s future work.
Chapter 4 is the part addressed most directly to organizations that might become victims. It described the FBI’s outreach and information sharing, including Private Industry Notifications, FBI Liaison Alert System reports and joint products with the Department of Homeland Security. It described the FBI’s partnership programs: the Domestic Security Alliance Council, with over 500 member companies; InfraGard, with over 50,000 vetted members in 84 local chapters; and others. It said the FBI had hosted four Chief Information Security Officer Academies with over 120 total participants as of April 2018, and four General Counsel Cyber Summits with over 500 total attendees.
The chapter then explained victim notification and reporting. The FBI has 56 field offices, it said, and may learn through law enforcement or intelligence sources that an organization has suffered an incident and notify it, or the victim may detect the incident first and notify the FBI. In larger breaches involving thousands or millions of affected customers, the report said, “the FBI relies on victimized institutions to provide notification to affected individuals.” It urged organizations, particularly critical infrastructure owners and operators, to build relationships with their local FBI field office before an incident occurred.
Finally, it set the FBI’s work inside Presidential Policy Directive 41 of July 2016, which describes cyber incident response as three concurrent lines of effort, threat response, asset response and intelligence support, and refers, in the report’s words, to “a fourth, unnamed line of effort that is best described as ‘business response.’” The report said PPD-41 designates the Department of Justice, through the FBI and the National Cyber Investigative Joint Task Force, as the lead federal agency for threat response in a significant cyber incident.
A report written by law enforcement about law enforcement can be read for what it says about the agency. It can also be read for what it tells everyone else to expect. The second reading is the useful one for a bank, a health system or a public agency. Chapter 4 of the Cyber-Digital Task Force report described what an organization gets when it calls the FBI after an intrusion, and by setting that inside PPD-41, it also showed what the organization does not get.
The framework it used divides incident response into four lines of effort, and we use them as the structure here:
- Threat response: investigation, attribution and pursuit of the actor, led by the FBI.
- Asset response: technical help to protect assets, mitigate vulnerabilities and recover, led by DHS.
- Intelligence support: building awareness of the threat and degrading the adversary, led by the intelligence community.
- Business response: continuity, legal and regulatory duties, disclosure and communications, which the report called a fourth, unnamed line of effort, and which belongs to the affected organization.
PPD-41 gives each line a different purpose and, for the first three, a different federal lead. In our reading, the four are mutually exclusive and, between them, cover everything an organization does after an intrusion. Our argument is that the report’s more practical lesson lies less in its account of FBI capability than in what that account leaves out. The federal government brings resources to three lines and, for a private organization, stays out of the fourth, which is the line that carries the organization’s legal, financial and reputational exposure. After the four lines we look at what the report said about preparing beforehand, how the lines fall on different sectors, the objections, and what a leader can check.
Threat response: what the FBI brings, and what it asks
The report presented the FBI as the natural first call. It described a “field-centric model” that lets the FBI respond quickly and in person, and said each of the 56 field offices houses a multi-agency Cyber Task Force bringing together investigators, prosecutors, intelligence analysts, computer scientists and digital forensic technicians from federal, state and local agencies. Every field office has a computer forensics laboratory, and some host a larger Regional Computer Forensic Laboratory. Since 2014 a 24-hour watch called CyWatch, housed at the National Cyber Investigative Joint Task Force, has coordinated domestic law enforcement response and tracked victim notification. Abroad, the FBI has approximately 80 Legal Attaché offices, 20 of them supplemented with cyber-specific investigators.
The report was equally clear about what the FBI wanted in return. “It is critically important to report incidents to law enforcement,” it said, “as each incident potentially involves the commission of a federal crime and may warrant investigation.” When the FBI is promptly notified, it can work to determine who caused the incident, link it to others and “potentially provide context regarding the actor, their tradecraft, and their motivations.” Attribution from FBI investigations, it noted, can support other agencies in imposing regulatory, diplomatic and technical costs on those responsible.
For the organization, threat response delivers something it cannot produce alone: knowledge of the adversary drawn from other cases and other sources. That knowledge can change a defensive plan. Knowing whether an intruder is a financially motivated group or a state service changes what the organization should expect next and what it should look for.
But threat response is the FBI’s line, run for the FBI’s purposes. Its goals are investigation, attribution and pursuit. The organization benefits, but it does not direct the work. The report’s own description makes this plain: the FBI acts “to determine who caused the incident” and to “maximize investigative opportunities.” Those are law enforcement objectives. They overlap with the victim’s interest in understanding the attack and recovering from it, but they are not identical, and an organization that expects the FBI to remediate its systems or manage its disclosure has misread the role.
The report also explained how threat response works for incidents of different size. Not every incident is “significant” from a national perspective, it said, and the scale and speed of a federal response “will vary based on the facts and circumstances of particular cases.” For significant incidents, PPD-41’s “enhanced coordination procedures” apply: an accountable senior executive manages the response, a dedicated command center is established, and a designated special agent serves as the U.S. government’s point of contact to the victim throughout. For routine incidents, the field office and its task force respond. An organization cannot know in advance which category it will fall into; it can know who in its local field office it would call.
Asset response: the line the FBI does not lead
PPD-41 describes asset response as “furnishing technical assistance to affected entities to protect their assets, mitigate vulnerabilities, and reduce impacts of cyber incidents,” together with identifying other entities at risk, assessing risks to a sector or region and guiding the use of federal resources to speed recovery. It names the Department of Homeland Security, acting through its National Cybersecurity and Communications Integration Center, as the lead for this line in significant incidents.
The report touched on asset response only at its edges, as a DOJ document would. It noted that the FBI collaborates with DHS on joint products such as Joint Analysis Reports and Joint Technical Advisories, and that DHS had been added as a partner to the Domestic Security Alliance Council. But the chapter’s account of what the FBI does on site is an account of investigation, not repair.
For an organization, that distinction has a planning consequence. Restoring systems, rebuilding trust in an environment and closing the hole the attacker used are the organization’s own work, or the work of whatever third-party responders it has retained. The report itself said that in a nationally significant incident the activities are carried out “in a coordinated way by the affected entity, by its third-party cybersecurity providers (if any), and by relevant federal agencies.” Federal asset response can add expertise and information about risks to others. It does not replace the organization’s own recovery capacity.
In our view, the practical point is to know, before an incident, which party will do what on the organization’s own systems: internal staff, a retained incident response firm, a managed service provider, the FBI as investigator, DHS as technical adviser. Each needs access, each produces evidence, and each has its own priorities. The conflicts among them, such as preserving evidence while restoring service, are easier to settle in a plan than in a crisis.
Contracts matter here as well. A retained incident response firm works for the organization, under terms the organization negotiated, and its findings may be shared with investigators or regulators only as the organization decides with counsel. A managed service provider that runs the affected systems may have its own obligations and its own investigators. The asset response line on the organization’s side is therefore a set of contracts as much as a set of people, and those contracts should say who may talk to law enforcement, who owns the forensic evidence and how quickly each party must act.
Intelligence support: information that may not come back
The third line is the least visible to a victim. PPD-41 describes intelligence support as building situational threat awareness and sharing related intelligence, integrated analysis of threat trends, identifying knowledge gaps and degrading or mitigating adversary capabilities. It names the Office of the Director of National Intelligence, through the Cyber Threat Intelligence Integration Center, as the lead for this line in significant incidents.
The report explained the limit that follows. The Department identifies victims through the FBI’s contact with them, through investigations of threat actors, through other members of the intelligence community and through foreign partners. “This information may be highly classified or may carry special handling or sharing restrictions based on the sensitivity of the source and the information provided,” it said. The FBI “takes all reasonable steps to identify the targeted individual or entity, determine if there was an actual compromise, and assess if there is actionable information it may share.”
That last phrase is the honest one. A victim notification from the FBI may arrive with less detail than the organization wants, because the source of the information cannot be exposed. An organization told that it has been compromised may not be told how the FBI knows, what exactly was seen or who else is affected. It then has to find the evidence in its own environment.
The report also described the FBI’s products aimed at industry: Private Industry Notifications providing context on ongoing or emerging threats, FLASH reports providing technical indicators, and joint products with DHS. Those are the parts of intelligence support that reach organizations in routine form. For a security team, the useful question is whether anyone is receiving them, reading them and acting on them. A notification that arrives at an unmonitored mailbox delivers nothing.
What counts as an incident
PPD-41’s definition of a cyber incident, which the report quoted, is broader than the word suggests. It covers “an event occurring on or conducted through a computer network that actually or imminently jeopardizes the integrity, confidentiality, or availability” of computers, systems, networks, infrastructure controlled by computers, or information on them. It adds: “For purposes of this directive, a cyber incident may include a vulnerability in an information system, system security procedures, internal controls, or implementation that could be exploited by a threat source.”
That second sentence matters for the four lines. Under the federal definition, an exploitable weakness can itself be an incident for coordination purposes, before any intruder has used it. A notification from the FBI or DHS about a vulnerability in an organization’s systems is therefore an event the four-line structure was built to handle, not a routine advisory to be filed.
Organizations use their own definitions, and regulators use theirs, so the federal definition does not decide what an organization must report or to whom. But aligning the internal definition with the federal one has a practical benefit. It means the people who receive federal notices and the people who run the incident process agree on when the process starts. In our reading, a mismatch, where the security team treats a vulnerability notice as an incident and the legal team does not, or the other way round, can delay the business response line, and it is cheap to fix in advance.
Matching federal products to the people who use them
The report included a table of FBI product lines that is worth reading as a distribution list. Private Industry Notifications, written by the FBI for private industry, provide contextual information about ongoing or emerging threats. FLASH reports, for selected partners and target industries, provide technical indicators gleaned through investigations or intelligence. Public Service Announcements, for the general public, cover general cyber threats. Joint Analysis Reports and Joint Technical Alerts, written with DHS and other partners for private industry, provide technical details and indicators from joint analysis. The FBI also ran what the report called “action campaigns” with sector-specific agencies to advise a defined group of stakeholders quickly about a particular threat.
Each product has a natural reader inside an organization. Technical indicators belong with the security operations team that can load them into detection tools. Contextual notices belong with threat intelligence analysts and the CISO, who decide whether the organization’s risk has changed. Public announcements belong with the communications and customer service teams, because customers will read them too and may call. An action campaign aimed at a sector belongs with whoever owns the organization’s relationship with that sector’s agency and information sharing body.
The four-line structure explains why the routing matters. These products are the intelligence support line reaching the organization before an incident. If they land in the right hands, the organization’s own asset response starts earlier and its business response, including what it tells customers, is better informed. If they land nowhere, the federal line has done its work and the organization has gained nothing from it.
Business response: the line no agency carries for you
The report’s description of PPD-41 included a phrase that we think deserves close attention. Beyond the three named lines, it said, the directive “refers to a fourth, unnamed line of effort that is best described as ‘business response’ (ensuring business continuity, addressing legal and regulatory issues, and external affairs).”
PPD-41 itself is more specific. For a federal agency that is itself the affected entity, this line may include maintaining business or operational continuity, addressing adverse financial impacts, protection of privacy, managing liability risks, complying with legal and regulatory requirements “(including disclosure and notification),” communicating with employees and other affected individuals, and dealing with external affairs such as media and congressional inquiries. The affected agency has primary responsibility. Then comes the sentence that matters for everyone else: “When a cyber incident affects a private entity, the Federal Government typically will not play a role in this line of effort, but it will remain cognizant of the affected entity’s response activities.” The relevant sector-specific agency generally coordinates the federal effort to understand the business or operational impact on private critical infrastructure.
Read together, the report and the directive tell a private organization that the line carrying its continuity, its regulatory notices, its customer communications and its liability is its own. PPD-41’s principles add that federal responders “generally will defer to affected entities in notifying other affected private sector entities and the public.” The report’s own description of victim notification is consistent: in large breaches, the FBI relies on the victimized institution to notify affected individuals.
The report did connect the two worlds in one sentence. “Finally,” it said, “notifying law enforcement may also place a victim company in a positive light with regulators, shareholders, and the public.” That is a statement about how others may view the victim, not a promise of any regulatory treatment. In our reading, it should not be relied on as a defense in an examination or an enforcement matter. It is a reason to report, not a substitute for meeting each regulator’s own requirements, which are set by each regulator and which counsel should map in advance.
The report also acknowledged why organizations hesitate. It cited the White House Council of Economic Advisers as observing that most data breaches are not reported to the U.S. government, and suggested the reluctance “may be driven by a fear of regulatory action, of reputational harm, or of an interruption to business operations.” Those three fears are, in our reading, a list of business response concerns. The report could encourage reporting; it could not take on those concerns for the victim.
When the FBI calls first
An incident plan can easily assume that the organization detects the intrusion itself. The report described the reverse case as part of the FBI’s ordinary work. The Bureau “may learn through law enforcement or intelligence sources that a U.S. person or organization has suffered an incident or is the target of illicit cyber activity, and can proactively notify the targeted entity.” Depending on the circumstances, it said, the FBI can give direct or indirect notice, and direct notification “is typically handled in-person through established liaison contacts, such as by notifying the representatives of an institutional victim.”
That scenario tests the four lines in a different order. The organization learns of the incident from the threat response line, possibly with limited detail because of the intelligence restrictions described above. It then has to start its own asset response, finding and containing the intrusion, without the head start that its own detection would have given it. And its business response clock may start at the moment of notification, depending on how its regulators and the law define awareness of an incident. Counsel should settle that definition in advance.
Three practical questions follow. First, who receives the call? The report’s reference to established liaison contacts implies that an organization with a known contact will be reached faster and more reliably than one without. Second, how does the organization confirm that the caller is genuine? A notification is also an opportunity for social engineering, and the organization should have a way to verify a contact through the field office. Third, what does the organization do in the first hour? The plan should say who is told, what is preserved and who decides whether to engage outside responders.
When the FBI calls first, the threat response line is working as designed. What happens next depends on the organization.
Routine and significant: who decides the size of the response
The report explained that the federal government had adopted a Cyber Incident Severity Schema, “a rubric for describing an incident’s significance and improving the federal government’s response.” An incident of national significance is rated Level 3 “High” (Orange) or greater. The FBI, it said, “does not allocate resources based exclusively on the schema rating,” but the rating enables multi-agency coordination procedures.
PPD-41, as the report quoted it, defines a significant cyber incident as one “that is likely to result in demonstrable harm to the national security interests, foreign relations, or economy of the United States or to the public confidence, civil liberties, or public health and safety of the American people.” Only those incidents trigger the enhanced coordination procedures and the formal federal lead-agency structure.
The practical effect for an organization is that it does not choose the size of the federal response. A hospital’s ransomware outage is a crisis for the hospital and its patients. Whether it is a significant cyber incident in the national sense depends on federal judgment about harm beyond the hospital. A regional bank’s intrusion may be severe for the bank and its customers without meeting the national threshold.
For planning purposes, then, an organization should assume the routine path: its local field office and Cyber Task Force for threat response, its own and its contractors’ resources for asset response, whatever intelligence products reach it, and its own business response. If the incident turns out to be significant, the federal structure grows around the organization’s plan. If the plan assumed the significant path, the organization will find itself waiting for help that is not coming.
When an incident becomes physical
The report’s description of the FBI’s capabilities ended with a reminder that some cyber incidents do not stay inside computers. The FBI Cyber Action Team, it said, is the agency’s rapid response force, prepared to deploy globally for significant incidents, and each field office maintains personnel “specifically trained on responding to incidents involving critical infrastructure and control systems.” If a cyber incident “generates physical impacts rising to the level of a crisis,” the FBI’s Crisis Management Unit can coordinate its tactical and disaster relief efforts and activate command posts anywhere in the United States.
For health systems and public agencies, physical impact is not hypothetical. A hospital whose systems go down may have to divert ambulances and move to paper. An agency that runs emergency services, water or transport faces safety consequences. In those cases business response includes life safety, and the asset response line includes restoring control systems and clinical devices that have their own vendors and their own rules.
The report did not suggest that the FBI would manage those consequences. Its crisis management capability supports the FBI’s own operations at scale. The organization’s emergency management plan, and the relationships with state and local emergency managers that go with it, remain the organization’s. In our reading, the useful step is to connect the cyber incident plan to the emergency operations plan, so that a cyber event with physical effects is handled by one command structure rather than two.
Preparation: the relationships the report asked for
The chapter opened with a sentence that applies to all four lines: “When responding to cyber incidents, preparation is key.” Its account of preparation was mostly about relationships with the FBI. It encouraged key organizations, “particularly critical infrastructure owners and operators,” to identify and form relationships with personnel in their local FBI field office before an incident, saying pre-established relationships and open lines of communication “will speed reporting and response efforts.”
It listed the programs through which those relationships could form. The Domestic Security Alliance Council, founded in 2006, connects corporate chief security officers with the FBI and DHS. InfraGard is a partnership in which members join as individuals rather than companies. The National Cyber-Forensics and Training Alliance, a Pittsburgh-based nonprofit created in 2003, joins law enforcement, industry and academia. The Internet Crime Complaint Center provides a reporting mechanism for internet-facilitated crime. The FBI’s Cyber Division also ran CISO Academies at Quantico and, with field offices and U.S. Attorney’s Offices, General Counsel Cyber Summits where corporate attorneys and CISOs discussed “how best to work with the U.S. government when responding to a cyber incident.”
The General Counsel summits are the detail we would underline. They recognized that the decision to call the FBI, and the terms on which an organization cooperates, are legal decisions as well as security ones. An organization whose general counsel has never discussed law enforcement cooperation with the security team will have that conversation for the first time during an incident, under time pressure.
Preparation for the other three lines is the organization’s own. It means knowing whom to call at DHS and at the organization’s sector-specific agency, having an incident response retainer if the organization relies on outside help, and, above all, having a business response plan that names who decides on continuity, notification and communications, and how fast.
How the four lines fall on banks, health systems and agencies
The four-line structure is the same for every sector. What differs is who sits around the organization in the fourth line.
For a bank or credit union, business response may include its prudential regulator’s expectations, any state requirements and, for public companies, securities disclosure. PPD-41 gives the bank’s sector-specific agency the role of coordinating the federal effort to understand the business impact; it does not take over the bank’s duties. Threat response may intersect with the bank’s own fraud and anti-money laundering work, because the same intrusion may be a crime against the bank and a channel for crimes against its customers.
For a health system, business response may include patient safety and continuity of clinical operations as well as notification duties under health privacy law. Here, too, the sector-specific agency’s role under PPD-41 is to understand the impact, not to carry the response. The asset response line may matter more here than elsewhere, because restoring clinical systems safely is a different problem from restoring a business application.
For a federal agency, PPD-41 is explicit that the fourth line is the agency’s own: “when a Federal agency is an affected entity, it shall undertake a fourth concurrent line of effort to manage the effects of the cyber incident on its operations, customers, and workforce.” State and local agencies are not federal agencies under the directive, but its principles say the federal government “must be prepared to partner” with state, local, tribal and territorial governments. A state agency’s business response sits within its own state’s laws, and its relationships with the FBI field office and with DHS are the routes into the other three lines. The report added one more line of contact for the officials who run election systems: the FBI would attempt to warn state and local officials about attempts to penetrate their systems, consistent with the Department’s new disclosure policy.
Objections: cooperation, control and cost
One objection is that calling the FBI means losing control of the response. The report did not describe the FBI taking over a victim’s systems, and PPD-41 says federal response activities will be conducted “in a manner to facilitate restoration and recovery,” balancing investigative needs with the need to return to normal operations. The real tension is narrower: evidence preservation and restoration can conflict, and the organization needs to decide in advance how it will handle requests that slow recovery.
A second objection is that reporting creates regulatory risk. The report acknowledged the fear. But reporting to law enforcement and notifying regulators are separate acts governed by separate rules. An organization may have obligations to regulators whether or not it calls the FBI, and the decision to call the FBI does not, by itself, create or remove them. Counsel should confirm how each applies.
A third objection is that the FBI shares too little to be useful. The report itself explained why information may be withheld. The answer is to treat FBI information as one input among several and to build the internal capability to find evidence independently, not to forgo the relationship.
A fourth objection is that small organizations will not receive a significant-incident response, so the framework does not apply to them. The scale of the federal response varies, as the report said. The four lines do not. A small credit union or a rural hospital still has a threat, needs to restore its assets, may receive or need intelligence, and must carry its own business response. Its plan may be shorter, but it needs all four parts.
A fifth objection is that the framework is a federal coordination tool and says nothing a private organization must do. That is correct as a matter of what PPD-41 governs: it directs federal agencies. But the directive’s description of what the federal government will not do for a private entity is information the private entity needs. It marks the boundary of outside help, and everything on the organization’s side of that boundary is its own planning problem.
What a leader can check
The four lines translate into checks a CIO, CISO, general counsel or agency director can run now.
- Name the person in the organization who will contact the FBI, and confirm that the organization knows its local field office and how to reach it outside business hours.
- Write down who will do recovery work on the organization’s systems, in-house or retained, and how evidence preservation requests will be handled while restoring service.
- Confirm that FBI and DHS threat products reach a monitored address and that someone is responsible for acting on them.
- Map the business response: every regulator and authority to notify, each deadline, each decision maker, and how the decision to report to law enforcement is made and recorded.
- Put the general counsel and the CISO in the same room before an incident to agree how the organization cooperates with law enforcement.
Each check produces an artifact that can be tested in an exercise: a contact, a retainer, a distribution list, a notification map and an agreed approach. The first three serve the federal lines. The fourth and fifth serve the line that no agency will carry for the organization.
The exercise is where the four lines meet. A tabletop that includes a call from the FBI, a request to preserve evidence while systems are down, a vulnerability notice from DHS and a regulator’s deadline tests whether the owners of each line know where the others sit. The report described the FBI using exactly this kind of exercise at its CISO Academies, where sessions explained how the government interacts with private industry before, during and after a cyberattack and engaged participants in tabletop exercises. An organization can run the same exercise on its own plan.
None of the five checks depends on the federal framework staying the same. Agencies and directives change names and roles. The division between the government’s lines and the organization’s own does not depend on any one of them, and a plan built around that division survives the changes.
With hindsight
The years after the report did not move the business response line to the government. They added duties to it, and in one case gave the Justice Department a role inside it.
On July 26, 2023, the Securities and Exchange Commission adopted rules requiring public companies to disclose material cybersecurity incidents on a new Item 1.05 of Form 8-K, generally due four business days after a company determines that an incident is material. The SEC’s announcement added: “The disclosure may be delayed if the United States Attorney General determines that immediate disclosure would pose a substantial risk to national security or public safety and notifies the Commission of such determination in writing.” In the language of PPD-41, that put a Justice Department determination inside one part of a public company’s business response, its disclosure, while leaving the decision about materiality and the disclosure itself with the company. The same rules added an annual disclosure, Regulation S-K Item 106, describing the company’s processes for assessing, identifying and managing material cybersecurity risks, the board’s oversight of those risks and management’s role and expertise. That is business response planning, made public.
Congress, meanwhile, had passed the Cyber Incident Reporting for Critical Infrastructure Act of 2022, signed on March 15, 2022. As the Cybersecurity and Infrastructure Security Agency described it in its April 4, 2024 proposed rule, the law requires covered entities to report covered cyber incidents to CISA within 72 hours after reasonably believing one has occurred, and ransom payments within 24 hours after payment. In preparing the proposal, CISA said, it consulted sector risk management agencies and members of the law enforcement and intelligence communities, such as the FBI, the U.S. Secret Service, the Treasury Department’s Financial Crimes Enforcement Network and the NSA. CISA said reporting would enhance its ability to identify trends and track cyber threat activity, and that the statute allows reports to be used for preventing, investigating, disrupting or prosecuting offenses arising from a reported incident. CIRCIA requires CISA to implement these reporting requirements through rulemaking, with a final rule due within 18 months of the proposal’s publication.
As checked on November 15, 2026, we found no final rule in the Federal Register, and the latest CIRCIA rulemaking notice there was a May 26, 2026 notice of revised town hall meetings, which said they would give stakeholders “a limited additional opportunity to provide input on refining the scope and burden” of the 2024 proposed rule. The notice said CISA had not held town halls announced in February 2026 because of a lapse in DHS appropriations from February 14 to April 30, 2026, and rescheduled them for June 2026, organized by critical infrastructure sector groupings that included financial services, healthcare and public health, and government facilities.
Neither development settled who coordinates the federal side of a response; that remained the subject of the directive the report relied on, and we did not find a source showing whether PPD-41 had been changed, so we draw no conclusion about its current status.
In our reading, both developments confirm the report’s structure rather than change it. Reporting to government grew into a set of legal duties with deadlines, which belong to the business response line. The federal lines still offer investigation, technical help and intelligence. The organization still carries its own continuity, disclosure and communications, now with more of them written into law.
Spotted an error? Tell us and we will check it and correct the article where needed.