Command by incident type
The seats on The organization fit every incident. Each incident type, and each regulated sector, adds people to command and fills some seats earlier than the usual triggers. It also reserves decisions for the executive group and adds constraints to the Incident Action Plan. The org chart builder draws the seats for a type and sector at each size.
Check the organization against the type at each objectives meeting. An exploited edge device that leads to ransomware is two types, and needs the seats of both. The incident types come first, then the sectors.
| Incident type | Seats to add |
|---|---|
| Ransomware | Legal advisor and Finance/Admin in the first hour, a negotiator, Intelligence/Investigations as a section, the crisis team |
| Insider | HR and the Legal advisor in command, Intelligence/Investigations with evidence custody |
| Fraud and business email compromise | Finance leadership in unified command, Finance/Admin and Liaison in the first hour |
| Operational technology | Engineering and plant operations in unified command, the Safety Officer in the first hour, an OT branch |
| Supply chain or third party | The supplier where its role puts it, a Technical Specialist on its advisories |
| Regulated or restricted data | Counsel in unified command, the privacy officer as a Technical Specialist |
| Edge device mass exploitation | Network owners in unified command, a Technical Specialist on vendor and CISA guidance |
| Identity provider compromise | Identity leadership in unified command, an identity task force, Logistics first |
| Distributed denial of service | Network and service owners in unified command, Liaison to the providers in the first hour, a second-intrusion watch |
| Customer account takeover | Product, fraud and support leaders in unified command, Finance/Admin on payouts and chargebacks, the Public Information Officer on customer notices and the support script |
Ransomware
Command. Technology leadership joins unified command, because systems will be isolated, rebuilt and restored. The affected business joins when operations stop. The Legal advisor sits with command from the first hour.
Seats. Finance/Admin gives the insurer notice in the first period. Liaison takes law enforcement and the insurer. Intelligence/Investigations becomes its own section once an outside firm or counsel directs the investigation. The crisis team runs manual workarounds.
Executive group decides. Any contact with the attacker, any payment, the restore order for business systems, taking a line of business offline, and public disclosure.
Write into the IAP. No contact with the attacker except through the negotiator. The ransom note's victim identifier and portal address go only to the negotiator, the Incident Commander and counsel. Encrypted systems stay isolated as evidence. Restores use backups dated before initial access, in the order the executive group set, which changes only by a new entry in the decision register.
Technical steps. PIVTR-D ransomware scenario.
The payment decision path
The Incident Commander runs the path and the executive group decides, under the written position in the PIVTR-D authority matrix.
| # | Item | Owner |
|---|---|---|
| 1 | Written ransom position retrieved, and the deciding executives confirmed | Incident Commander |
| 2 | Recovery without payment estimated: clean backups, restore times, decryptors | Operations |
| 3 | Exfiltration confidence rated and passed to counsel | Intelligence/Investigations |
| 4 | The group, its aliases and every payment address screened for sanctions by counsel experienced in ransomware | Legal advisor |
| 5 | Law enforcement told, and its requests recorded | Liaison |
| 6 | Insurer's coverage position recorded, with written consent where the policy requires it | Finance/Admin |
| 7 | Options and counsel's advice put to the executive group as an executive decision request | Incident Commander |
| 8 | Decision entered in the register, naming counsel and the carrier consulted | Planning |
| 9 | Reporting duties after any payment checked against notification deadlines | Legal advisor |
OFAC's advisory of September 21, 2021 states that the US government strongly discourages paying ransom or extortion demands.
OFAC can impose civil penalties on strict liability, even when the payer did not know the recipient was sanctioned. It counts a self-initiated, complete report to law enforcement or other relevant US government agencies, such as CISA, made as soon as possible after discovery, as a significant mitigating factor. Its listings of digital currency addresses are not likely to be exhaustive, so a clean address check settles nothing alone.
Sources: OFAC ransomware advisory, checked October 2026; OFAC FAQ 562, checked September 2026.
The negotiator and the attacker channel
FEMA's ICS 300 course places Technical Specialists in Planning or wherever their services are required. Assign the negotiator, as a Technical Specialist, to Intelligence/Investigations, which keeps what is known about the group, or to Planning while Intelligence/Investigations sits inside Operations. Engage the negotiator through counsel when counsel directs the investigation.
- The negotiator owns the attacker channel: one account, and every message saved word for word with its time.
- Nothing goes to the attacker without the Incident Commander's approval and counsel's review, inside limits the executive group set.
- The Public Information Officer owns leak-site monitoring, as in the PIVTR-D scenario. Intelligence/Investigations watches the site and reports each post to the Public Information Officer, Incident Commander and Legal advisor.
Technical Specialists: ICS-300, Lesson 2: Staffing Fundamentals.
Insider
Command. HR and the Legal advisor sit in command with the Incident Commander. HR has authority over the employment action, which meets the test for unified command. Where HR stays outside unified command, the Liaison carries HR's input, as in the PIVTR-D scenario. If the subject sits on the executive group, the chief executive names a replacement on counsel's advice, or the board does when the subject is the chief executive.
Seats. Intelligence/Investigations runs as its own section with evidence custody, because the investigation is the main effort. The Safety Officer works with HR and physical security when anyone fears for their safety.
Need to know. ICS runs in the open: the IAP, the organization list and the roster go to every supervisor, and anyone on the incident reads the common operating picture. An insider case closes that down.
- Planning keeps a restricted roster that counsel approves. Nobody works the incident until counsel has added them and they are briefed on confidentiality.
- The incident, the subject and each channel get code names. The subject's name stays out of tickets, calendar invitations, chat and the ICS 209.
- Channels run where the subject has no administrator or reader access, which can rule out corporate chat and ticketing.
- The subject's manager and peers stay off the roster unless counsel approves.
- The IAP goes to named people only, and no distribution list carries it.
Executive group decides. Law enforcement referral on counsel's advice, civil action, and statements to customers or regulators.
Write into the IAP. The posture, covert or overt, and the monitoring counsel approved. No account change without HR and counsel. Preservation before any termination step. The code names and where the roster is kept.
Technical steps. PIVTR-D insider scenario.
Fraud and business email compromise
Command. Finance leadership joins unified command, because the loss is money and the payment decisions are theirs. Finance/Admin calls the bank for a recall in the first hour, before the organization is built.
Seats. Finance/Admin works with the bank and accounts payable. Liaison works with law enforcement and every counterparty that received a fraudulent message. The Legal advisor rates the data the attacker could read.
Executive group decides. Pausing a payment run or all outbound payments, whether to pay a genuine supplier whose invoice went to the fraudulent account, and any broad notice to customers or suppliers.
Write into the IAP. No change to payment details without a call back to a number already on file. Payments to recently changed bank details paused. Every inbox rule and grant exported as evidence before removal.
Technical steps. PIVTR-D BEC scenario.
Operational technology
Command. OT engineering and plant operations leadership join unified command whenever plant or physical systems are affected or at risk.
Seats. The Safety Officer from the first hour. FEMA's ICS 300 course gives the Safety Officer emergency authority to stop unsafe acts, which in OT covers any action that could touch a physical process. An OT branch under Operations, led by a plant engineer. Logistics for radios, PPE and staff for manual operation.
Executive group decides. Stopping or restarting production or service, and running for days under manual control. Plant operations stops a process at once when safety requires it, and tells command after. The Incident Commander decides island mode, with operations and the Safety Officer.
Approvals. The IAP names the engineers who may sign off for each plant area. No containment, eradication or recovery step on OT runs until one of them has signed it and the Safety Officer has reviewed it in the ICS 215A. Each sign-off goes into the PIVTR-D containment decision record, T3.
Write into the IAP. The actions that need sign-off. Automatic EDR isolation turned off on OT hosts. Vendor remote access confined to a jump host. The trigger conditions for a controlled safe shutdown.
Technical steps. PIVTR-D OT scenario.
Safety Officer authority: ICS-300, Lesson 2: Staffing Fundamentals.
Supply chain or third party
Command. Place the supplier, including a SaaS vendor, with the table on When a partner runs your infrastructure. The choices are separate commands, an assisting organization inside Operations, or unified command for a partner with authority over part of the response.
Seats. Liaison as the single contact, logging each supplier statement about scope with its time, because early statements change. A Technical Specialist tracking the supplier's advisories for Planning. The Legal advisor for the contract and notification duties.
Executive group decides. Suspending a supplier that runs a business process, naming it in public, claims against it, and the customer advisory when your own pipeline shipped malicious code.
Write into the IAP. What may be shared with the supplier, as counsel set it. Actions the supplier may take on its own authority. Platform logs exported before any token is revoked, and the supplier's evidence requested on PIVTR-D T19.
Technical steps. PIVTR-D supply chain and SaaS OAuth scenarios.
Regulated or restricted data breach
Command. Counsel joins unified command, because notification and legal exposure drive the decisions. So does the owner of the commitment that sets the boundary, such as a government contract or a data residency agreement.
Seats. The privacy officer or data protection officer, as a Technical Specialist beside the Legal advisor. The GDPR requires that the data protection officer be involved, properly and in a timely manner, in all issues relating to personal data protection. Planning tracks each notification clock in the ICS 209. Notices use PIVTR-D T16 and T17, approved by the Legal advisor. Finance/Admin buys mailing, call center and credit monitoring.
Executive group decides. Public disclosure, any materiality determination for securities reporting, and offers to affected people beyond what the law requires.
Write into the IAP. Privilege routing. Each clock, with who decided it had started and when. Preservation before any stray copy is deleted. Facts kept apart from assessments in every report.
Technical steps. PIVTR-D restricted data scenario.
Data protection officer: GDPR, Article 38(1).
Edge device mass exploitation
Command. Network and remote access owners join unified command, because taking the devices offline cuts off staff or customers.
Seats. A Technical Specialist tracking vendor and CISA guidance for Planning each period, because mitigations change. Liaison with vendor support. Logistics for replacement hardware and temporary remote access. Intelligence/Investigations to hunt through every credential the device handled.
Executive group decides. Disconnecting remote access, or accepting the exposure while a fix is pending. On January 31, 2024, CISA ordered federal civilian agencies to disconnect every Ivanti Connect Secure and Policy Secure instance by February 2. The order also required agencies to treat associated domain accounts as compromised, and to factory reset and rebuild each device before reconnecting it.
Write into the IAP. Device images and logs preserved before any reset. Every credential that passed through the device treated as compromised. No device cleared on the vendor's integrity check alone. CISA and its partners reported in February 2024 that the Ivanti Integrity Checker Tool could be deceived, and that an actor may keep root-level persistence through a factory reset.
Technical steps. PIVTR-D edge device scenario.
Sources, checked October 2026: CISA, Supplemental Direction V1: ED 24-01; CISA Ivanti advisory, February 29, 2024.
Identity provider compromise
Command. Identity and access leadership joins unified command. The identity provider's vendor works through Liaison, or joins unified command when its own platform was breached.
Seats. Logistics first: every responder moves to accounts, devices and channels independent of the identity provider before the planned changes to the tenant. Emergency containment, such as removing an attacker's administrator role, goes ahead at once. An identity task force under Operations. Intelligence/Investigations treats every federated application as in scope until cleared.
Executive group decides. Signing everyone out and forcing password resets or MFA re-enrollment, cutting federation to business applications, and the downtime either one causes.
Write into the IAP. Identity provider changes made only from clean administrative workstations, by named administrators, each entered in the decision register. Help desk resets of passwords and MFA only after a call back to a number on file. Requests by chat or email confirmed by voice.
Technical steps. PIVTR-D identity scenario.
Distributed denial of service
Command. Network and service owners join unified command, because diversion, blocks and turned-off features change what customers can reach. The affected business joins when a customer-facing service fails.
Seats. Liaison opens cases with the ISP and the DDoS mitigation or CDN provider in the first hour. Finance/Admin approves emergency provider onboarding and later files any cost concession. Intelligence/Investigations keeps one analyst on identity, endpoint, email and outbound alerts for the length of the attack, apart from the analysts fighting the traffic. The Public Information Officer runs the status page.
Executive group decides. Blackholing an address, blocking a country, turning off a customer-facing feature, emergency spending with a mitigation provider, and the position on any extortion demand. OFAC's September 21, 2021 advisory says the US government strongly discourages paying ransom or extortion demands.
Write into the IAP. No reply to an extortion sender, as FBI PSA I-073115-PSA advises. The note is preserved with full headers and reported at ic3.gov. Every rule, block and diversion has an owner and an end time in the containment record. The second-intrusion watch closes only on the analyst's report.
Technical steps. PIVTR-D distributed denial of service scenario. Exercise it with the extortion and account takeover tabletop.
Sources, checked November 2026: CISA, FBI and MS-ISAC, Understanding and Responding to Distributed Denial-of-Service Attacks, March 21, 2024; FBI PSA I-073115-PSA; OFAC ransomware advisory.
Customer account takeover
Command. Product, fraud and customer support leaders join unified command, because containment changes what customers see at login and what support tells them.
Seats. Intelligence/Investigations tracks attack sources and confirmed takeovers for Planning each period. Finance/Admin runs payout freezes, refunds and chargebacks with the payment processor. The Public Information Officer owns customer notices and the support agent script. Liaison files with IC3 and requests phishing site takedowns.
Executive group decides. Forcing password resets on confirmed takeovers alone or on every account whose credentials worked, moving bot rules from challenge to block, the refund policy, and requiring MFA for all customers. In June 2025 the UK Information Commissioner's Office fined 23andMe £2.31 million after credential stuffing, and listed the lack of mandatory multi-factor authentication among its failures.
Write into the IAP. Payout and contact detail freezes stay in force until each owner passes verification. Every forced reset revokes the account's sessions and refresh tokens in the same change. Support agents never ask for a password or one-time code. Bot and rate limit changes start in challenge mode and go into the decision register.
Technical steps. PIVTR-D customer account takeover scenario. Exercise it with the extortion and account takeover tabletop.
Sources, checked November 2026: ICO, 23andMe fined £2.31 million, June 17, 2025; New York Attorney General, Business guide for credential-stuffing attacks; NIST SP 800-63B-4.
Sectors
A regulated sector adds its regulator's clocks, its own approvers and its own reporting channels to whichever incident type is running. Apply the sector block with the type block. The rules behind each block are on the PIVTR-D sector pages.
| Sector | Seats to add |
|---|---|
| Federal civilian agency | The CIO in the executive group, the Senior Agency Official for Privacy when personal data is involved, Liaison to CISA, OMB, the FBI and the Inspector General |
| Defense contractor | Government contracts counsel in unified command, the facility security officer at a cleared facility, Liaison with a DoD medium assurance certificate |
| Healthcare organization | The hospital incident commander in unified command under HICS, the Privacy Officer, a clinical systems branch led by the CMIO or CNIO, the Safety Officer in the first hour |
| Financial institution | Counsel and payments operations in unified command, the BSA officer beside the Legal advisor, Liaison to regulators, the acquirer and service providers |
| Energy or water utility | System operations and engineering in unified command, the reliability coordinator through Liaison, the NERC compliance lead in Planning, the Safety Officer in the first hour |
| Transportation operator | The OCC or operations control superintendent in unified command, signals and train control engineering under Operations, the Cybersecurity Coordinator or Cybersecurity Officer as Liaison, the Safety Officer in the first hour |
| State and local government | Executive group: elected leadership and the manager or administrator. Also the emergency manager and EOC, and the police chief or sheriff for public safety systems. Liaison works with the state reporting agency, the CSA ISO and the IRS Office of Safeguards |
| Education institution | Counsel and the privacy officer in unified command, the registrar and financial aid director beside Planning and Liaison, the Clery officer as Safety Officer, Liaison to Federal Student Aid and the SIS vendor |
Federal civilian agency
Command. The CISO or a delegate commands. The CIO joins the executive group with the agency head's delegate, because the CIO takes part in the major incident determination. When personally identifiable information is involved, the Senior Agency Official for Privacy joins unified command and leads the breach response team.
Seats. Liaison reports to CISA within the first hour, then to CISA and OMB within 1 hour of a major incident determination. Liaison also reports to the FBI and the Office of Inspector General as agency procedures require, and works with legislative affairs on the 7-day congressional notice. When a CISA hunt or response team arrives, Logistics provides its access. Planning records the time the SOC identified the incident and the time of the major incident determination, because both start federal clocks.
Executive group decides. The major incident determination, notice to affected individuals (the agency head's decision), and public statements.
Approvals. The authorizing official approves containment and restoration on each system that official authorized.
Sector rules. PIVTR-D federal civilian agencies.
Sources, checked October 2026: OMB M-25-04; OMB M-17-12; CISA Federal Incident Notification Guidelines.
Defense contractor
Command. Government contracts counsel joins unified command when the incident touches covered defense information or operationally critical support. At a cleared facility, the facility security officer joins too, because classified systems follow DCSA direction.
Seats. Liaison has a DoD medium assurance certificate and files the DIBNet report within 72 hours of discovery. Liaison also carries contracting officer requests. The Legal advisor approves every report. Planning tracks the 72-hour clock and the 90-day media preservation in the ICS 209. The ISSM leads a classified systems branch under Operations.
Executive group decides. Any statement to DoD about the SPRS score or a CMMC affirmation, and whether to join the voluntary DIB CS Program.
Write into the IAP. Images and packet captures taken before any rebuild. Malware sent to DC3 only, and none of it to the contracting officer. Spilled classified information kept out of tickets and chat.
Sector rules. PIVTR-D defense and defense contractors.
Sources, checked October 2026: DFARS 252.204-7012; PGI 204.7303-3; 32 CFR Part 117.
Healthcare organization
Command. A hospital manages the event under the Hospital Incident Command System (HICS), which keeps the ICS Command and General Staff. Form unified command: the hospital incident commander for patient care, the cyber Incident Commander for the response. The nursing supervisor can command at night until the administrator on call arrives.
Seats. The Privacy Officer as a Technical Specialist beside the Legal advisor. The CMIO or CNIO leads a clinical systems branch under Operations, with clinical engineering for devices. The Safety Officer from the first hour. Liaison takes the local EMS agency, the state health department and business associates. Planning tracks the 60-day HIPAA clock from discovery and any law enforcement delay under 164.412.
Executive group decides. Canceled elective care, public statements, and delegating breach notice to a business associate. The hospital incident commander declares ambulance diversion under the criteria agreed with the local EMS agency, without waiting for the executive group, and informs it.
Approvals. The CMIO or CNIO approves taking a clinical system or device offline, and restoring it. When active destruction forces an immediate cut, the Incident Commander orders it, downtime starts at once, and the decision goes in the decision register.
Write into the IAP. Downtime procedures in force by unit. Diversion status. No PHI in tickets or chat beyond the minimum necessary.
Sector rules. PIVTR-D healthcare organizations.
Sources, checked October 2026: 45 CFR 164 Subpart D; California EMS Authority, HICS.
Financial institution
Command. Counsel joins unified command, because one incident can start banking agency, SEC, NYDFS, card brand and FinCEN duties at once. Treasury and payments operations join when payments, settlement or customer access are affected.
Seats. The Incident Commander puts the notification incident question to the named decider and counsel at the first triage brief, and at each brief after until it is decided. Planning records each decision that starts a clock. The clocks are 36 hours for the banking agencies, 72 hours for NCUA and NYDFS, and 3 calendar days for Visa after a reasonable suspicion of a compromise. They are 30 days for Regulation S-P and the FTC Safeguards Rule, and 4 business days after a materiality determination. Liaison files regulator notices and works with the acquirer and bank service providers. The BSA officer works beside the Legal advisor. Investor relations works with the Public Information Officer.
Executive group decides. Materiality, through the disclosure committee, pausing or rerouting payments, and any ransom payment after OFAC screening.
Write into the IAP. Card systems isolated at the network and left running for the PFI. No mention of a SAR in the IAP, the ICS 209 or any briefing.
Sector rules. PIVTR-D financial services.
Sources, checked October 2026: 12 CFR Part 53; 23 NYCRR 500.17; 31 CFR 1020.320; Visa What To Do If Compromised.
Energy or water utility
Command. Form unified command: the control room shift supervisor or plant manager for the physical process, the cyber Incident Commander for the response. At a nuclear plant the shift manager commands the plant under its emergency plan. Operators stop a process or shed load at once when safety or reliability requires it, and tell command after.
Seats. The Safety Officer from the first hour. An OT branch under Operations, led by protection, control or SCADA engineers. Liaison takes the reliability coordinator, E-ISAC, CISA, DOE, the NRC, TSA and the primacy agency. The NERC compliance lead works in Planning beside the Legal advisor and records two times for every event: when the incident occurred, which starts Form DOE-417, and when it was determined reportable, which starts CIP-008. Logistics takes mutual assistance crews and equipment.
Executive group decides. Running for days under manual control, taking a plant or pipeline out of service, and public statements. The Incident Commander decides island mode with operations, the Safety Officer and, for the grid, the reliability coordinator.
Approvals. No containment, eradication or recovery step on the EMS, SCADA, relays or controllers runs until a named engineer signs it in PIVTR-D T3 and the Safety Officer has reviewed it.
Write into the IAP. Each reporting clock and its start time. Automatic endpoint isolation turned off on OT hosts. Logs from access control and monitoring systems copied before CIP-007's 90-day rollover. BES Cyber System Information marked in evidence and sent only to authorized recipients.
Sector rules. PIVTR-D energy and water utilities.
Sources, checked November 2026: FERC letter order approving CIP-008-6; Form DOE-417 instructions; 10 CFR 73.77; TSA Security Directive Pipeline-2021-01D; 40 CFR 141.202.
Transportation operator
Command. The operations control center (OCC), dispatch or airport operations leader joins unified command with the cyber Incident Commander, because service and safety decisions belong to operations. At a port, brief the Captain of the Port (COTP) early; the COTP has authority over the port zone.
Seats. The Safety Officer from the first hour, with the chief safety officer. Signals and train control engineering leads an OT branch under Operations. The TSA Cybersecurity Coordinator or the Coast Guard Cybersecurity Officer sits with Liaison and files the CISA or National Response Center (NRC) report. Planning records the identification time, because the TSA clock starts there.
Executive group decides. Suspending or restricting revenue service across a system, running for days on manual operation, and public statements. The OCC stops trains or vehicles at once when safety requires it, and tells command after.
Approvals. Signals engineering and the OCC approve every containment, eradication and recovery step on train control, PTC, CBTC, SCADA and wayside systems in PIVTR-D T3. The Safety Officer decides whether a restored safety-critical system needs safety certification before revenue service, recorded in T7.
Write into the IAP. Service status by line, terminal or berth. Automatic EDR isolation off on OCC, wayside and SCADA hosts. Each reporting clock. Rail and transit directives: 72 hours to CISA. Pipeline directives and aviation security programs: 24 hours (for aviation, confirm against your TSA-approved security program). Maritime: without delay to the National Response Center. A listed safety event: 2 hours to the State Safety Oversight Agency and FTA. Sensitive Security Information kept out of tickets, chat and public statements.
Sector rules. PIVTR-D transportation.
Sources, checked November 2026: TSA notice of September 1, 2026; SD 1582-21-01C; Coast Guard final rule; FTA two-hour guide.
State and local government
Command. The CISO or IT director commands the cyber response. When services to the public stop, the emergency manager opens the emergency operations center (EOC) and forms unified command with the cyber Incident Commander. When police, dispatch or jail systems are affected, the police chief or sheriff joins unified command.
Seats. Liaison files the state report within the statute's clock: 72 hours in New York, 24 hours in Virginia, 48 hours in Florida (12 hours for ransomware), 7 days in Ohio. Staff report a suspected criminal justice data incident to the agency's incident response capability within 1 hour, and Liaison passes confirmed incidents to the CJIS Systems Agency. Liaison also reports to TIGTA and the IRS Office of Safeguards within 24 hours for federal tax information, and to SSA under its agreement. The Local Agency Security Officer sits as a Technical Specialist under Intelligence/Investigations. Planning logs public records requests and records who decided each clock started.
Executive group decides. An emergency declaration, requests for the National Guard or mutual aid, public statements, and any ransom question, which state law may bar or route to the governing body.
Approvals. The police chief or sheriff approves isolating dispatch, records or jail systems. The election official approves actions on registration and voting systems.
Write into the IAP. Manual procedures in force for 911, courts, permits and payroll. Which briefings to elected officials go to closed session under counsel's advice.
Sector rules. PIVTR-D state and local government.
Sources, checked November 2026: New York DHSES; Code of Virginia 2.2-5514; Florida Statutes 282.3185; Ohio Revised Code 9.64; California DOJ bulletin 2026-ISRS-001 on CJIS Security Policy v6.1; IRS reporting page.
Education institution
Command. The CISO or technology director commands. Counsel and the privacy officer join unified command, because student records, Title IV aid data and health records follow different rules. At a university with a hospital or clinic, the HIPAA privacy officer joins for health records.
Seats. Liaison files the Federal Student Aid breach report within 24 hours of identifying the incident, and works with the SIS and other student data vendors. The registrar works under Planning and enters the FERPA record of each disclosure. The financial aid director confirms which Title IV systems were touched. The Clery compliance officer sits as Safety Officer and decides on any emergency notification. Planning tracks the FTC 30-day clock and each state clock, such as New York's 10 calendar days to the State Education Department.
Executive group decides. School or campus closure, family and campus statements, any ransom payment after sanctions screening, and who sends notices when a vendor offers to send them.
Write into the IAP. The time the incident was known or identified. The Clery decision and its basis. Student PII kept out of tickets and chat beyond what responders need. Vendor support and integration accounts disabled until reset.
Sector rules. PIVTR-D education.
Sources, checked November 2026: 34 CFR Part 99; FSA GENERAL-24-46; 16 CFR 314.4(j); 34 CFR 668.46; 8 NYCRR 121.10.