Incident¶
Quick Summary
Tracks security incidents and service outages from detection through resolution. Incidents carry severity levels, involve the Incident Response Team, and produce the audit trail required by FedRAMP, NIST SP 800-171, and DFARS.
An incident ticket is created when a security event, service outage, or other disruption requires coordinated investigation and response. Incidents may be raised manually by a team member or escalated in place from an alert after triage confirms a genuine event.
The ticket captures detection details, affected systems, severity, and whether sensitive data (such as CUI) is potentially involved. All actions taken during containment, eradication, and recovery are documented directly on the ticket through notes and attachments, creating the authoritative record for post-incident review and regulatory reporting.
Workflow¶
An incident moves through these steps:
| Step | What happens |
|---|---|
| New | The incident is raised and waits for evaluation |
| Evaluated | The incident is not reportable. Complete and approve the After Action Report from this step |
| Initial Report Due | The incident is reportable and the Initial Incident Report is owed |
| Ongoing Report Due | The Initial Incident Report is sent. Ongoing reports are sent from this step until recovery is complete |
| Final Report Due | Recovery Complete moves the ticket here. The Final Incident Report is owed |
| AAR Due | The Final Incident Report is sent. The After Action Report is owed |
| AAR Pending | The After Action Report is waiting for approval |
| AAR Approved | The After Action Report is approved and the incident can be resolved |
| Resolved | The incident is closed |
The Evaluate action stays available on the reporting steps and on AAR Due, so you can re-evaluate as facts develop.
Evaluation and Reporting¶
Every incident is evaluated to determine whether it affects, or is likely to affect, the confidentiality or integrity of federal customer data -- such incidents are FedRAMP Reportable Incidents. The evaluating responder records the reportability determination and assigns a Potential Agency Impact N-rating (PAIN); a reportable incident whose PAIN rating is not promptly estimated defaults to PAIN 5. Each evaluation adds a row to the incident's event timeline. The reportability reason must open with "Reportability (IEC-CSO-EFR):".
The PAIN rating sets the reporting clocks: affected parties receive an Initial Incident Report, Ongoing Incident Reports, and a Final Incident Report on PAIN-keyed timeframes. OLAs track the initial and final report deadlines only. The notice checks and a daily sweep score the reports; see FedRAMP Notices.
Sending the reports¶
Each report has two actions:
- Initial Report, Ongoing Report, Final Report record the report content on the ticket. They do not send anything and do not move the ticket.
- Send FedRAMP Initial Incident Report, Send FedRAMP Ongoing Incident Report, and Send FedRAMP Final Incident Report open a templated email in preview. Enter Reported To and the Sent At time, then press Send in the preview. Sending the initial report moves the ticket to Ongoing Report Due, and sending the final report moves it to AAR Due.
No AI tool sends a notice; the AI record tools only fill fields. Notice emails print dates in UTC and label them "(UTC)".
After Action Report¶
Every incident ends in an After Action Report -- root cause, lessons learned, and corrective actions authored on the incident record and approved by the After Action Report Approvers CAB. The report comes before the incident resolves:
- Click Complete AAR to record the report.
- Click AAR Approval to request approval. The ticket moves to AAR Pending.
- If the approvers reject it, the ticket returns to AAR Due. If they approve it, the ticket moves to AAR Approved, and you can resolve it.
Incidents from vulnerabilities¶
An incident can open automatically from a vulnerability Issue. The incident opens once the Issue's evaluation is recorded, or once the evaluation window passes (Class A 14 days, B 7, C 5, D 2). Each Issue opens at most one incident. If the Issue later drops below the threshold, the automatic de-escalation closes an incident still in New and records Externally Reportable as No.
Exercises¶
Tick Is Exercise on a practice incident. It stays out of the Trust Center and POA&M reports but is still scored. See FedRAMP Notices for how exercise rows and emails are marked.
See the Incident Response policy for the reporting timeframes, PAIN defaults, and the FedRAMP Security Inbox obligations.
Compliance Context¶
Incident tickets support overlapping requirements across FedRAMP and CMMC:
| Control Area | Requirement |
|---|---|
| Incident Handling (FedRAMP IR-4) | Implement an incident handling capability that includes preparation, detection, analysis, containment, eradication, and recovery |
| Incident Reporting (FedRAMP IR-6) | Report incidents to appropriate authorities within required timeframes |
| Incident Monitoring (FedRAMP IR-5) | Track and document incidents on an ongoing basis |
| Incident Response (CMMC IR.L2-3.6.1) | Establish operational incident-handling capabilities |
| Incident Reporting (CMMC IR.L2-3.6.2) | Track, document, and report incidents to designated officials |
| CUI Incident Reporting (DFARS 252.204-7012) | Report cyber incidents involving CUI to DoD within 72 hours |
See the Incident Response playbook for detailed procedures.