Skip to content

Incident Report Form

Incident Report Form template: The record of one report of a suspected incident or breach, from the first report through triage, notifications and closure, with a register of every report, as SP 800-53 IR-6 and IR-5 require.

TypeProgram stageStatusTemplate versionNIST basis
Form or registerCoreDraft1.0.0SP 800-53 release 5.2.0

The record of one report of a suspected incident or breach, from the first report through triage, notifications and closure, with a register of every report, as SP 800-53 IR-6 and IR-5 require.

ControlTitle
IR-6Incident Reporting
IR-6(1)Automated Reporting
IR-5Incident Monitoring
IR-7Incident Response Assistance
IR-8(1)Breaches
VariantReady to adoptAnnotated
All baselinesWord · MarkdownWord · Markdown

The register as a spreadsheet: CSV, with one column per field.

Report IDDate and time receivedReceived throughIncident record IDStatus
Fill in: unique report IDFill in: date and timeFill in: phone, email, portal, alert, or outside partyFill in: incident record ID, or noneFill in: received, triaged, declared, not an incident, or closed
  • Anyone who suspects an incident or a breach completes Parts A to C, or calls the service desk, which completes them during the call. Report within Fill in: time period for personnel to report suspected incidents to the organizational incident response capability Typical: 1 hour of discovery (IR-6a). Do not wait to confirm it, and do not investigate first.
  • Report what you know. A blank answer is better than a guess, and the team will follow up.
  • Describe information that was exposed without copying it into the form: write “a spreadsheet of customer names and account numbers”, not the names and numbers.
  • Submitting the form through Fill in: automated mechanisms used for reporting incidents Typical: the incident report form and case management system, which notify the incident response team automatically alerts the Incident response team (IR-6(1)).
  • The Incident response team completes Parts D to F and enters the report in the register.
FieldEntry
Name of the person reportingFill in: name
Contact phone and emailFill in: phone and email
Organizational unit, or company for an outside reporterFill in: unit or company
Person who discovered it, if differentFill in: name and contact
Best time and way to reach youFill in: time and method
FieldEntry
Date and time it was discoveredFill in: date and time
What you saw or what happenedFill in: description in your own words
How it was noticedFill in: for example a suspicious email, a security alert, a missing device, a customer’s call
Systems, devices or services involvedFill in: names, addresses or asset tags, and any connection to other systems
Where it happenedFill in: office, remote, a supplier, a cloud service
Is it still happening?Fill in: yes, no, or not sure
What you have done so farFill in: for example disconnected the laptop, forwarded the email to the service desk, nothing
QuestionAnswer
What information was, or may have been, lost, exposed, changed or deleted?Fill in: a description, not the information itself
Does it include personal information about people, such as names with identification numbers, financial, health or contact details?Fill in: yes, no, or not sure
If yes: about how many people?Fill in: number or estimate
What medium was it on?Fill in: for example laptop, phone, removable media, paper, a cloud service, email, a conversation
Was it protected, for example encrypted or password protected?Fill in: yes, no, or not sure, and how
Has anyone outside the organization been told, such as law enforcement or the recipient?Fill in: no; or yes, who and when

Completed by the Incident response team.

FieldEntry
Received by, and date and timeFill in: name, date and time
OutcomeFill in: incident declared; not an incident, with the reason; or referred elsewhere, such as a routine service request
Date and time declaredFill in: date and time
Incident typeFill in: from section 6 of the incident handling playbook, for example ransomware, account takeover, lost device
SeverityFill in: from section 4 of the Incident Response Plan
Functional impactFill in: what the organization cannot do, or can do only with difficulty
Information impactFill in: none known, suspected, or the type of information compromised
RecoverabilityFill in: recoverable with existing resources, with added resources, or not recoverable
Personally identifiable information involvedFill in: no; or yes or possibly, and the time the privacy official was told
Major incidentFill in: no; or yes, declared by and time
Incident leadFill in: name

The Incident response team reports incident information to Fill in: authorities to whom incident information is to be reported Typical: senior leadership, legal counsel, and any regulator, customer or partner that law or contract requires be notified (IR-6b). Record every notification, inside and outside the organization.

PartyRequired byDeadlineDecided bySent byDate and time sentReference
Chief Information Security OfficerIncident Response PlanFill in: for example at declaration for High and CriticalFill in: nameFill in: date and time
Senior privacy officialIncident Response Plan breach sectionAt identification, when personally identifiable information is or may be involvedFill in: nameFill in: date and time
Senior leadershipIncident Response PlanFill in: deadlineFill in: nameFill in: nameFill in: date and time
Fill in: regulator, customer, partner, supplier or law enforcementFill in: law, regulation or contractFill in: deadlineFill in: nameFill in: nameFill in: date and timeFill in: their reference
Affected individualsFill in: requirement, or the privacy official’s decisionFill in: deadlineFill in: nameFill in: nameFill in: date rangeFill in: notice version

Federal agencies notify the Cybersecurity and Infrastructure Security Agency (CISA) of incidents under FISMA (44 U.S.C. §§ 3553 and 3554). As of October 2026, the CISA Federal Incident Notification Guidelines (effective April 1, 2017) require a report within one hour of identification by the agency’s top-level incident response team, security operations center or IT department, with seven required elements. Part D’s impact fields follow the guidelines’ functional impact, information impact and recoverability categories, so the report can be filed from this form. CISA asks agencies not to include sensitive personally identifiable information in submissions.

OMB Memorandum M-25-04 (January 15, 2025), the most recent FISMA guidance memorandum as of October 2026, section X, sets the major incident fields below. Events still unresolved after 72 hours of investigation are reported to CISA. A major incident determination is required for a breach affecting the personally identifiable information of 100,000 or more people. A major incident is reported to CISA and the OMB Office of the Federal Chief Information Officer within 1 hour of the determination, to the appropriate congressional committees and the Office of Inspector General within 7 days of the reasonable-basis determination, and, for a breach, in a supplemental report to Congress within 30 days of discovering it. OMB Memorandum M-17-12, section VIII, requires the principal security operations center to track each breach, including the number of individuals, the types of information, whether individuals were notified or offered services, and whether it was reported to CISA or Congress.

CISA elementEntry
Time of identification by the top-level team, which starts the one-hour clockFill in: date and time
Functional impact (CISA category)Fill in: category
Information impact (CISA category, for example privacy data breach)Fill in: one or more categories
Recoverability (CISA category)Fill in: category
When the activity was first detectedFill in: date and time
Number of systems, records and users affectedFill in: numbers or estimates
Network location of the observed activityFill in: location
Point of contactFill in: name and contact
Attack vector, indicators of compromise and mitigation, if knownFill in: details
Reported to CISA by, date and timeFill in: name, date and time
CISA tracking numberFill in: number
Unresolved after 72 hours of investigation; reported to CISAFill in: not applicable; or date and time reported
Major incident determination (M-25-04 section X)Fill in: not major; or major, under criterion A or B, and whether the 100,000-person rule applies
Determination made by, with date and time; who took partFill in: name, date and time; for example the CIO, CISO, system owner and, for a breach, the senior agency official for privacy
Reported to CISA and the OMB Office of the Federal Chief Information OfficerFill in: by whom, date and time, within 1 hour of the determination
Congressional committees and Office of Inspector General notifiedFill in: by whom and date, within 7 days of the reasonable-basis determination
Breach supplemental report to CongressFill in: not applicable; or date sent, within 30 days of discovering the breach
Breach tracked jointly by the principal security operations center and the senior agency official for privacy, for a breach that is a major incident (M-25-04 section X; M-17-12 section VIII)Fill in: tracking reference
FieldEntry
Root causeFill in: summary, or a reference to the incident record
Records or individuals affected, final countFill in: number, or not applicable
Lessons-learned review heldFill in: date, or not required at this severity
After-action report and action listFill in: reference
Closed by, and dateFill in: name and date
Report IDReceived (date and time)Reported byDiscovered (date and time)OutcomeDeclared (date and time)Incident typeSeverityPersonally identifiable information involvedMajor incidentOutside notifications (party and date)Closed
Fill in: IDFill in: date and timeFill in: name or sourceFill in: date and timeFill in: declared, not an incident, or referredFill in: date and timeFill in: typeFill in: severityFill in: no, yes or possiblyFill in: no or yesFill in: parties and dates, or noneFill in: date

Independent guidance, not an official NIST publication. Control text is from NIST SP 800-53 Rev. 5 and SP 800-53A (public domain). Original content is licensed CC BY 4.0; program templates and the downloadable kit are dedicated to the public domain under CC0 1.0.