Templates
Each record copies to the clipboard. Where a template overlaps an ICS form from the companion Incident Command guide, Which document is the record says which one to keep. The KEY TIMES in T1 are defined on the metrics page, and T10 and T15 take their durations from them.
T14 and T15 are Debrief records. The Public Information Officer drafts T16 and counsel adapts it to each jurisdiction before it goes out, because the laws ask for different content. California requires a general description of the breach, for example, and Massachusetts requires the notice to residents to leave out the nature of the breach and the number of residents affected.
Open one T17 for each regime on the notification deadlines list that counsel decides applies. The Public Information Officer approves T18, and counsel signs off every statement to the media or the public, as who authorizes what requires. Counsel reviews T19 before it is sent.
T1. Incident record, opened at verification
INCIDENT ID :
TITLE :
HANDLER : (who opened this record)
INCIDENT COMMANDER : (name; update at each transfer)
OUT-OF-BAND CHANNEL:
REPORTED : (date, time, zone)
REPORT SOURCE : user | alert | hunt | partner | customer |
researcher | law enforcement | vendor | other
CLASSIFICATION : ransomware | business email compromise | cloud |
insider | supply chain | operational technology |
restricted data | SaaS or OAuth abuse |
edge device | identity provider |
AI application | denial of service |
customer account takeover | other
SECTOR RULES : federal civilian | defense | healthcare |
financial | energy and water | transportation |
state and local | education | none
(open the sector page)
INITIAL RISK : low | medium | high | critical (SEV 4 to SEV 1)
RISK RATIONALE :
SUMMARY :
EVIDENCE REFS :
VERIFY DECISION : continue | stop | defer
RATIONALE :
DEFER REVIEW BY : (date, time, zone; defer only)
DECIDED BY / AT :
CONTAINMENT TRIGGERS (yes or no for each; see Decide)
active destruction :
exfiltration :
safety or critical systems :
regulatory clock :
COUNSEL NOTIFIED : (name, time) or the reason they were not
KEY TIMES (date, time, zone; revise as scoping learns more)
compromise start : (earliest evidence of attacker activity)
detected :
verified :
contained :
eradicated :
recovered :
T2. Triage brief to decision makers
INCIDENT ID : AS OF : (time of this brief) WHAT WE KNOW : (facts only, three lines maximum) 1. 2. 3. WHAT WE DO NOT KNOW: 1. 2. SYSTEMS IN SCOPE : (counts by class: servers, workstations, cloud, identities) BUSINESS EXPOSURE : revenue | regulated data | safety | contractual PROPOSED POSTURE : passive | adaptive | active | deceptive ACTION REQUESTED : (the one authorization you need) IF APPROVED : (impact) IF DEFERRED : (impact) DECISION / BY / AT : NEXT UPDATE : (date, time, zone; by the risk level's cadence)
T3. Containment decision record
INCIDENT ID :
ACTION :
SYSTEMS / ACCOUNTS :
LAYER : network | host | application | identity
TRIGGER : active destruction | exfiltration | safety |
regulatory clock | judgment call
POSTURE : passive | adaptive | active | deceptive
AUTHORIZED BY : (per authority matrix)
BUSINESS IMPACT : (assessed before execution)
EXECUTED AT : (simultaneous across teams where possible)
ROLLBACK PROCEDURE :
VALIDATION
network : pass | fail - what was checked
process : pass | fail - what was checked
logs : pass | fail - what was checked
VALIDATED BY / AT :
T4. Loop iteration log
INCIDENT ID :
ITERATION # :
OPENED AT :
TRIGGER TYPE : new indicator | scope expansion |
incomplete eradication | analysis revelation |
business change
TRIGGER DETAIL :
CHANGES TO
scope :
containment :
eradication :
recovery :
NEW INDICATORS :
CLOSED AT :
CARRIED FORWARD : (what the next iteration inherits)
T5. Technical closure
INCIDENT ID : ITERATIONS RUN : No new indicators in scoping since : Monitoring clean since : Eradication verified : method / analyst / date Restored systems nominal since : Outstanding visibility gaps : Monitoring retained, and for how long: TECHNICAL CLOSURE BY : (name, role) DATE / TIME :
T6. Residual risk acceptance
INCIDENT ID : RESIDUAL RISKS ACCEPTED (one line each, plain language) 1. 2. 3. COMPENSATING CONTROLS RETAINED : CONDITIONS THAT WOULD REOPEN : 1. 2. ACCEPTED BY : (name and role of the risk owner) DATE / TIME :
T7. Pre-restoration sign-off
INCIDENT ID : SYSTEM : CHECK RESULT BY DATE 1 Root cause remediated pass/fail 2 Patching current pass/fail 3 Persistence removed pass/fail 4 Backup predates compromise pass/fail/na 5 Rebuild from trusted media pass/fail/na 6 EDR, firewall, logging live pass/fail 7 Indicator scan (run last) pass/fail EXCEPTIONS ACCEPTED : VERIFIED BY / AT :
T8. System owner acceptance
INCIDENT ID : SYSTEM : OWNER : TESTS PERFORMED : PERFORMED BY : ISSUES FOUND : LIMITATIONS ACCEPTED BY OWNER : ENHANCED MONITORING CONFIRMED : yes | no DETECTION RULES ENABLED : yes | no OWNER SIGN-OFF : (name, role) DATE / TIME :
T9. After-action review agenda, 90 minutes
INCIDENT : DATE :
ATTENDEES : (every team that took part)
0:00 Ground rules. Blameless. Controls, procedures, resources.
Individual performance is handled elsewhere.
0:05 Timeline walkthrough (prepared in advance)
0:30 What worked, and why
0:45 What slowed us down
1:05 Root cause, and the organizational conditions behind it
1:20 Candidate improvements, ranked by risk reduction
1:30 Owners and dates assigned
DECISIONS :
IMPROVEMENTS + OWNERS + DATES :
1.
2.
3.
T10. Executive debrief, one page
INCIDENT : DATE : CLASSIFICATION : RISK LEVEL / SEV : WHAT HAPPENED : (three sentences, no jargon) IMPACT systems : accounts : records / data : downtime : cost to date : DURATIONS (from the KEY TIMES in T1) dwell time : (compromise start to detected) to contain : (detected to contained) to recover : (detected to recovered) HOW IT ENDED : ROOT CAUSE : WHAT WE ARE CHANGING (owner and date on each) 1. 2. 3. WHAT WE NEED : (funding, staff, policy; ask now)
T11. Stakeholder status update
INCIDENT : UPDATE NO. : AUDIENCE : executives | staff | customers | partners SENT (date, time, zone) : APPROVED BY : (Public Information Officer; counsel if external) WHAT IS AFFECTED : (systems, data, locations, people) HOW BAD IT IS : (impact now, and whether it is growing) WHAT TO DO NOW : (workarounds, resets, channels to avoid) WHAT WE ARE DOING : (one or two sentences, no technical detail) WHEN IT WILL BE FIXED : (estimate, or "not yet known") NEXT UPDATE (date, time, zone) : QUESTIONS TO :
T12. Internal notice to staff
SUBJECT: Security incident: what we need from you
We are responding to a security incident affecting ______________.
The response team is working on it now.
What we need from you:
1. Do not discuss the incident outside the company, including on
social media, with customers or with reporters.
2. Send any outside question about it to ______________.
3. Report anything unusual to ______________ by phone, using
______________, until we tell you email is safe.
4. Do not delete email, files or messages related to ______________.
5. Do not reply to anyone claiming to be the attacker.
Report it by phone to ______________ and leave the message
in place. Do not photograph, share or post ransom notes.
What to expect: ______________ (for example, password resets or
systems offline).
The next update will come at ______________ from ______________.
T13. Law enforcement and insurer contact
DECIDED BY / AT : (counsel and Incident Commander) INSURER carrier / policy no. / claim no. : notice deadline in policy : notified (date, time, by whom) : panel vendors required? : yes | no approved vendors : pre-approval needed for : forensics | counsel | negotiator | payment carrier contact : LAW ENFORCEMENT agency / office : (FBI field office, IC3, national CERT, other) case or complaint no. : contacted (date, time, by whom) : what was shared : (counsel approved: yes | no) requests or limits from agency : (for example, delay public disclosure) agency contact : NEXT CONTACT DUE :
T14. Improvement register
INCIDENT ID :
REGISTER OWNER : (one name; Incident Commander until handed
to the program owner)
ISSUED : (date, after the after-action review)
REVIEWS (days after issue; date, reviewer, rows open)
30 days :
60 days :
90 days :
FINDINGS (one block per finding; copy as needed)
ID : (incident ID plus -01, -02, and so on)
finding : (what failed or slowed the response)
source : debrief | tabletop | audit
control / change : (the fix, stated so someone can check it)
owner : (one name)
due date :
risk reduced : (which risk, and by how much, as ranked in T9)
status : open | in progress | done | verified |
risk accepted (attach T6)
verified by / at : (someone other than the owner)
T15. Incident report
INCIDENT ID : VERSION / DATE :
TITLE :
CLASSIFICATION : RISK LEVEL / SEV :
PREPARED BY : (Planning)
REVIEWED BY : (Incident Commander; counsel before release)
DISTRIBUTION :
1. SUMMARY (five sentences or fewer, no jargon)
2. TIMELINE (from the attack timeline; date, time, zone)
compromise start, detected, verified, contained, eradicated, recovered,
closed, and each event between them that changed the response
3. SCOPE AND IMPACT
systems :
accounts :
records / data : (count, types, regulatory categories)
business impact : (disruption duration, revenue effect)
visibility gaps : (what could not be seen, and what that means)
4. ROOT CAUSE AND CONTRIBUTING CAUSES
root cause :
contributing : (conditions that let it happen or spread)
1.
2.
5. ACTIONS TAKEN BY PHASE (cite each record by number)
verify / triage : (T1, T2)
scope : (T4 for each iteration)
contain : (T3 for each decision)
eradicate :
recover : (T7, T8)
6. NOTIFICATIONS MADE (one line each: who, when, under which
obligation, by whom; from T13, T16, T17)
1.
2.
3.
7. METRICS (from T1 KEY TIMES and T10 DURATIONS)
dwell time : (compromise start to detected)
to contain : (detected to contained)
to eradicate : (contained to eradicated)
to recover : (detected to recovered)
loop iterations :
effort and cost : (hours, outside services, any ransom paid)
8. IMPROVEMENTS (T14 IDs, with owner and due date)
1.
2.
3.
APPENDICES
A. Evidence register
B. Containment decision records (T3)
C. Technical closure (T5)
D. Residual risk acceptance (T6)
T16. Notice to affected individuals or customers
NOTICE OF DATA BREACH
DATE OF NOTICE :
FROM : (organization name and address)
TO : (recipient name and address)
METHOD : mail | email | other method counsel approves
JURISDICTION : (the law this version is written for)
APPROVED BY : (counsel; name, date)
WHAT HAPPENED
On ______________ we learned that ______________.
It happened on ______________ (date, estimated date, or date range).
A law enforcement investigation delayed this notice: yes | no
WHAT INFORMATION WAS INVOLVED
______________ (each type of personal information, for example name,
Social Security number, account number, medical information)
WHAT THIS MEANS FOR YOU
______________ (the likely consequences of the breach for you)
WHAT WE ARE DOING
______________ (steps taken to stop it, investigate it and protect
you, and who else has been notified)
WHAT YOU CAN DO
1. ______________ (for example, change your password for ______)
2. Review your account statements and credit reports for activity
you do not recognize.
3. Place a fraud alert or a security freeze on your credit file.
For a fraud alert, contact one of the three nationwide credit
bureaus, and it tells the other two. For a freeze, contact all
three. A freeze is free.
4. ______________
OFFER (where the law requires one, or you offer it)
service : credit monitoring | identity protection
provider :
length : (months, at no cost to you)
enroll by :
enrollment code :
how to enroll :
FOR MORE INFORMATION
contact : (name or team; the data protection officer
where one is appointed)
telephone : (toll-free where possible, with hours)
email / web :
mail :
credit bureaus : (toll-free numbers and addresses, where
the law requires them)
agencies : (state attorney general and Federal Trade
Commission contact details, where the law
requires them)
T17. Regulator notification worksheet
INCIDENT ID :
REGIME : (law, rule or contract, and the regulator;
one worksheet per regime)
TRIGGER : (the event the rule names)
CLOCK STARTED : (date, time, zone)
DECIDED BY / AT : (counsel, and the facts that started the clock)
DEADLINE : (date, time, zone)
CONTENT SUBMITTED : (version; attach a copy)
APPROVED BY : (counsel)
SUBMITTED BY / AT :
METHOD : portal | email | letter | phone
REFERENCE NO. :
CONFIRMATION : (received yes | no; date, time; attach it)
FOLLOW-UP REPORTS DUE (for example, an intermediate or final report)
1. due : submitted :
2. due : submitted :
REGULATOR CONTACT :
T18. Interim statement and media inquiry log
INTERIM STATEMENT
VERSION / TIME : (date, time, zone)
APPROVED BY : (Public Information Officer, with counsel
sign-off)
We are aware of ______________ (what users see, for example "customers
cannot sign in to ______________"), which began at ______________.
We are working to ______________ (restore service, or investigate).
What you should do now: ______________ (for example, use ______________
until service returns).
We will post the next update by ______________ (time and zone) on
______________ (status page or channel).
RULES
1. State a cause only once it is confirmed.
2. Say data is safe only after someone has checked the stored data.
3. Take every fact from the current status summary.
MEDIA INQUIRY LOG (one block per inquiry)
time : (date, time, zone)
outlet :
reporter :
contact : (phone, email)
question :
response given : (statement version, or what was said)
by whom : (Public Information Officer)
follow-up : (what was promised, and by when)
T19. Vendor evidence and preservation request
TO : (vendor or cloud provider; the security or
legal contact named in the contract)
FROM : (name, role, organization)
DATE :
INCIDENT REFERENCE :
LEGAL BASIS : (contract clause or data processing
agreement section; counsel supplies it)
COUNSEL REVIEW : (name, date; before sending)
SUBJECT: Request to preserve and provide records, reference ______________
We are investigating a security incident that may involve our use of
______________. Please preserve the records listed below for the
systems, accounts and time window named here, and send us copies.
Tell us also whether you have seen related activity on your side.
SYSTEMS / ACCOUNTS : (tenant, account or subscription IDs,
user names, products or services)
TIME WINDOW : (start and end; date, time, zone)
RECORDS REQUESTED (mark each yes | no)
1. Authentication logs: sign-ins, token grants, multifactor events
2. API and administrative audit logs
3. Support access records: your staff's access to our data or
tenant, with the reason and the approver
4. Deployment and change records: releases, configuration changes
5. Other: ______________
PRESERVATION
Please suspend deletion and routine purging of these records and
keep them until we release this request in writing. Tell us if any
record has already aged out, and the retention period that applied.
FORMAT : (native export, timestamps in UTC, and a
hash of each file where possible)
RESPOND BY : (date; confirm preservation and give a
delivery date for the records)
CONTACT : (name, phone, and an email address outside
the affected domain)
T14 to T19 are additions to the book. Sources for T16, checked September 2026: GDPR Article 34 and the Article 33(3) points it names; California Civil Code section 1798.82; New York General Business Law section 899-aa; Massachusetts General Laws chapter 93H, section 3; and the FTC's guidance on credit freezes and fraud alerts. T18 follows the communications standards in Incident Command.
Which document is the record
PIVTR-D and Incident Command each have their own paperwork, and some of it covers the same ground. Use this table to decide which document is the record, so nothing is written twice or kept in two places that disagree.
| PIVTR-D template | ICS form | Which is the record |
|---|---|---|
| T1 Incident record | ICS 201, ICS 214 | T1 is the incident record from verification to closure. The ICS 201 is a briefing taken from it, and each ICS 214 activity log feeds its timeline. |
| T2 Triage brief | ICS 209 | T2 is the first brief to decision makers. Once Planning is staffed, the ICS 209 carries every later update. |
| T3 Containment decision record | ICS 204 | T3 records the decision and who authorized it. The ICS 204 assigns the work that carries it out. |
| T4 Loop iteration log | ICS 209 | T4 is the technical record of each pass through the loop. The ICS 209 summarizes it for executives each operational period. |
| T5 to T8, closure, risk acceptance and sign-offs | None | The PIVTR-D templates are the record. Attach each to T1. |
| T9 After-action review agenda | AAR/IP | The AAR/IP is the record. T9 is the agenda for the meeting that produces it. |
| T10 Executive debrief | ICS 209, final | T10 is the closing summary for executives, and the final ICS 209 is the last status report. |
| T11 Stakeholder status update, T12 Internal notice | ICS 209 | The ICS 209 is the record of status. Each T11 and T12 is drawn from the current ICS 209 and logged by the Public Information Officer. |
| T13 Law enforcement and insurer contact | ICS 213 | T13 is the record. Requests from the agency or the carrier that must survive the incident also go on an ICS 213. |
| T14 Improvement register | AAR/IP, improvement plan | T14 is the record of each improvement from issue to verification. The improvement plan in the AAR/IP lists the same actions by T14 ID. |
| T15 Incident report | AAR/IP, ICS 209, final | T15 is the record of what happened and what was done. The AAR/IP is the record of the review, and the final ICS 209 is the last status report. All three use the same timeline. |
| T16 Notice to affected individuals | None | T16 is the record, one version per jurisdiction. The Public Information Officer drafts it and the Legal advisor approves it. The Legal advisor owns the notification deadlines list. |
| T17 Regulator notification worksheet | Decision register | T17 is the record for each regime. The decision that a clock started, and who made it, also goes in the decision register. |
| T18 Interim statement and media inquiry log | ICS 214 of the Public Information Officer | T18 is the record of public statements and media inquiries, kept by the Public Information Officer. Each statement takes its facts from the current ICS 209, and the officer's ICS 214 logs each release. |
| T19 Vendor evidence and preservation request | ICS 213 | T19 is the record of the request. A request the vendor must act on after the incident also goes on an ICS 213, and the records the vendor sends go in the evidence register. |
| None | ICS 202, 203, 205, 221 | The ICS forms are the record. File each with the Incident Action Plan for its period, or with T1. |