Sectors
Scenarios describe what happened. Sectors describe who you are: the rules you report under, the clocks that start, the records you keep and the words your colleagues use. Work the sector page with the phase playbook for your step and the scenario for the incident. A ransomware incident at a federal agency uses the ransomware scenario and the federal civilian page together. The kit builder puts a sector, a scenario and a cloud provider on one sheet.
Each sector page has the same parts: reporting obligations with their clocks, a terms crosswalk and a roles crosswalk. It then lists what changes in each phase, what changes in the records, and the bodies you work with. Counsel decides which obligations apply to your organization. Incident Command seats for each sector are on Command by incident type.
| Sector | Use it when | What it adds |
|---|---|---|
| Federal civilian agencies | The incident affects a federal civilian executive branch agency, its systems or its data, including systems a contractor runs for it | CISA reporting, major incident determination and congressional notification, breach response under OMB policy, federal terms and roles |
| Defense and defense contractors | The incident affects the Department of Defense, or a contractor that handles controlled unclassified information or supports a defense contract | DFARS 252.204-7012 reporting through DIBNet, media preservation, DoD incident categories, CMMC, defense terms and roles |
| Healthcare | The incident affects a hospital, health system, clinic, health plan, clearinghouse, or a business associate handling protected health information | HIPAA breach notification and its clocks, clinical downtime and diversion, medical devices, Health-ISAC and HHS, healthcare terms and roles |
| Financial services | The incident affects a bank, credit union, broker-dealer, investment adviser, insurer, fintech, payment processor or money transmitter | Banking agency 36-hour notice, SEC, FTC, NYDFS and state rules, card brand and payment network duties, suspicious activity reporting, FS-ISAC, financial terms and roles |
| Energy and water utilities | The incident affects an electric utility or other bulk electric system owner, a nuclear plant, an oil or gas pipeline, or a drinking water or wastewater system | NERC CIP-008 and Form DOE-417 first-hour reports, NRC cyber event notices, TSA pipeline reporting, water public notice and state rules, engineering sign-off, energy and water terms and roles |
| Transportation | The incident affects a freight railroad, passenger railroad, rail transit or bus system, airport, air carrier, or an MTSA vessel, port facility or outer continental shelf facility | TSA directive and security program reporting to CISA, Coast Guard reporting to the National Response Center, FTA two-hour safety event notice, train control and safety certification, transportation ISACs, transportation terms and roles |
| State and local government | The incident affects a state, county, city, town, tribe or territory, including its police, courts, elections office or agencies that receive federal tax, Social Security or criminal justice data | State incident reporting laws and their clocks, ransom payment limits, CJIS, IRS Publication 1075 and SSA reporting, public records and open meetings, MS-ISAC and fusion centers, government terms and roles |
| Education | The incident affects a K-12 district or school, a college or university, a university research enterprise, or a vendor or servicer that handles student records or Title IV student aid data | FERPA records of disclosure, the 24-hour Federal Student Aid report, the FTC Safeguards Rule notice, New York and Illinois student data clocks, Clery emergency notification, K12 SIX and REN-ISAC, education terms and roles |
This section is an addition to the book.