{
 "edition": "2026-11-16",
 "sections": {
  "purpose": {
   "id": "purpose",
   "title": "1. Purpose, scope and authority",
   "intro": "This plan sets out how [Organization name] detects, declares, handles, recovers from and learns from cybersecurity incidents. It is written so that a person who has never handled an incident can act on it.",
   "bullets": [
    "Scope: this plan applies to [systems, sites, people, suppliers and data covered]. It does not cover [exclusions, for example physical safety emergencies handled under the site emergency plan].",
    "Owner: [Role, for example Chief Information Officer] owns this plan and keeps it current.",
    "Approval: [Role, for example Chief Executive Officer] approved version [number] on [date]. The next review is due on [date, no later than 12 months from approval].",
    "Definitions: an event is [any observable occurrence in a system or network]. An incident is an event or a set of events that has been declared against the criteria in section 5.",
    "Authority: the incident lead may isolate systems, disable accounts and take services offline as listed in section 7, without waiting for further approval."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "roles": {
   "id": "roles",
   "title": "2. Roles and responsibilities",
   "intro": "Name one person and one deputy for each role. A role can be filled by an outside provider if the contract says so; write the provider name in the Name column.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Role",
     "Name",
     "Deputy",
     "What this role decides"
    ],
    "rows": [
     [
      "Executive sponsor",
      "[name]",
      "[name]",
      "Funds the response. Approves shutting down or rebuilding critical services."
     ],
     [
      "Incident lead",
      "[name]",
      "[name]",
      "Declares and closes the incident. Sets priorities. Runs the response meetings."
     ],
     [
      "Technical lead",
      "[name]",
      "[name]",
      "Chooses containment and recovery actions. Directs system and network administrators."
     ],
     [
      "Communications lead",
      "[name]",
      "[name]",
      "Approves every internal and external message. Is the only spokesperson."
     ],
     [
      "Legal and privacy lead",
      "[name]",
      "[name]",
      "Decides which notice duties apply and when the clock started. Directs contact with regulators and law enforcement."
     ],
     [
      "Human resources",
      "[name]",
      "[name]",
      "Handles any case where an employee may be involved."
     ],
     [
      "Facilities and physical security",
      "[name]",
      "[name]",
      "Gives responders physical access to sites and devices."
     ],
     [
      "System and data owners",
      "[names]",
      "[names]",
      "Advise on recovery priority for their systems. Receive status updates."
     ],
     [
      "Scribe",
      "[name]",
      "[name]",
      "Keeps the incident log in appendix A."
     ]
    ]
   },
   "after": "Roles follow the examples in NIST SP 800-61 Rev. 3, section 2.2: leadership, incident handlers, technology professionals, legal, public affairs, human resources, physical security, and asset owners.",
   "note": null
  },
  "contacts": {
   "id": "contacts",
   "title": "3. Contact and escalation sheet",
   "intro": "Keep a printed copy and an offline copy. Use phone numbers that work if email and chat are down.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Who",
     "Name or organization",
     "Phone (24 hours)",
     "Backup contact",
     "Call when"
    ],
    "rows": [
     [
      "Incident lead",
      "[name]",
      "[number]",
      "[number]",
      "Any suspected incident"
     ],
     [
      "Executive sponsor",
      "[name]",
      "[number]",
      "[number]",
      "Severity 3 or 4, or any legal duty to notify"
     ],
     [
      "Legal counsel",
      "[firm or person]",
      "[number]",
      "[number]",
      "Any exposure of personal data, or any contact with a regulator"
     ],
     [
      "Cyber insurer hotline",
      "[insurer]",
      "[number]",
      "[policy number]",
      "Before hiring outside responders, if the policy requires it"
     ],
     [
      "Incident response firm",
      "[firm]",
      "[number]",
      "[retainer reference]",
      "Severity 3 or 4, or when the team cannot scope the incident"
     ],
     [
      "Internet and cloud providers",
      "[providers]",
      "[numbers]",
      "[account ids]",
      "Attack on availability, or compromise of a cloud account"
     ],
     [
      "Law enforcement",
      "[agency and office]",
      "[number]",
      "",
      "After legal counsel agrees, or when funds were sent"
     ],
     [
      "Regulators",
      "[agency per section 10]",
      "[number or portal]",
      "",
      "As section 10 directs"
     ]
    ]
   },
   "after": null,
   "note": null
  },
  "severity": {
   "id": "severity",
   "title": "4. Severity levels",
   "intro": "Rate every incident on the same four-point scale as soon as it is declared, and re-rate it when facts change. Base the rating on business impact, not on how the attack looks.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Level",
     "Criteria",
     "Examples to adapt",
     "Who is called",
     "First response target"
    ],
    "rows": [
     [
      "1 Low",
      "One user or device. No sensitive data exposed. No service affected.",
      "A blocked phishing email that no one opened.",
      "Incident lead",
      "[hours]"
     ],
     [
      "2 Medium",
      "More than one user or device, or a non-critical service affected. No confirmed exposure of sensitive data.",
      "One account compromised and reset before any data was accessed.",
      "Incident lead, technical lead",
      "[hours]"
     ],
     [
      "3 High",
      "A critical service is down or degraded, or sensitive data may have been exposed.",
      "Unauthorized access to a database holding customer records.",
      "All roles in section 2, legal counsel",
      "[minutes]"
     ],
     [
      "4 Critical",
      "Wide loss of service, confirmed exposure of regulated data, or a threat to safety.",
      "A compromised administrator account with access across the network.",
      "All roles, executive sponsor, outside responders",
      "[minutes]"
     ]
    ]
   },
   "after": "Prioritizing by organizational impact, with a failed single workstation as minor and stolen privileged data as high, is the approach the SANS Incident Handler's Handbook describes.",
   "note": null
  },
  "declare": {
   "id": "declare",
   "title": "5. Detecting, reporting and declaring an incident",
   "intro": "Anyone who sees something unusual reports it. Only the incident lead, or the deputy, declares an incident.",
   "bullets": [
    "How staff report: [phone number], [email address] or [report button]. Reports are accepted at any hour. Staff are told in training that reporting a mistake will not be punished.",
    "Who receives reports: [role or team]. They log the report in appendix A within [15 minutes].",
    "Declaration criteria: declare an incident when an event shows [unauthorized access, loss or exposure of data, malicious software on a managed device, loss of a service caused by an attack, or a supplier report of any of these]. Add your own criteria.",
    "Out-of-band communication: if email or chat may be compromised, the team uses [phone bridge or secure messaging group] and tells affected users by phone.",
    "On declaration: the incident lead sets a severity (section 4), opens the log (appendix A) and starts the clock for every notice duty in section 10."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "triage": {
   "id": "triage",
   "title": "6. Triage and analysis",
   "intro": "Work through these steps in order, and record each one in the log. Several can run at the same time.",
   "bullets": [],
   "steps": [
    "Validate: confirm the report is real and not authorized activity such as an administrator running remote tools.",
    "Scope: list the affected users, devices, accounts, services and data. Note what is not yet known.",
    "Categorize: record the type, for example [phishing, malware, account compromise, data exposure, availability attack, insider, lost device, supplier].",
    "Assess the data: state whether personal, regulated or confidential data may be involved, and whether it was encrypted.",
    "Preserve evidence: before changing a system, capture logs and, where the technical lead decides it is needed, a memory and disk image.",
    "Re-rate the severity and update the people called."
   ],
   "table": null,
   "after": null,
   "note": null
  },
  "contain": {
   "id": "contain",
   "title": "7. Containment",
   "intro": "The aim is to stop the damage from spreading without destroying evidence or alerting the attacker more than needed. Record who approved each action and when.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Action",
     "Who may approve",
     "Business impact to weigh first",
     "Logged where"
    ],
    "rows": [
     [
      "Isolate a device from the network",
      "[role]",
      "[effect on users and services]",
      "Appendix A"
     ],
     [
      "Disable or reset an account",
      "[role]",
      "[effect on the person and linked services]",
      "Appendix A"
     ],
     [
      "Block an address, domain or file",
      "[role]",
      "[effect on legitimate traffic]",
      "Appendix A"
     ],
     [
      "Take a service offline",
      "[role]",
      "[customers and contracts affected]",
      "Appendix A"
     ],
     [
      "Rotate keys and service account secrets",
      "[role]",
      "[systems that will fail until updated]",
      "Appendix A"
     ]
    ]
   },
   "after": "Short-term containment limits damage fast. Long-term containment keeps systems in production safely while a rebuild is prepared. Take a backup image of an affected system before wiping it.",
   "note": null
  },
  "recover": {
   "id": "recover",
   "title": "8. Eradication and recovery",
   "intro": "Do not start removal until every known way back in has been found and the evidence is collected. Do not declare recovery until the checks below pass.",
   "bullets": [],
   "steps": [
    "Confirm containment: no new signs of attacker activity for [period].",
    "Eradicate: remove malicious files, close the entry point, reset affected credentials, patch the exploited weakness, and rebuild systems from known-good sources where there is doubt.",
    "Verify backups before restoring from them, and restore to clean systems only.",
    "Test restored systems, then watch them closely for [period] for signs of re-entry.",
    "Declare the end of recovery: the incident lead signs when the exit criteria are met: [criteria, for example services at normal levels, no alerts for 72 hours, owners agree]."
   ],
   "table": null,
   "after": null,
   "note": null
  },
  "comms": {
   "id": "comms",
   "title": "9. Communications",
   "intro": "One person speaks for the organization. Facts are confirmed before they are shared, and nothing is guessed in writing.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Audience",
     "Owner",
     "Channel",
     "Approved by",
     "Timing"
    ],
    "rows": [
     [
      "Employees",
      "[role]",
      "[channel]",
      "Communications lead",
      "[when]"
     ],
     [
      "Customers and partners",
      "[role]",
      "[channel]",
      "Communications lead, legal",
      "[when]"
     ],
     [
      "Regulators and law enforcement",
      "Legal and privacy lead",
      "[portal or phone]",
      "Legal and privacy lead",
      "As section 10 directs"
     ],
     [
      "Insurer",
      "[role]",
      "[hotline]",
      "Executive sponsor",
      "[when]"
     ],
     [
      "Media",
      "Communications lead",
      "Holding statement",
      "Executive sponsor, legal",
      "Only if asked or required"
     ],
     [
      "Executives and board",
      "Incident lead",
      "[channel]",
      "Incident lead",
      "[interval]"
     ]
    ]
   },
   "after": "Prepare a holding statement now: \"We are investigating a security incident. We will share confirmed facts as we have them. Contact [name and number] with questions.\"",
   "note": null
  },
  "legal": {
   "id": "legal",
   "title": "10. Legal, regulatory, contractual and insurance notices",
   "intro": "List every duty to notify that applies to your organization, with the trigger, the deadline and the owner. The legal and privacy lead confirms the list at least once a year. Record the date and time each clock started.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Rule, contract or policy",
     "Applies when",
     "Deadline and to whom",
     "Owner",
     "Source"
    ],
    "rows": [
     [
      "[Name the law, for example a state breach notification law]",
      "[trigger]",
      "[deadline] to [authority or individuals]",
      "[role]",
      "[link]"
     ],
     [
      "[Customer contract clause]",
      "[trigger]",
      "[deadline] to [customer]",
      "[role]",
      "[contract reference]"
     ],
     [
      "[Cyber insurance policy]",
      "[trigger]",
      "[deadline] to [insurer]",
      "[role]",
      "[policy number]"
     ],
     [
      "[Other]",
      "[trigger]",
      "[deadline]",
      "[role]",
      "[link]"
     ]
    ]
   },
   "after": "The company-type pages of this site show the filled-in rows for health care, financial services, public companies, software providers, schools, federal agencies and the United Kingdom, each with its source.",
   "note": null
  },
  "evidence": {
   "id": "evidence",
   "title": "11. Evidence handling and documentation",
   "intro": "Write down what happened, what was decided, and by whom, at the time. The log supports the review, regulators, insurers and any later legal action.",
   "bullets": [
    "Record for each entry: date and time with time zone, who observed or acted, what was seen or done, which system, where evidence is stored.",
    "Store logs, images and notes in a location only responders can reach.",
    "For each evidence item record: item id, source, who collected it, when, how it was copied, a hash value if available, and who has handled it since.",
    "Do not edit entries after the fact. Add a correction as a new entry."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "third": {
   "id": "third",
   "title": "12. Third parties and suppliers",
   "intro": "List the providers who hold your data or run your systems, and what each must tell you and when. Include them in exercises.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Third party",
     "Service",
     "Incident contact",
     "Their duty to tell us",
     "Our duty to tell them"
    ],
    "rows": [
     [
      "[provider]",
      "[service]",
      "[name and number]",
      "[contract clause and time]",
      "[when]"
     ],
     [
      "[provider]",
      "[service]",
      "[name and number]",
      "[contract clause and time]",
      "[when]"
     ]
    ]
   },
   "after": "Check what each provider may do on your behalf during an incident, such as shutting off a service, and what it may not share with its other customers.",
   "note": null
  },
  "review": {
   "id": "review",
   "title": "13. Post-incident review",
   "intro": "Hold a review after every declared incident, as soon as possible and within [10 business days] of closing it. Keep the meeting short and about facts and fixes, not blame.",
   "bullets": [
    "Agenda: what happened and when; what worked; what did not; what was missing, including information that was hard to get.",
    "Outputs: a closing report (appendix D), the root cause, and a list of actions each with an owner and a due date.",
    "Update this plan, the contact sheet and the detections within [30 days].",
    "Share what was learned with the people who need it, without waiting for the final report if a lesson is urgent."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "maintain": {
   "id": "maintain",
   "title": "14. Testing, training and keeping the plan current",
   "intro": "A plan that has not been practiced is a draft.",
   "bullets": [
    "Exercise: walk through this plan with all roles at least once every [12 months] using a realistic scenario, and record the findings.",
    "Test restoring critical systems from backups at least once every [12 months].",
    "Training: every responder is trained for their role. All staff learn how to report an incident.",
    "Distribution: current copies are available to every person with a role, including offline, and are reachable during an incident.",
    "Update this plan when roles change, after every incident or exercise, and when a law or contract changes a notice duty."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "forms": {
   "id": "forms",
   "title": "Appendices: forms",
   "intro": "Copy these forms into your records system. Appendix A is opened on declaration and closed on review.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Appendix",
     "Form",
     "Fields"
    ],
    "rows": [
     [
      "A",
      "Incident log",
      "Entry number; date and time; recorded by; what was observed or done; system; evidence id; decision and approver"
     ],
     [
      "B",
      "Timeline",
      "Time of first malicious activity; time detected; time declared; time contained; time notices sent; time recovered; time closed"
     ],
     [
      "C",
      "Handover note",
      "Current status; open actions; next decisions; people on shift; next update time; where the log is"
     ],
     [
      "D",
      "Closing report",
      "Summary; cause; impact; data involved; notices sent with times; cost; lessons; actions with owners and dates"
     ]
    ]
   },
   "after": null,
   "note": null
  },
  "sb1": {
   "id": "sb1",
   "title": "1. Prepare: who is in charge",
   "intro": "Write this page once and print it.",
   "bullets": [
    "Incident lead: [name], phone [number]. Deputy: [name], phone [number].",
    "Outside help: [IT provider or incident response firm], phone [number]. Insurance hotline: [number], policy [number].",
    "Where the backups are and who can restore them: [location and name]. Test a restore once a year.",
    "The three systems we cannot run without: [system 1], [system 2], [system 3]."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "sb2": {
   "id": "sb2",
   "title": "2. Identify: what counts as an incident",
   "intro": "Call the incident lead if any of these happen.",
   "bullets": [
    "Someone clicked a link or opened a file and the device now behaves oddly.",
    "A password or account was shared, guessed or used by someone else.",
    "A device with business data is lost or stolen.",
    "A payment request or bank detail change looks wrong.",
    "A website, system or phone line stops working and the cause is not clear.",
    "A supplier or customer tells us they were breached."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "sb3": {
   "id": "sb3",
   "title": "3. Resolve: the first hour",
   "intro": "The incident lead does these in order and writes the time next to each.",
   "bullets": [],
   "steps": [
    "Write down what you know: who, what, when, which devices and accounts.",
    "Disconnect affected devices from the network. Do not delete anything.",
    "Change passwords on affected accounts from a device you trust, and turn on two-step sign-in.",
    "Call the outside help number on page 1 and tell the insurer if the policy requires it.",
    "If money was sent, call the bank immediately and ask for a recall.",
    "Decide with the outside help what to restore, and from which backup."
   ],
   "table": null,
   "after": null,
   "note": null
  },
  "sb4": {
   "id": "sb4",
   "title": "4. Report: who to tell and when",
   "intro": "Decide with legal advice whether any law or contract requires a notice, and how soon.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Who",
     "When",
     "Who tells them",
     "Done (time)"
    ],
    "rows": [
     [
      "Staff",
      "After the first hour",
      "[name]",
      ""
     ],
     [
      "Customers or partners affected",
      "As soon as facts are confirmed",
      "[name]",
      ""
     ],
     [
      "Regulator or authority, if any law applies",
      "[deadline from the law]",
      "[name]",
      ""
     ],
     [
      "Insurer",
      "[per policy]",
      "[name]",
      ""
     ],
     [
      "Police or national reporting service",
      "If a crime, or funds were lost",
      "[name]",
      ""
     ]
    ]
   },
   "after": null,
   "note": null
  },
  "sb5": {
   "id": "sb5",
   "title": "5. Learn: after the incident",
   "intro": "Within two weeks, meet for 30 minutes.",
   "bullets": [
    "What happened, in a few sentences.",
    "What we did well. What we missed.",
    "Three fixes, each with a name and a date.",
    "Update this plan and the phone numbers."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "db1": {
   "id": "db1",
   "title": "1. Purpose, scope and breach team",
   "intro": "This plan applies when personal or regulated data may have been accessed, disclosed, lost or altered without authority, at [Organization name] or at a supplier that holds our data.",
   "bullets": [
    "Breach team: incident lead [name]; privacy lead [name]; legal counsel [name]; communications lead [name]; technical lead [name]; executive sponsor [name]; each with a named deputy.",
    "The team has authority to [take systems offline, suspend accounts, engage outside experts] without further approval."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "db2": {
   "id": "db2",
   "title": "2. Discover, report and contain",
   "intro": "Anyone who suspects a breach reports it at once. The incident lead records the time of discovery.",
   "bullets": [],
   "steps": [
    "Record the date and time the breach was first known, and who knew.",
    "Stop the exposure: revoke access, take down the page or share, recover the device or message where possible.",
    "Preserve logs and evidence. Do not wipe systems yet.",
    "Open the log and the decision record."
   ],
   "table": null,
   "after": null,
   "note": null
  },
  "db3": {
   "id": "db3",
   "title": "3. Assess the breach",
   "intro": "Answer these questions, in writing, as soon as the facts allow. Update the answers as the investigation develops.",
   "bullets": [
    "What data: types of data and, for each, the number of people and records.",
    "Whose data: customers, employees, patients, students, children; which countries and states.",
    "How: cause and whether the breach is still happening.",
    "Was the data protected, for example by strong encryption, so that it is unintelligible to unauthorized people?",
    "Who has it: an unknown actor, a known recipient, a supplier, a misdirected email.",
    "What harm could follow: fraud, identity theft, physical or reputational harm, discrimination."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "db4": {
   "id": "db4",
   "title": "4. Decide who must be told",
   "intro": "The privacy lead and counsel complete this table within [24 hours] of discovery and revisit it daily.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Recipient",
     "Test for notifying",
     "Deadline",
     "Decision, time and owner"
    ],
    "rows": [
     [
      "Supervisory authority or regulator",
      "[rule and test from section 10 of the plan]",
      "[deadline]",
      ""
     ],
     [
      "Affected individuals",
      "[rule and test]",
      "[deadline]",
      ""
     ],
     [
      "Customers whose data we process",
      "[contract clause]",
      "[deadline]",
      ""
     ],
     [
      "Insurer",
      "[policy clause]",
      "[deadline]",
      ""
     ],
     [
      "Law enforcement",
      "[when advised by counsel]",
      "n/a",
      ""
     ],
     [
      "Payment brands, banks, other contractual parties",
      "[contract clause]",
      "[deadline]",
      ""
     ]
    ]
   },
   "after": "Examples of tests, each from the source named on this site: GDPR Article 33 (72 hours to the authority unless the breach is unlikely to result in a risk), Article 34 (communicate to individuals when likely to result in a high risk), HIPAA 164.404 (60 days to individuals), FTC Safeguards Rule 314.4(j) (30 days to the FTC for 500 or more consumers).",
   "note": null
  },
  "db5": {
   "id": "db5",
   "title": "5. Write the notice",
   "intro": "Use plain language. Include the same minimum content for every audience, then add what the audience needs.",
   "bullets": [
    "What happened, with dates, and when it was discovered.",
    "The categories and approximate number of people and records involved.",
    "The likely consequences.",
    "What we have done and are doing, including steps to limit harm.",
    "What recipients should do to protect themselves.",
    "How to ask questions: name or role, phone, email, website or postal address."
   ],
   "steps": [],
   "table": null,
   "after": "GDPR Article 33(3) lists the elements on what happened, the categories and numbers, the likely consequences, the measures taken and the contact point. The element on what recipients should do to protect themselves comes from 45 CFR 164.404(c)(1)(C); GDPR reaches it only through the mitigation measures in Article 33(3)(d) and Article 34(2).",
   "note": null
  },
  "db6": {
   "id": "db6",
   "title": "6. Support affected people",
   "intro": "Decide what help to offer and who delivers it.",
   "bullets": [
    "Dedicated phone line or mailbox: [details], staffed [hours].",
    "Offers such as credit monitoring or identity protection where the data supports a need: [offer, provider, duration].",
    "A frequently asked questions page, updated daily until closure."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "db7": {
   "id": "db7",
   "title": "7. Document and review",
   "intro": "Document every breach, even one that is not reported to anyone.",
   "bullets": [
    "Record the facts, the effects and the remedial action, in a form that lets a regulator check compliance (GDPR Article 33(5)).",
    "Hold a review within [10 business days] of closure: cause, controls that failed, what to change, owners and dates.",
    "Update the plan, the notice templates and the training."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "cl1": {
   "id": "cl1",
   "title": "First-hours checklist",
   "intro": "Tick each item and write the time. Hand the page to the next shift with the log.",
   "bullets": [],
   "steps": [],
   "note": null,
   "after": null,
   "table": {
    "head": [
     "Step",
     "Done",
     "Time",
     "By"
    ],
    "rows": [
     [
      "Incident declared. Severity set. Log opened.",
      "[ ]",
      "",
      ""
     ],
     [
      "Incident lead, technical lead and communications lead called.",
      "[ ]",
      "",
      ""
     ],
     [
      "Out-of-band channel opened (phone bridge or secure group).",
      "[ ]",
      "",
      ""
     ],
     [
      "Affected systems, accounts and data listed. Unknowns listed.",
      "[ ]",
      "",
      ""
     ],
     [
      "Evidence preserved before any change: logs saved, images taken where needed.",
      "[ ]",
      "",
      ""
     ],
     [
      "Containment actions approved and recorded.",
      "[ ]",
      "",
      ""
     ],
     [
      "Legal and privacy lead told. Notice clocks started and times recorded.",
      "[ ]",
      "",
      ""
     ],
     [
      "Insurer and outside responders told, if the policy or plan requires it.",
      "[ ]",
      "",
      ""
     ],
     [
      "First message to staff approved by the communications lead.",
      "[ ]",
      "",
      ""
     ],
     [
      "Next update time set and announced.",
      "[ ]",
      "",
      ""
     ],
     [
      "Handover note written if the shift changes.",
      "[ ]",
      "",
      ""
     ]
    ]
   }
  },
  "cl2": {
   "id": "cl2",
   "title": "Form A: incident log",
   "intro": "One row per entry. Never edit a row; add a new row to correct it.",
   "bullets": [],
   "steps": [],
   "note": null,
   "after": null,
   "table": {
    "head": [
     "No.",
     "Date and time (zone)",
     "Recorded by",
     "What was observed or done",
     "System or account",
     "Evidence id",
     "Decision and approver"
    ],
    "rows": [
     [
      "1",
      "[ ]",
      "[ ]",
      "[ ]",
      "[ ]",
      "[ ]",
      "[ ]"
     ],
     [
      "2",
      "[ ]",
      "[ ]",
      "[ ]",
      "[ ]",
      "[ ]",
      "[ ]"
     ],
     [
      "3",
      "[ ]",
      "[ ]",
      "[ ]",
      "[ ]",
      "[ ]",
      "[ ]"
     ]
    ]
   }
  },
  "cl3": {
   "id": "cl3",
   "title": "Form B: timeline",
   "intro": "Fill in as facts are confirmed. Mark estimates with \"est.\".",
   "bullets": [],
   "steps": [],
   "note": null,
   "after": null,
   "table": {
    "head": [
     "Event",
     "Date and time (zone)",
     "Source of the time"
    ],
    "rows": [
     [
      "First malicious activity",
      "[ ]",
      "[ ]"
     ],
     [
      "Detected",
      "[ ]",
      "[ ]"
     ],
     [
      "Reported",
      "[ ]",
      "[ ]"
     ],
     [
      "Declared",
      "[ ]",
      "[ ]"
     ],
     [
      "Contained",
      "[ ]",
      "[ ]"
     ],
     [
      "Notice clock started (one row per rule)",
      "[ ]",
      "[ ]"
     ],
     [
      "Notices sent (one row per recipient)",
      "[ ]",
      "[ ]"
     ],
     [
      "Recovery started",
      "[ ]",
      "[ ]"
     ],
     [
      "Recovery declared complete",
      "[ ]",
      "[ ]"
     ],
     [
      "Review held",
      "[ ]",
      "[ ]"
     ]
    ]
   }
  },
  "cl4": {
   "id": "cl4",
   "title": "Form C: handover note",
   "intro": "Write this at every change of shift, in under one page.",
   "bullets": [
    "Current status and severity.",
    "Actions open, with owners.",
    "Decisions waiting, and who must make them.",
    "People on shift and how to reach them.",
    "Next update time and audience.",
    "Where the log and evidence are."
   ],
   "steps": [],
   "table": null,
   "note": null,
   "after": null
  },
  "cl5": {
   "id": "cl5",
   "title": "Form D: closing report outline",
   "intro": "The incident lead completes this before the review meeting.",
   "bullets": [],
   "steps": [
    "Summary in five sentences.",
    "Timeline (Form B).",
    "Cause and how it was found.",
    "Impact: systems, people, data, money, hours.",
    "Notices sent, to whom and when.",
    "What worked and what did not.",
    "Actions: owner, due date, status.",
    "Changes made to this plan."
   ],
   "table": null,
   "note": null,
   "after": null
  },
  "add-healthcare": {
   "id": "add-healthcare",
   "title": "10A. Health care: HIPAA breach notification",
   "intro": "Use this addendum if your organization is a HIPAA covered entity or a business associate. It adds the notice duties of the HIPAA Breach Notification Rule to section 10.",
   "bullets": [
    "Record the date and time of discovery in the incident log, because the 60-day period counts from it.",
    "Record whether the data was encrypted to the standard that makes it \"secured\". Only unsecured protected health information triggers these notices.",
    "The individual notice must include: what happened with dates, the types of information involved, steps individuals should take, what the entity is doing, and contact procedures that include a toll-free number, an email address, a website or a postal address (164.404(c)).",
    "A business associate adds the covered entity's incident contact to the contact sheet and the time allowed by the contract, which may be shorter than 60 days."
   ],
   "steps": [],
   "table": {
    "head": [
     "Duty",
     "What the rule says",
     "Deadline",
     "Source"
    ],
    "rows": [
     [
      "Presumption of breach",
      "An impermissible use or sharing of protected health information is presumed a breach unless a risk assessment shows a low probability of compromise. The assessment weighs four factors: the nature and extent of the information, the person who used or received it, whether it was actually acquired or viewed, and how far the risk was mitigated.",
      "Decide before the notice clock questions arise",
      "45 CFR 164.402"
     ],
     [
      "Notice to individuals",
      "Notify each individual affected by a breach of unsecured protected health information, in plain language, by first-class mail or by email if the person agreed.",
      "Without unreasonable delay and no later than 60 calendar days after discovery",
      "45 CFR 164.404"
     ],
     [
      "When a breach is \"discovered\"",
      "The first day the breach is known, or would have been known with reasonable diligence, to the covered entity.",
      "Start the clock on that day",
      "45 CFR 164.404(a)(2)"
     ],
     [
      "Notice to the Secretary of HHS",
      "500 or more individuals: notify at the same time as individuals. Fewer than 500: keep a log and notify within 60 days after the end of the calendar year.",
      "Same time, or 60 days after year end",
      "45 CFR 164.408"
     ],
     [
      "Notice to media",
      "More than 500 residents of a State or jurisdiction: notify prominent media outlets serving that area.",
      "No later than 60 calendar days after discovery",
      "45 CFR 164.406"
     ],
     [
      "Business associate to covered entity",
      "A business associate notifies the covered entity of a breach it discovers.",
      "Without unreasonable delay and no later than 60 calendar days after discovery",
      "45 CFR 164.410"
     ]
    ]
   },
   "after": null,
   "note": null,
   "sources": [
    "h402",
    "h404",
    "h406",
    "h408",
    "h410"
   ]
  },
  "add-financial": {
   "id": "add-financial",
   "title": "10A. Financial services: GLBA Safeguards Rule and New York 23 NYCRR 500",
   "intro": "Use this addendum if your organization is a financial institution under the FTC's Safeguards Rule, or a covered entity under the New York Department of Financial Services cybersecurity regulation. The two rules prescribe what the plan must cover.",
   "bullets": [
    "Add the seven Safeguards Rule areas as a checklist on the cover page of the plan and name the section of this plan that answers each.",
    "Name the Qualified Individual in the roles table and schedule the annual board report.",
    "For New York covered entities, add the root cause analysis template to appendix D and the backup restore test to the annual calendar.",
    "Record the time the entity \"determined\" an incident occurred, because the 72-hour period counts from it."
   ],
   "steps": [],
   "table": {
    "head": [
     "Duty",
     "What the rule says",
     "Deadline",
     "Source"
    ],
    "rows": [
     [
      "Written incident response plan",
      "Establish a written plan designed to respond to and recover from any security event materially affecting customer information. It must address seven areas: goals; internal processes; roles, responsibilities and levels of decision-making authority; external and internal communications and information sharing; remediation of identified weaknesses; documentation and reporting; and evaluation and revision after a security event.",
      "In place now",
      "16 CFR 314.4(h)"
     ],
     [
      "Notice to the FTC",
      "If a notification event involves the information of at least 500 consumers, notify the FTC electronically.",
      "As soon as possible and no later than 30 days after discovery",
      "16 CFR 314.4(j)"
     ],
     [
      "Report to the board",
      "The Qualified Individual reports in writing at least annually to the board or equivalent, covering program status and material matters, including security events and management's responses.",
      "At least annually",
      "16 CFR 314.4(i)"
     ],
     [
      "New York plan content",
      "Plans must address nine areas: the same topics as the Safeguards Rule, plus recovery from backups and a root cause analysis describing how and why the event occurred, its business impact and what will prevent a repeat, with the plan updated as necessary.",
      "In place now",
      "23 NYCRR 500.16(a)(1)"
     ],
     [
      "New York test",
      "Test the incident response and business continuity plans with all staff and management critical to the response, and test the ability to restore critical data from backups, at least annually.",
      "At least annually",
      "23 NYCRR 500.16(d)"
     ],
     [
      "Notice to the New York superintendent",
      "Notify the superintendent electronically of a cybersecurity incident at the covered entity, its affiliates or a third-party service provider.",
      "As promptly as possible and no later than 72 hours after determining an incident occurred",
      "23 NYCRR 500.17(a)"
     ]
    ]
   },
   "after": null,
   "note": null,
   "sources": [
    "ftc314",
    "nydfs16",
    "nydfs17"
   ]
  },
  "add-public-company": {
   "id": "add-public-company",
   "title": "10A. U.S. public companies: SEC Form 8-K Item 1.05",
   "intro": "Use this addendum if your company files reports under the Securities Exchange Act of 1934. It adds the material cybersecurity incident filing to section 10.",
   "bullets": [
    "Name who makes the materiality call (for example the committee that reviews public filings) and when the incident lead must brief them.",
    "Add a standing agenda item: \"Has anything changed that bears on materiality?\" at each response meeting.",
    "Record the date and time the determination was made, because the four business days count from it, not from discovery.",
    "The rules took effect on September 5, 2023. Confirm the current text with securities counsel before relying on this summary."
   ],
   "steps": [],
   "table": {
    "head": [
     "Duty",
     "What the rule says",
     "Deadline",
     "Source"
    ],
    "rows": [
     [
      "Materiality determination",
      "Registrants must make the materiality determination about an incident without unreasonable delay. The SEC changed the proposed wording \"as soon as reasonably practicable\" to this.",
      "Without unreasonable delay after discovery",
      "SEC release 33-11216"
     ],
     [
      "Form 8-K Item 1.05",
      "Disclose a cybersecurity incident determined to be material, describing the material aspects of its nature, scope and timing, and its impact or reasonably likely impact.",
      "Within four business days of determining the incident was material",
      "SEC release 33-11216"
     ],
     [
      "Delay for national security",
      "A filing may be delayed if the United States Attorney General determines that immediate public filing would pose a substantial risk to national security or public safety.",
      "As the Attorney General determines",
      "SEC release 33-11216"
     ],
     [
      "Amendment",
      "Amend a prior Item 1.05 Form 8-K to report information that was not determined or was unavailable at the first filing. The first filing must say which Item 1.05(a) information is not yet determined or is unavailable.",
      "Within four business days after the information is determined or becomes available",
      "SEC release 33-11216"
     ]
    ]
   },
   "after": null,
   "note": null,
   "sources": [
    "secfr"
   ]
  },
  "add-saas": {
   "id": "add-saas",
   "title": "10A. Software and cloud providers: duties to customers",
   "intro": "Use this addendum if your organization stores or processes customer data on their behalf. Your customers carry their own clocks, and your notice starts theirs.",
   "bullets": [
    "Keep a current list of customers by data type and region so legal can see who must hear from you, and in what order.",
    "Decide in advance who posts to the status page and what it may say, so that customers hear from you before they read about it elsewhere.",
    "Add a sub-processor list to section 12 with each sub-processor's duty to tell you.",
    "Keep logs long enough to answer customer questions about what was accessed."
   ],
   "steps": [],
   "table": {
    "head": [
     "Duty",
     "What the rule says",
     "Deadline",
     "Source"
    ],
    "rows": [
     [
      "GDPR processor",
      "A processor notifies the controller of a personal data breach after becoming aware of it.",
      "Without undue delay",
      "GDPR Article 33(2)"
     ],
     [
      "HIPAA business associate",
      "A business associate that discovers a breach of unsecured protected health information notifies the covered entity.",
      "Without unreasonable delay and no later than 60 calendar days after discovery",
      "45 CFR 164.410"
     ],
     [
      "NIS2 recipients of services",
      "Essential and important entities notify, where appropriate and without undue delay, the recipients of their services of significant incidents likely to adversely affect the provision of those services.",
      "Without undue delay",
      "NIS2 Article 23(1)"
     ],
     [
      "Contracts",
      "Customer agreements often set shorter times and named contacts. Record each one in the contact sheet.",
      "Per contract",
      "Your contracts"
     ]
    ]
   },
   "after": null,
   "note": null,
   "sources": [
    "gdpr",
    "h410",
    "nis2"
   ]
  },
  "add-school": {
   "id": "add-school",
   "title": "10A. Schools and education agencies: student data",
   "intro": "Use this addendum for a school, district, college or education agency. The U.S. Department of Education's Privacy Technical Assistance Center (PTAC) publishes a breach response checklist for these organizations.",
   "bullets": [
    "Name the data owners (for example the student information system owner and each cloud vendor) in section 12 with the person to call.",
    "Add the state student privacy and breach notification statutes that apply to your state in the section 10 table, after checking with counsel.",
    "Write the parent and student notice in plain language and keep a translated version if your community needs one."
   ],
   "steps": [],
   "table": {
    "head": [
     "Point",
     "What the source says",
     "Source"
    ],
    "rows": [
     [
      "FERPA and notice",
      "FERPA itself does not contain specific breach notification requirements. It protects the confidentiality of education records by requiring a record of each release of student data.",
      "PTAC checklist, September 2012"
     ],
     [
      "State and other federal laws",
      "Most states have breach notification laws. Federal laws that may apply include the Gramm-Leach-Bliley Act, the FTC Act, the HITECH Act and FERPA. Check each with counsel.",
      "PTAC checklist, September 2012"
     ],
     [
      "Before a breach",
      "Write a breach response policy; find where personally identifiable information lives, including backups; monitor for leakage; train staff on a recurring basis.",
      "PTAC checklist, September 2012"
     ],
     [
      "Responding",
      "Validate the breach; determine its scope and composition; notify data owners; decide whether to notify law enforcement; decide whether, when and how to notify affected individuals.",
      "PTAC checklist, September 2012"
     ]
    ]
   },
   "after": null,
   "note": null,
   "sources": [
    "ptac"
   ]
  },
  "add-federal": {
   "id": "add-federal",
   "title": "10A. U.S. federal civilian agencies: reporting to CISA",
   "intro": "Use this addendum for a Federal Civilian Executive Branch (FCEB) agency. CISA's playbook applies to these agencies; other organizations may use it as a model.",
   "bullets": [
    "Add the agency's CISA liaison and the OMB contact to the contact sheet.",
    "Use the playbook's Appendix B checklist as the working checklist during a major incident.",
    "Add continuity-of-operations contacts to section 3 if the agency's COOP plan applies."
   ],
   "steps": [],
   "table": {
    "head": [
     "Duty",
     "What the playbook says",
     "Source"
    ],
    "rows": [
     [
      "Report every incident",
      "FCEB agencies must promptly report all cybersecurity incidents, regardless of severity, to CISA. \"Declaring\" an incident means reporting it to CISA at cisa.gov/report and alerting agency IT leadership.",
      "CISA playbook, November 2021"
     ],
     [
      "Major incidents",
      "Report major incidents to CISA and to OMB at the address the playbook gives. CISA can help decide whether an incident should be declared a major incident.",
      "CISA playbook, November 2021"
     ],
     [
      "Coordination lead",
      "Document processes for designating a coordination lead (incident manager), escalation of major incidents, surge staffing, and evidence sharing with law enforcement.",
      "CISA playbook, November 2021"
     ],
     [
      "Playbook basis",
      "The playbook follows the phases of NIST SP 800-61 Rev. 2: preparation, detection and analysis, containment, eradication and recovery, and post-incident activities. NIST published Rev. 3 in April 2025.",
      "CISA playbook; NIST"
     ]
    ]
   },
   "after": null,
   "note": null,
   "sources": [
    "cisapb",
    "n61r3"
   ]
  },
  "add-uk": {
   "id": "add-uk",
   "title": "10A. United Kingdom: ICO and NCSC",
   "intro": "Use this addendum for an organization that processes personal data in the United Kingdom.",
   "bullets": [
    "Add the ICO and NCSC to the contact sheet, with the NCSC number printed in the guide: 0300 123 2040.",
    "Write down who decides whether a breach is notifiable and on what test, and record the time you became aware.",
    "For the first report, say what happened, what data is involved and what you are doing, and add detail later; the ICO allows phased reports."
   ],
   "steps": [],
   "table": {
    "head": [
     "Duty",
     "What the source says",
     "Deadline",
     "Source"
    ],
    "rows": [
     [
      "Report to the ICO",
      "Report a notifiable personal data breach to the Information Commissioner's Office. If you take longer than 72 hours you must give reasons for the delay.",
      "Without undue delay and no later than 72 hours after becoming aware, where feasible",
      "ICO guide"
     ],
     [
      "Phased reporting",
      "It is not always possible to investigate fully within 72 hours, so Article 33(4) lets you provide information in phases without undue further delay. The ICO says to tell it when you expect more detail.",
      "Initial report within 72 hours, then as soon as possible",
      "ICO guide"
     ],
     [
      "Communications service providers",
      "Providers report breaches under the Privacy and Electronic Communications Regulations on a separate form. The ICO says the Data Use and Access Act changed the PECR period from 24 hours to 72 hours on 20 August 2025.",
      "72 hours",
      "ICO guide"
     ],
     [
      "NCSC live attack",
      "A business, charity or other organization suffering a live cyber attack can call the NCSC. It states the service is available 24 hours a day, 7 days a week.",
      "Immediately",
      "NCSC small business guide"
     ]
    ]
   },
   "after": null,
   "note": null,
   "sources": [
    "ico",
    "ncscsmall"
   ]
  },
  "phishing-1": {
   "id": "phishing-1",
   "title": "When to use this playbook",
   "intro": "Use this playbook when staff report a suspicious message, or when a user clicked a link, opened a file or entered credentials after a message arrived by email, text or chat.",
   "bullets": [],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "phishing-2": {
   "id": "phishing-2",
   "title": "Before you start: prerequisites",
   "intro": "Complete these before an incident, as part of planning.",
   "bullets": [
    "Mailbox auditing is on for all mailboxes, and message trace logs can be searched.",
    "Sign-in logs and endpoint alerts are kept and searchable.",
    "At least one identifier (email address or username) is known for each suspected target.",
    "Staff know how to report a message with one click or one phone call, and know they will not be blamed.",
    "Responders have the accounts and roles needed to search mail, reset sessions and remove messages."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "phishing-3": {
   "id": "phishing-3",
   "title": "Workflow",
   "intro": "Work in this order. Record each step and its time in the incident log.",
   "bullets": [],
   "steps": [
    "Identify and confirm the phishing message: get the original message and its message identifier.",
    "Scope: find every recipient and whether each message was delivered.",
    "Assess interaction: who opened, clicked or replied, and who entered credentials or ran a file.",
    "Look for follow-on activity: new sign-ins, mailbox rules, forwarding, file downloads, new devices, lateral movement.",
    "Contain: remove the message from all mailboxes; block the sender, link and domain; revoke sessions and reset passwords for exposed accounts; isolate any device that ran a file.",
    "Prevent recurrence: add detections, adjust filters, and send a short note to staff."
   ],
   "table": null,
   "after": null,
   "note": null
  },
  "phishing-4": {
   "id": "phishing-4",
   "title": "Decision points",
   "intro": "Stop at each of these and record the decision, the decider and the time.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Decision",
     "Who decides",
     "Information needed"
    ],
    "rows": [
     [
      "Is any account or device compromised?",
      "Technical lead",
      "Sign-in logs, endpoint alerts, user interview"
     ],
     [
      "Is data exposed?",
      "Technical lead, privacy lead",
      "Mailbox access logs, downloads, forwarding rules"
     ],
     [
      "Is this one message or a campaign?",
      "Incident lead",
      "Recipient count, similar messages elsewhere"
     ],
     [
      "Is a payment request involved?",
      "Incident lead",
      "If yes, also open the business email compromise playbook"
     ]
    ]
   },
   "after": null,
   "note": null
  },
  "phishing-5": {
   "id": "phishing-5",
   "title": "Notices to check",
   "intro": "Open section 10 of the plan and confirm whether any of these start a notice clock.",
   "bullets": [
    "If personal data was accessed, start the data breach plan and the clocks in section 10.",
    "Report phishing to the national service for your country; CISA asks organizations to report to report@cisa.gov or its 24/7 line, and the FBI IC3 takes complaints."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "phishing-6": {
   "id": "phishing-6",
   "title": "Exit criteria and follow-up",
   "intro": "Close the playbook only when all of these are true.",
   "bullets": [
    "No malicious messages remain in any mailbox.",
    "Every exposed account is reset and its sessions are revoked.",
    "No new suspicious activity for [period].",
    "Detections and filters are updated, and staff are told the outcome."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "bec-1": {
   "id": "bec-1",
   "title": "When to use this playbook",
   "intro": "Use this playbook when a payment request, bank detail change or invoice looks fraudulent, when an executive or supplier email account may be controlled by someone else, or when funds may have been sent to a fraudulent account.",
   "bullets": [],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "bec-2": {
   "id": "bec-2",
   "title": "Before you start: prerequisites",
   "intro": "Complete these before an incident, as part of planning.",
   "bullets": [
    "The finance team has a call-back procedure on a known number for any change of bank details.",
    "The bank's fraud and recall contact is on the contact sheet, available 24 hours.",
    "Mailbox rules and forwarding can be listed for any user.",
    "Two-step sign-in is required on email accounts, preferably with phishing-resistant methods."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "bec-3": {
   "id": "bec-3",
   "title": "Workflow",
   "intro": "Work in this order. Record each step and its time in the incident log.",
   "bullets": [],
   "steps": [
    "If a payment was sent, call the bank immediately and ask for a recall and any indemnification documents. Time matters.",
    "File a complaint with the FBI IC3 (ic3.gov) as soon as possible, whatever the amount, so that it can help banks and law enforcement try to freeze funds.",
    "Find the account used: check the sender, reply-to address, look-alike domains, and mailbox rules or forwarding set by an intruder.",
    "Contain: reset the password, revoke sessions, remove the intruder's rules and forwarding on every affected mailbox.",
    "Verify any open payment requests by phone on a known number.",
    "Search for other victims inside and outside the company, and warn customers and suppliers whose details were used.",
    "Preserve the emails, headers and bank records."
   ],
   "table": null,
   "after": null,
   "note": null
  },
  "bec-4": {
   "id": "bec-4",
   "title": "Decision points",
   "intro": "Stop at each of these and record the decision, the decider and the time.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Decision",
     "Who decides",
     "Information needed"
    ],
    "rows": [
     [
      "Recall funds or accept the loss?",
      "Finance lead, executive sponsor",
      "Amount, bank guidance, time since the transfer"
     ],
     [
      "Is personal data exposed from the mailbox?",
      "Privacy lead",
      "Mailbox contents and access logs"
     ],
     [
      "Tell the insurer?",
      "Executive sponsor",
      "Policy terms; crime and cyber cover"
     ]
    ]
   },
   "after": null,
   "note": null
  },
  "bec-5": {
   "id": "bec-5",
   "title": "Notices to check",
   "intro": "Open section 10 of the plan and confirm whether any of these start a notice clock.",
   "bullets": [
    "If personal information of employees or customers was in the compromised mailbox, treat it as a possible data breach.",
    "Insurance notice may be required for both crime and cyber policies."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "bec-6": {
   "id": "bec-6",
   "title": "Exit criteria and follow-up",
   "intro": "Close the playbook only when all of these are true.",
   "bullets": [
    "Bank recall requested, and the IC3 complaint filed.",
    "Intruder access removed from every mailbox.",
    "The payment verification procedure is updated."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "malware-1": {
   "id": "malware-1",
   "title": "When to use this playbook",
   "intro": "Use this playbook when endpoint protection or a user reports malicious software on one or more devices. It excludes extortion cases, which are covered elsewhere.",
   "bullets": [],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "malware-2": {
   "id": "malware-2",
   "title": "Before you start: prerequisites",
   "intro": "Complete these before an incident, as part of planning.",
   "bullets": [
    "Endpoint detection and response or antivirus alerts reach a monitored place.",
    "Offline, tested backups exist for important data.",
    "Responders can isolate a device remotely.",
    "A clean rebuild image exists for each standard device."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "malware-3": {
   "id": "malware-3",
   "title": "Workflow",
   "intro": "Work in this order. Record each step and its time in the incident log.",
   "bullets": [],
   "steps": [
    "Validate the alert and identify the device, user and malware family if known.",
    "Short-term containment: isolate the device from the network. Do not power it off if memory evidence may be needed.",
    "Check for spread: other devices with the same file, shared drives, and accounts used on the device.",
    "Reset passwords and revoke sessions for any account that was used on the infected device.",
    "Take a backup image of the affected system before wiping it.",
    "Eradicate: reimage from a trusted source, replace compromised files with clean versions, and patch what was exploited.",
    "Recover: restore data from a verified backup onto the clean system, and watch it for signs of re-infection."
   ],
   "table": null,
   "after": null,
   "note": null
  },
  "malware-4": {
   "id": "malware-4",
   "title": "Decision points",
   "intro": "Stop at each of these and record the decision, the decider and the time.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Decision",
     "Who decides",
     "Information needed"
    ],
    "rows": [
     [
      "Is this a single device or a spread?",
      "Technical lead",
      "Alerts, file hashes, network connections"
     ],
     [
      "Rebuild or clean in place?",
      "Technical lead",
      "Malware type, risk of rootkits, time to rebuild"
     ],
     [
      "Is data stolen?",
      "Technical lead, privacy lead",
      "Outbound traffic, staging files, cloud sync"
     ]
    ]
   },
   "after": null,
   "note": null
  },
  "malware-5": {
   "id": "malware-5",
   "title": "Notices to check",
   "intro": "Open section 10 of the plan and confirm whether any of these start a notice clock.",
   "bullets": [
    "If data left the network, assess it under the data breach plan.",
    "If the malware reached systems that run a service for customers, check customer contract notice terms."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "malware-6": {
   "id": "malware-6",
   "title": "Exit criteria and follow-up",
   "intro": "Close the playbook only when all of these are true.",
   "bullets": [
    "Malware removed from every device or the device rebuilt.",
    "Credentials reset.",
    "No new alerts for [period].",
    "The infection route is found and closed."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "insider-1": {
   "id": "insider-1",
   "title": "When to use this playbook",
   "intro": "Use this playbook when an employee, contractor or other trusted person is suspected of misusing access, whether on purpose or by mistake.",
   "bullets": [],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "insider-2": {
   "id": "insider-2",
   "title": "Before you start: prerequisites",
   "intro": "Complete these before an incident, as part of planning.",
   "bullets": [
    "Human resources and legal have agreed in advance how an employee case is handled.",
    "Access to sensitive systems is logged and reviewable.",
    "A written policy tells staff what is acceptable and what is monitored, as the law in your location allows.",
    "Responders know who may disable a person's access, and on whose authority."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "insider-3": {
   "id": "insider-3",
   "title": "Workflow",
   "intro": "Work in this order. Record each step and its time in the incident log.",
   "bullets": [],
   "steps": [
    "Receive the concern and record it. Limit who knows to the people in the plan.",
    "Involve human resources and legal before any action against a person.",
    "Preserve evidence quietly: logs, mailbox, file access, device images where counsel agrees.",
    "Assess against behavior and facts, not assumptions. CISA describes the steps as define, detect and identify, assess, and manage.",
    "Contain access in a way the legal team has agreed, for example disabling accounts at the time of an interview.",
    "Recover assets: devices, keys, tokens and data copies.",
    "Decide actions with human resources and legal, and record them."
   ],
   "table": null,
   "after": null,
   "note": null
  },
  "insider-4": {
   "id": "insider-4",
   "title": "Decision points",
   "intro": "Stop at each of these and record the decision, the decider and the time.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Decision",
     "Who decides",
     "Information needed"
    ],
    "rows": [
     [
      "Is the act intentional or accidental?",
      "Human resources, legal",
      "Facts, intent indicators, history"
     ],
     [
      "When to remove access?",
      "Incident lead, human resources",
      "Risk of further harm versus risk to evidence"
     ],
     [
      "Involve law enforcement?",
      "Legal counsel, executive sponsor",
      "Nature of the act, data involved"
     ]
    ]
   },
   "after": null,
   "note": null
  },
  "insider-5": {
   "id": "insider-5",
   "title": "Notices to check",
   "intro": "Open section 10 of the plan and confirm whether any of these start a notice clock.",
   "bullets": [
    "If personal data left the organization, assess it under the data breach plan.",
    "Employment law may limit what can be monitored and what can be said."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "insider-6": {
   "id": "insider-6",
   "title": "Exit criteria and follow-up",
   "intro": "Close the playbook only when all of these are true.",
   "bullets": [
    "Access removed and assets recovered.",
    "Evidence stored under legal direction.",
    "Controls changed to reduce the chance of a repeat."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "lost-device-1": {
   "id": "lost-device-1",
   "title": "When to use this playbook",
   "intro": "Use this playbook when a laptop, phone, tablet, removable drive or paper record that holds business data is lost, stolen or misplaced.",
   "bullets": [],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "lost-device-2": {
   "id": "lost-device-2",
   "title": "Before you start: prerequisites",
   "intro": "Complete these before an incident, as part of planning.",
   "bullets": [
    "A current asset list says which devices hold which data.",
    "Devices are encrypted, and the list shows which ones are.",
    "Remote lock and wipe is set up and tested for phones and laptops.",
    "Staff know to report a loss at once, at any hour."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "lost-device-3": {
   "id": "lost-device-3",
   "title": "Workflow",
   "intro": "Work in this order. Record each step and its time in the incident log.",
   "bullets": [],
   "steps": [
    "Record when and where the loss was noticed, when it was last seen, and who had it.",
    "Lock or wipe the device remotely and revoke its sessions, tokens and certificates.",
    "Reset passwords for accounts that were signed in on the device.",
    "Find out what was on the device and whether it was encrypted and locked.",
    "Check logs for sign-in attempts from the device after the loss.",
    "If it may have been stolen, report to the police and record the report number.",
    "Decide whether this is a reportable breach, using the encryption facts."
   ],
   "table": null,
   "after": null,
   "note": null
  },
  "lost-device-4": {
   "id": "lost-device-4",
   "title": "Decision points",
   "intro": "Stop at each of these and record the decision, the decider and the time.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Decision",
     "Who decides",
     "Information needed"
    ],
    "rows": [
     [
      "Was the data protected by encryption?",
      "Technical lead",
      "Device encryption status and key handling"
     ],
     [
      "Is it a reportable breach?",
      "Privacy lead, legal",
      "Data types, people affected, rules in section 10"
     ],
     [
      "Wipe now or wait?",
      "Technical lead",
      "Chance of recovery versus risk of access"
     ]
    ]
   },
   "after": null,
   "note": null
  },
  "lost-device-5": {
   "id": "lost-device-5",
   "title": "Notices to check",
   "intro": "Open section 10 of the plan and confirm whether any of these start a notice clock.",
   "bullets": [
    "Under HIPAA, only unsecured protected health information triggers breach notice; the rule defines it by whether the information was rendered unusable, unreadable or indecipherable.",
    "Under GDPR Article 34, communication to individuals is not required if the data was protected by measures such as encryption that made it unintelligible to unauthorized people."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "lost-device-6": {
   "id": "lost-device-6",
   "title": "Exit criteria and follow-up",
   "intro": "Close the playbook only when all of these are true.",
   "bullets": [
    "The device is recovered or wiped, and sessions revoked.",
    "The reportability decision is recorded with reasons.",
    "The asset list is corrected."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "cloud-account-1": {
   "id": "cloud-account-1",
   "title": "When to use this playbook",
   "intro": "Use this playbook when a cloud identity, such as a user, administrator, service account or application, is used by someone other than its owner.",
   "bullets": [],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "cloud-account-2": {
   "id": "cloud-account-2",
   "title": "Before you start: prerequisites",
   "intro": "Complete these before an incident, as part of planning.",
   "bullets": [
    "Sign-in and audit logs are on and retained in the cloud tenant.",
    "The accounts that can grant application consent are known and limited.",
    "Two-step sign-in is required, with phishing-resistant methods for administrators.",
    "A break-glass administrator account exists and is stored securely."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "cloud-account-3": {
   "id": "cloud-account-3",
   "title": "Workflow",
   "intro": "Work in this order. Record each step and its time in the incident log.",
   "bullets": [],
   "steps": [
    "Identify the account, the time window and the indicators: unusual sign-ins, impossible travel, new devices, new mailbox rules, new application consents.",
    "Contain: revoke sessions and tokens, reset the password and require a fresh two-step enrollment.",
    "Review application consents granted by the user or tenant-wide, and remove any suspicious application. Check permissions such as read and send mail.",
    "Rotate administrator passwords, private keys and service account secrets where compromise is suspected.",
    "Review what the account could reach and what it did: mail, files, configuration changes, new accounts.",
    "Check other accounts for the same pattern, such as a password spray across many users.",
    "Restore changed settings and add detections for the technique."
   ],
   "table": null,
   "after": null,
   "note": null
  },
  "cloud-account-4": {
   "id": "cloud-account-4",
   "title": "Decision points",
   "intro": "Stop at each of these and record the decision, the decider and the time.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Decision",
     "Who decides",
     "Information needed"
    ],
    "rows": [
     [
      "Is it one account or many?",
      "Technical lead",
      "Sign-in patterns across accounts"
     ],
     [
      "Was an administrator account used?",
      "Technical lead, executive sponsor",
      "Role assignments, configuration changes"
     ],
     [
      "Was data accessed or sent out?",
      "Privacy lead",
      "Audit logs, downloads, forwarding"
     ]
    ]
   },
   "after": null,
   "note": null
  },
  "cloud-account-5": {
   "id": "cloud-account-5",
   "title": "Notices to check",
   "intro": "Open section 10 of the plan and confirm whether any of these start a notice clock.",
   "bullets": [
    "If personal data was accessed, start the data breach plan.",
    "If the cloud provider is a processor for your customers, check section 12 and customer notice terms."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "cloud-account-6": {
   "id": "cloud-account-6",
   "title": "Exit criteria and follow-up",
   "intro": "Close the playbook only when all of these are true.",
   "bullets": [
    "All sessions and tokens revoked; credentials rotated.",
    "No suspicious application consents remain.",
    "Detections are in place for the technique used."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "ddos-1": {
   "id": "ddos-1",
   "title": "When to use this playbook",
   "intro": "Use this playbook when a website, application or network service becomes slow or unavailable because of a flood of traffic or requests.",
   "bullets": [],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "ddos-2": {
   "id": "ddos-2",
   "title": "Before you start: prerequisites",
   "intro": "Complete these before an incident, as part of planning.",
   "bullets": [
    "Normal traffic baselines are known.",
    "Contacts at the internet provider, content delivery network and any DDoS mitigation service are on the contact sheet.",
    "The service has redundancy, load balancing and a way to scale.",
    "Communications for customers are ready, with a way to post status away from the affected service."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "ddos-3": {
   "id": "ddos-3",
   "title": "Workflow",
   "intro": "Work in this order. Record each step and its time in the incident log.",
   "bullets": [],
   "steps": [
    "Confirm it is an attack: check for unavailability, network congestion, unusual traffic patterns, server crashes, high resource use and trouble reaching other services such as DNS.",
    "Classify the technique: volumetric, protocol or application. The response differs by type.",
    "Call the upstream provider or mitigation service and ask for filtering.",
    "Apply filtering at the edge: rate limits, blocks on known malicious sources, and a challenge for web requests where suitable.",
    "Keep customers informed through a channel that does not depend on the affected service.",
    "After the attack: assess the impact, restore services, do a post-incident analysis, fix what was found and update the plan."
   ],
   "table": null,
   "after": null,
   "note": null
  },
  "ddos-4": {
   "id": "ddos-4",
   "title": "Decision points",
   "intro": "Stop at each of these and record the decision, the decider and the time.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Decision",
     "Who decides",
     "Information needed"
    ],
    "rows": [
     [
      "Switch to a mitigation service or failover?",
      "Technical lead, executive sponsor",
      "Attack type, cost, time to switch"
     ],
     [
      "Is the attack covering something else?",
      "Incident lead",
      "Other alerts, access attempts during the attack"
     ],
     [
      "What do we tell customers?",
      "Communications lead",
      "Impact, expected recovery time"
     ]
    ]
   },
   "after": null,
   "note": null
  },
  "ddos-5": {
   "id": "ddos-5",
   "title": "Notices to check",
   "intro": "Open section 10 of the plan and confirm whether any of these start a notice clock.",
   "bullets": [
    "A DDoS attack alone is an availability incident; check whether personal data was affected before treating it as a breach.",
    "Check contract service levels and customer notice terms."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "ddos-6": {
   "id": "ddos-6",
   "title": "Exit criteria and follow-up",
   "intro": "Close the playbook only when all of these are true.",
   "bullets": [
    "Service restored to normal levels.",
    "Traffic patterns back to baseline for [period].",
    "The plan is updated with what was learned."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "third-party-1": {
   "id": "third-party-1",
   "title": "When to use this playbook",
   "intro": "Use this playbook when a supplier tells you it has been compromised, when a supplier's product or update is malicious, or when a supplier holding your data may have lost control of it.",
   "bullets": [],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "third-party-2": {
   "id": "third-party-2",
   "title": "Before you start: prerequisites",
   "intro": "Complete these before an incident, as part of planning.",
   "bullets": [
    "Each critical supplier is on the list in section 12 with an incident contact and a contractual notice time.",
    "Contracts say what the supplier must tell you, how fast, and what it may do on your behalf.",
    "You know what data and access each supplier has.",
    "You have an exercise scenario that includes a supplier failure."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "third-party-3": {
   "id": "third-party-3",
   "title": "Workflow",
   "intro": "Work in this order. Record each step and its time in the incident log.",
   "bullets": [],
   "steps": [
    "Get the facts from the supplier: what happened, when, what of yours is affected, and what it has done.",
    "Check your own logs for activity linked to the supplier: connections, API calls, accounts and updates.",
    "Contain: suspend the supplier's access, rotate shared secrets and credentials, and block affected components.",
    "Assess your exposure: data held by the supplier, access it had to your systems, and customers who depend on it.",
    "Decide who must be told. A supplier that is a processor must tell you without undue delay under GDPR Article 33(2); a business associate must tell the covered entity under 45 CFR 164.410.",
    "Agree a shared communications line with the supplier.",
    "Review the contract and the supplier's assurance after the incident."
   ],
   "table": null,
   "after": null,
   "note": null
  },
  "third-party-4": {
   "id": "third-party-4",
   "title": "Decision points",
   "intro": "Stop at each of these and record the decision, the decider and the time.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Decision",
     "Who decides",
     "Information needed"
    ],
    "rows": [
     [
      "Suspend the supplier's access?",
      "Technical lead, executive sponsor",
      "Risk to your systems versus the business use"
     ],
     [
      "Are you the controller or covered entity with a notice duty?",
      "Privacy lead, legal",
      "Contract role, data involved"
     ],
     [
      "Switch suppliers?",
      "Executive sponsor",
      "Alternatives, time to switch"
     ]
    ]
   },
   "after": null,
   "note": null
  },
  "third-party-5": {
   "id": "third-party-5",
   "title": "Notices to check",
   "intro": "Open section 10 of the plan and confirm whether any of these start a notice clock.",
   "bullets": [
    "If you are the controller or covered entity, your own clock may have started when the supplier told you, or earlier if you would have known with reasonable diligence.",
    "Check customer contracts: your customers may expect notice because of your supplier's incident."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "third-party-6": {
   "id": "third-party-6",
   "title": "Exit criteria and follow-up",
   "intro": "Close the playbook only when all of these are true.",
   "bullets": [
    "Supplier access restored on agreed terms or ended.",
    "Shared secrets rotated.",
    "Contract and assurance updated."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "pt-1": {
   "id": "pt-1",
   "title": "Playbook header",
   "intro": "Fill in once per playbook.",
   "bullets": [
    "Name: [incident type].",
    "Owner: [role]. Approved on [date]. Review every [12 months].",
    "Use when: [trigger in one sentence].",
    "Do not use when: [what belongs to another playbook]."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "pt-2": {
   "id": "pt-2",
   "title": "Prerequisites",
   "intro": "What must be in place before an incident.",
   "bullets": [
    "Logs to be on: [list].",
    "Access and roles responders need: [list].",
    "Tools and contacts: [list]."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "pt-3": {
   "id": "pt-3",
   "title": "Workflow",
   "intro": "Numbered steps in order. One action per step. Name the role.",
   "bullets": [],
   "steps": [
    "[Step 1: action, role, expected result]",
    "[Step 2]",
    "[Step 3]"
   ],
   "table": null,
   "after": null,
   "note": null
  },
  "pt-4": {
   "id": "pt-4",
   "title": "Decision points",
   "intro": "Each point where a person must decide.",
   "bullets": [],
   "steps": [],
   "table": {
    "head": [
     "Decision",
     "Who decides",
     "Information needed",
     "If yes",
     "If no"
    ],
    "rows": [
     [
      "[question]",
      "[role]",
      "[facts]",
      "[next step]",
      "[next step]"
     ]
    ]
   },
   "after": null,
   "note": null
  },
  "pt-5": {
   "id": "pt-5",
   "title": "Checklist",
   "intro": "A tick-list that mirrors the workflow, for regulated settings.",
   "bullets": [
    "[ ] [Step 1 done, time, by]",
    "[ ] [Step 2 done, time, by]"
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  },
  "pt-6": {
   "id": "pt-6",
   "title": "Exit criteria and follow-up",
   "intro": "When to close and what to update.",
   "bullets": [
    "Exit when: [criteria].",
    "Update: [plan, detections, contacts].",
    "Review date: [date]."
   ],
   "steps": [],
   "table": null,
   "after": null,
   "note": null
  }
 }
}