Incident Response¶
This document establishes the organization's policy for detecting, evaluating, reporting, and closing incidents affecting the system, and the procedures by which GRC-ITSM executes that policy. It covers alert ingest and categorization, escalation of an Alert into an Incident, the human reportability and impact evaluation, the FedRAMP reporting chain from initial report through final report, the After Action Report and its approval, and the FedRAMP Security Inbox. It implements the FedRAMP Incident Evaluation and Communication (IEC) and Addressing FedRAMP Communication (AFC) rule families from the FedRAMP Consolidated Rules for 2026, and the Incident Response Key Security Indicators (KSI-INR).
Quick Summary
Every alert is ingested as a categorized Alert ticket and escalated in place into an Incident when it warrants one. A human evaluation sets the FedRAMP reportability determination and the Potential Agency Impact N-rating (PAIN), and that rating sets the reporting clocks. Each FedRAMP report then goes out through a Send action that opens the report's template in an email preview; pressing Send sends the notice and moves the Incident to its next step, from initial report through ongoing reports and recovery to final report. The After Action Report is completed and approved by CAB before the incident resolves. Notice checks and a daily sweep score every report, and the FedRAMP Security Inbox gives FedRAMP a monitored path into the same process.
Related documentation
- Incident Response playbook -- how to execute this procedure in the product, click by click
- Incident ticket type -- the evaluation fields, workflow stages, and FedRAMP reporting actions on the record
- Alert ticket type -- the alert taxonomy and the escalation path into an Incident
- Vulnerability Detection & Response -- the vulnerability boundaries that escalate into this process
- FedRAMP Notices -- the window, check, and daily sweep behind each incident notice
Download the KB article (Markdown)
Official FedRAMP references
Framework applicability¶
| Framework | What this document satisfies |
|---|---|
| FedRAMP 20x (Class C) | IEC provider rules (IEC-CSO); AFC provider rules (INB, NOC, RCV, TFG, CRA, EMR, ACK, IMA); KSI-INR-AAR, KSI-INR-RIR, KSI-INR-RPI; the vulnerability incident boundaries (VER-TFR-IRI, VER-TFR-NRI) |
| FedRAMP Rev5 (Class C) | The same IEC and AFC provider rules; underlying NIST IR-4, IR-5, IR-6 |
| CMMC Level 2 | IR.L2-3.6.1, IR.L2-3.6.2, IR.L2-3.6.3 (traceability; CMMC values in the ODV table) |
FedRAMP 20x classes differ in reporting timeframes and validation depth, not in the procedure itself; the Organization-Defined Values table carries the Class C values.
Policy¶
- P-1. Every alert is tracked and categorized. Alerts from security and operational tooling are ingested as Alert tickets and assigned a category from the shared Alerts and Incidents taxonomy. The category differentiates the alert type for triage and reporting and drives automatic framework attribution.
- P-2. Reportability is a human determination, made promptly. 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 (IEC-CSO-EFR, MUST). The determination is a required workflow step, recorded with its supporting fields on the ticket.
- P-3. Impact rating sets the clock. Reportable incidents are assigned a Potential Agency Impact N-rating (PAIN) at evaluation (IEC-CSO-EFI, SHOULD). A FedRAMP Reportable Incident whose PAIN rating is not promptly estimated is handled as PAIN 5 (IEC-CSO-DPR, MUST); the responder performing the evaluation applies that default.
- P-4. Reporting is persistent until the incident is resolved. Affected parties receive an Initial Incident Report, Ongoing Incident Reports as new information becomes available, and a Final Incident Report once recovery is complete (IEC-CSO-IIR, IEC-CSO-OIR, IEC-CSO-FIR, each MUST at Class C), on the PAIN-keyed timeframes in the ODV table.
- P-5. Reporting is automated wherever it can be. Each report is drafted from the incident record in a FedRAMP template, and each send is recorded on the ticket and scored automatically, which minimizes human intervention in producing and tracking reports (IEC-CSO-AIR, SHOULD). A person reviews every notice and presses Send; no AI or API tool sends a notice.
- P-6. Dangerous vulnerabilities are incidents. An internet-reachable, likely exploitable vulnerability rated above PAIN 3 is treated as a FedRAMP Reportable Incident until it is at least partially mitigated to PAIN 3 or below (VER-TFR-IRI, SHOULD at Class C; the organization implements it as binding internal policy). A likely exploitable vulnerability that is not internet-reachable and is rated PAIN 5 is treated the same way until it is at least partially mitigated to PAIN 4 or below (VER-TFR-NRI, MAY at Class C; the organization implements it as binding internal policy).
- P-7. FedRAMP can always reach the organization. The organization maintains a FedRAMP Security Inbox, receives FedRAMP mail without disruption, trusts the @fedramp.gov and @gsa.gov domains by default, routes Emergency designated messages to a senior security official, completes required actions within the timeframes in Emergency and Emergency Test designated messages, and immediately notifies FedRAMP of any inbox address change (AFC-CSO-INB, AFC-CSO-RCV, AFC-CSO-TFG, AFC-CSO-EMR, AFC-CSO-CRA, AFC-CSO-NOC, each MUST). Receipt is acknowledged automatically (AFC-CSO-ACK, SHOULD, implemented).
- P-8. Every incident ends in an approved After Action Report. Root cause, lessons learned, and corrective actions are authored on the incident record and approved by the After Action Report Approvers CAB before the incident resolves (KSI-INR-AAR).
- P-9. The procedure reviews itself. The effectiveness of this document is reviewed on the cadence in the ODV table (KSI-INR-RIR), and past incidents are reviewed for patterns not previously apparent (KSI-INR-RPI).
Organization-defined values¶
| Value | Setting | Default (Class C) | Force |
|---|---|---|---|
| Initial Incident Report, PAIN 5 / 4 / 3 | [timeframe] | 1 hour (IEC-CSO-IIR) | MUST |
| Initial Incident Report, PAIN 2 | [timeframe] | 24 hours (IEC-CSO-IIR) | MUST |
| Initial Incident Report, PAIN 1 | [timeframe] | 1 business day (IEC-CSO-IIR) | MUST |
| Ongoing Incident Report cadence, PAIN 5 / 4 / 3 | [cadence] | Every 6 hours (IEC-CSO-OIR) | MUST |
| Ongoing Incident Report cadence, PAIN 2 | [cadence] | Every 24 hours (IEC-CSO-OIR) | MUST |
| Ongoing Incident Report cadence, PAIN 1 | [cadence] | Every 1 business day (IEC-CSO-OIR) | MUST |
| Final Incident Report after recovery, PAIN 5 / 4 / 3 | [timeframe] | Within 6 hours (IEC-CSO-FIR) | MUST |
| Final Incident Report after recovery, PAIN 2 / 1 | [timeframe] | Within 1 business day (IEC-CSO-FIR) | MUST |
| Default rating when PAIN is not promptly estimated | PAIN 5 | PAIN 5, all classes (IEC-CSO-DPR) | MUST |
| Reportability evaluation window ("promptly") | [window] | 1 day from Detected At, the house threshold the notice checks score; the rules set no number (IEC-CSO-EFR) | MUST |
| PAIN estimation window ("promptly") | [window] | The rules set no numeric window (IEC-CSO-EFI) | SHOULD |
| Incident boundary, internet-reachable likely exploitable vulnerabilities | Above PAIN 3, until partially mitigated to PAIN 3 or below | Same (VER-TFR-IRI) | SHOULD |
| Incident boundary, non-internet-reachable likely exploitable vulnerabilities | PAIN 5, until partially mitigated to PAIN 4 or below | Same (VER-TFR-NRI) | MAY |
| FedRAMP Security Inbox human acknowledgment | [timeframe] | 1 hour, by internal inbox SLA (supports AFC-CSO-RCV) | N/A |
| FedRAMP Security Inbox notification breadth | [number of people] | At least 3 holders of the Notifications - FedRAMP Security Inbox role |
N/A |
| Emergency message routing target | [senior security official] | Senior security official designated by the System Owner (AFC-CSO-EMR) | MUST |
| After Action Report approvers | [CAB membership] | Members hold the Approver - After Action Reports role |
N/A |
| Incident response procedure effectiveness review | [cadence] | At least annually and after each approved After Action Report (KSI-INR-RIR) | N/A |
| Past-incident pattern review | [cadence] | At least annually (KSI-INR-RPI) | N/A |
| CMMC incident reporting timeframes and external authorities | [timeframe and authorities] | Per contract (IR.L2-3.6.2) | N/A |
Roles and responsibilities¶
- Anyone may report a suspected incident.
- Assigned agent (Alerts and Incidents). Each Alert and Incident is assigned a tracking owner automatically via the
Agent Assignment - Alerts/Incidentsrole. Assignment confers tracking ownership, not approval authority. - Evaluating responder. Completes the Evaluate action: the reportability determination, the PAIN rating and its rationale, the incident timestamps, and the detection source.
- Reporting responder. Records each report's content with the fill-in actions, takes the matching Send action, confirms the recipients and content in the email preview, and presses Send.
- After Action Report Approvers CAB. The
Approver - After Action Reportsrole grants membership to the After Action Report Approvers CAB, who approve After Action Reports. Approval is always by the CAB, never by the assigned agent. - FedRAMP Security Inbox notification group. The
Notifications - FedRAMP Security Inboxrole defines who is notified of inbound FedRAMP mail; at least three people hold it. - ISSO and System Owner. Accountability and escalation. The ISSO reviews this document on the cadence in the ODV table and the System Owner approves it. The System Owner designates the senior security official who receives Emergency designated messages.
Alert ingest and categorization¶
GRC-ITSM ingests alerts from endpoint detection and response, SIEM, observability tooling, and similar sources into Alert tickets. Every Alert carries a category from the shared Alerts and Incidents taxonomy:
| Group | Categories |
|---|---|
| Security | Unauthorized Access, Audit Log Failure, Malware, Phishing, Suspicious Activity, Integrity Violation, Data Exfiltration, Denial of Service, Unauthorized Change, Unauthorized Software, Policy Violation |
| Availability | System Outage, Backup Failure, Resource Exhaustion, Automation Error, Security Functionality, System Error, KSI |
| Performance | High Resource Usage, Disk Full, Network Latency |
The category differentiates alert types for triage and reporting, and drives the automatic attribution of controls, requirements, KSIs, and FedRAMP rules to the ticket per (ticket type x category), scoped to the system's authorized baselines.
Escalation to Incident¶
A responder escalates an Alert into an Incident with an action button. The escalation converts the Alert into an Incident in place: all Alert field detail carries forward, and the incident evaluation and reporting fields and processes are added. Because Alerts and Incidents share one category taxonomy, the category set at Alert creation survives the conversion.
Two further entry paths open Incidents directly:
- Vulnerability escalation (automated). A scheduled escalation sweep opens an Incident, in New, from an open vulnerability Issue at either boundary in P-6: internet-reachable, likely exploitable, above PAIN 3 (VER-TFR-IRI), or non-internet-reachable, likely exploitable, at PAIN 5 (VER-TFR-NRI). It opens the Incident once the Issue's evaluation is recorded, or once the evaluation window has passed without one (VER-TFR-EVU: Class A 14 days, Class B 7, Class C 5, Class D 2), and it opens at most one Incident per Issue. The sweep reads the current rating, so an approved Vulnerability Deviation that adjusts the rating adjusts the escalation. When the Issue drops below both boundaries while its Incident is still in New, the sweep closes that Incident and records an evaluation with Externally Reportable = No. Escalated tickets name their source in the title and preserve the link to the source Issue. Vulnerability handling itself follows the Vulnerability Detection & Response Policy and Procedures.
- FedRAMP Security Inbox. Inbound FedRAMP mail opens an Incident directly; see the FedRAMP Security Inbox section.
Evaluation¶
Every Incident starts in New. The first step is a human Evaluate action capturing these required structured fields:
| Field | Purpose |
|---|---|
| Externally Reportable | The FedRAMP reportability determination (IEC-CSO-EFR) |
| Priority | Handling priority for the incident record |
| Potential Adverse Impact | The PAIN rating (IEC-CSO-EFI; PAIN 5 by default per IEC-CSO-DPR) |
| PAIN Evaluation Notes | The rationale supporting the rating |
| Incident Started At, Detected At, Evaluation Completed At | The FedRAMP incident timeline |
| Detection Source | How the incident was detected |
The responder opens the reason in PAIN Evaluation Notes with Reportability (IEC-CSO-EFR):. The rules require the evaluation "promptly" and set no number, so the platform scores it against a house threshold of 1 day from Detected At. Each evaluation, including a re-evaluation, writes a row to the Incident Events timeline on the ticket.
Evaluate routes the Incident on Externally Reportable. A reportable incident moves to Initial Report Due. A non-reportable incident moves to Evaluated, where the responder completes the After Action Report and resolves the ticket. Evaluate stays available on Initial Report Due, Ongoing Report Due, Final Report Due and AAR Due, so the responder can revise the determination and the PAIN rating as facts change.
For reportable incidents the PAIN rating sets the reporting clocks. OLAs on the Incident ticket track the initial and final report deadlines, keyed to the PAIN rating, and notify the incident points of contact. Ongoing reports carry no OLA; the notice checks score them (see Automated validation evidence).
The FedRAMP reporting chain¶
Each report has two parts on the Incident ticket. A fill-in action (Initial Report, Ongoing Report, Final Report) records the report content and does not move the ticket. A Send action (Send FedRAMP Initial Incident Report, Send FedRAMP Ongoing Incident Report, Send FedRAMP Final Incident Report) opens the FedRAMP template for that report in an email preview, filled from the ticket. Nothing goes out until the sender presses Send in the preview, and the sender confirms the recipients there. Each Send action requires Reported To and its own sent-at field (Initial Report Sent At, Ongoing Report Last Sent At, Final Report Sent At), writes a Report Sent row to the Incident Events timeline, and is the only action that moves the ticket to its next step. No AI or API tool sends a notice; the record tools fill report fields only. Evaluation results carry forward read-only, and the workflow enforces the order.
| Step | Actions that move the Incident |
|---|---|
| New | Evaluate: to Initial Report Due (reportable) or Evaluated (not reportable) |
| Evaluated | Complete AAR and AAR Approval, then Resolve |
| Initial Report Due | Send FedRAMP Initial Incident Report: to Ongoing Report Due |
| Ongoing Report Due | Send FedRAMP Ongoing Incident Report (repeatable; the ticket stays on the step). Recovery Complete: to Final Report Due |
| Final Report Due | Send FedRAMP Final Incident Report: to AAR Due |
| AAR Due | Complete AAR, then AAR Approval: to AAR Pending |
| AAR Pending | Approved: to AAR Approved. Rejected: back to AAR Due |
| AAR Approved | Resolve |
- Initial Incident Report (IIR). Record the content, including Functional Impact, Recovery Plan, and Affected Agencies, then send it with Send FedRAMP Initial Incident Report (IEC-CSO-IIR).
- Ongoing Incident Reports (OIR). Repeatable. Record and send an ongoing report as new information becomes available and on the cadence in the ODV table (IEC-CSO-OIR). Send FedRAMP Ongoing Incident Report remains available on Final Report Due.
- Recovery Complete. Records Recovery Completed At against the recovery plan and moves the ticket to Final Report Due.
- Final Incident Report (FIR). Available only after recovery completes. Record the content, including Functional Impact, Root Cause, Response and Recovery Activities, and Affected Agencies, with Reported To, Observed Activity, and Related CVEs carried forward, then send it with Send FedRAMP Final Incident Report, which moves the ticket to AAR Due (IEC-CSO-FIR).
Notice emails print dates in UTC and label them "(UTC)". To mark an exercise, tick Is Exercise on the Incident; the FedRAMP Notices guide covers how exercise notices are addressed and scored, the reporting windows, and the daily sweep.
The full FedRAMP timeline therefore lives on one record: started, detected, evaluation completed, initial report, ongoing reports, recovery complete, final report. Externally reportable incidents surface on dedicated reports carrying that timeline in human-readable and machine-readable form on the FedRAMP Incident Report schema, which is how the organization minimizes human intervention in reporting (IEC-CSO-AIR).
After Action Report and approval¶
The After Action Report comes before the incident resolves. On a reportable incident, the Final Incident Report send moves the ticket to AAR Due, where the Complete AAR action authors the After Action Report on the same ticket: Root Cause, Lessons Learned, and Corrective Actions. A non-reportable incident completes its After Action Report from Evaluated.
The AAR Approval action then runs the After Action Report Approvers approval process and moves the ticket to AAR Pending: the submitter selects one or more CAB members to approve, and the Approver - After Action Reports role grants membership to the After Action Report Approvers CAB, who approve AARs. An approval moves the ticket to AAR Approved, where it is resolved. A rejection returns it to AAR Due for rework and resubmission. The approval writes dated machine validation evidence for KSI-INR-AAR automatically.
FedRAMP Security Inbox¶
A dedicated FedRAMP Client in GRC-ITSM defines the FedRAMP senders as users. The FedRAMP Security user carries fedramp_security@fedramp.gov and fedramp_security@gsa.gov, the two mailboxes FedRAMP uses for Emergency and Emergency Test designated messages (AFC-FRP-UFS); broader trust applies at the @fedramp.gov and @gsa.gov domain level (AFC-CSO-TFG).
Inbound mail from these senders:
- opens an Incident ticket carrying the message criticality designation in the title (for example
[EMERGENCY]); - sends an automatic acknowledgment on receipt (AFC-CSO-ACK);
- notifies every holder of the
Notifications - FedRAMP Security Inboxrole, under an inbox SLA requiring human acknowledgment within one hour (an internal SLA that supports AFC-CSO-RCV) with at least three people notified.
The organization routes Emergency designated messages to the senior security official designated by the System Owner (AFC-CSO-EMR), completes the required actions in Emergency and Emergency Test designated messages within the timeframe included in the message (AFC-CSO-CRA), and immediately notifies FedRAMP of any change to the FedRAMP Security Inbox address (AFC-CSO-NOC). Actions in Important designated messages are completed within the specified timeframe (AFC-CSO-IMA, SHOULD).
Outbound incident reports go through the Send actions in the reporting chain; the sender confirms the recipients in the email preview before sending.
Automated validation evidence¶
Operating this process produces machine validation evidence automatically:
- After Action Reports. AAR approval writes dated validation runs, evidencing that after action reports are generated and lessons learned are incorporated (KSI-INR-AAR).
- Notice checks. When Evaluate or a Send action is taken, notice checks score the reportability evaluation against the 1-day threshold (IEC-CSO-EFR), the PAIN estimate before the initial report (IEC-CSO-EFI), each initial, ongoing, and final report against its window (IEC-CSO-IIR, IEC-CSO-OIR, IEC-CSO-FIR), and the FedRAMP ID at each send (CDS-CSO-FID).
- Daily sweep. A daily sweep writes a Fail for a reportability evaluation, initial report, ongoing report, or final report still owed past its window. A later evaluation or send replaces that row.
- OLAs. OLAs track the initial and final report deadlines only. The notice checks and the daily sweep, not the OLAs, are the scoring record.
- Machine-readable reports. Externally reportable incidents publish on the FedRAMP Incident Report schema for automated retrieval.
The FedRAMP Notices guide covers the windows, the checks, and the sweep.
Authority, review, and revision¶
Issued under the authority of the System Owner and binding on all personnel with access to the system. Exceptions require written System Owner approval.
The ISSO reviews this document for effectiveness at least annually, after each approved After Action Report, and when frameworks, the system, or lessons learned warrant; the System Owner gives final approval. This review evidences persistent review of documented incident response procedure effectiveness (KSI-INR-RIR). The two halves land differently: the after-each-AAR half is discharged by the AAR approval itself, which writes its own dated validation evidence, and the annual half is tracked by the annual plan and policy review task under the Annual cadence parent.
Past incidents are reviewed for patterns or vulnerabilities not previously apparent (KSI-INR-RPI). This is a distinct obligation from the plan review, the plan test, and the response training, each of which carries its own annual task: it examines the incident population for what no single incident's After Action Report could show. It runs as an annual recurring task on the Annual cadence parent under the task program in the Continuous Monitoring and Reporting Policy and Procedures.
FedRAMP coverage¶
IEC provider rules: Evaluate FedRAMP Reportability (MUST), Default PAIN Rating (MUST), Estimate Federal Impact (SHOULD), Initial Incident Report (MUST at Class C), Ongoing Incident Reports (MUST at Class C), Final Incident Report (MUST at Class C), Automated Incident Reporting (SHOULD) (IEC-CSO). AFC provider rules: Maintain a FedRAMP Security Inbox (MUST), Notification of Changes (MUST), Receive Email Without Disruption (MUST), Trust @fedramp.gov and @gsa.gov (MUST), Complete Required Actions (MUST), Emergency Message Routing (MUST), Acknowledge Receipt (SHOULD), Important Message Actions (SHOULD) (AFC-CSO); the FedRAMP-side sender rule the inbox relies on is AFC-FRP-UFS. VER incident boundaries: Internet-Reachable Incidents (VER-TFR-IRI, SHOULD at Class C), Non-Internet-Reachable Incidents (VER-TFR-NRI, MAY at Class C). KSI-INR: Generating After Action Reports, Reviewing Incident Response Procedures, Reviewing Past Incidents. Underlying NIST: IR-4, IR-5, IR-6. CMMC: IR.L2-3.6.1, IR.L2-3.6.2, IR.L2-3.6.3.