Incident Response¶
Step-by-step procedures for handling security incidents and service outages within the GRC-ITSM platform.
Overview
GRC-ITSM is the central hub for tracking, documenting, and communicating throughout the incident response lifecycle. Every incident, from initial detection through lessons learned, is managed within the platform to maintain a complete audit trail for compliance with NIST SP 800-171, DFARS, and other applicable frameworks.
Governing policy
This playbook executes the Incident Response Policy and Procedures, which defines the binding policy statements, reporting timeframes, and framework citations behind these steps.
1. Incident Ticket Creation¶
When an incident is detected, whether through an automated alert, a security tool, or a user report, an incident ticket must be created in the GRC-ITSM platform immediately. Incidents live under the Alerts and Incidents category. When the detection arrives as an alert already tracked in the platform, escalate that alert in place to an Incident rather than opening a separate ticket; the existing ticket converts and its history carries forward.
Required Fields¶
The ticket should capture the following at creation:
| Field | Description |
|---|---|
| Date & Time of Detection | When the incident was first identified |
| Detection Source | Alert system, security tool, user report, etc. |
| Affected Systems & Assets | Systems, services, or assets impacted |
| Initial PAIN Rating | Potential Agency Impact N-rating (PAIN) estimate; defaults to PAIN 5 when not promptly estimated |
| Reportability | Whether the incident is evaluated as a FedRAMP Reportable Incident (a human determination, revisited as facts develop). Click Evaluate, record the reportability and PAIN rating, and open the reason with "Reportability (IEC-CSO-EFR):" |
| Sensitive Data Involvement | Whether CUI or other sensitive data is potentially involved |
| IRT Personnel | Incident Response Team members assigned to the ticket |
Automated Ticket Creation
Certain security tools (e.g., Huntress) can integrate directly with the GRC-ITSM platform to create incident tickets and notify IRT members automatically upon alert, eliminating the manual creation step for those detection sources.
Incidents also open automatically from vulnerability Issues, one incident per Issue, once the Issue's evaluation is recorded or its evaluation window passes. Treat these like any other incident and evaluate them promptly.
After evaluation, the ticket moves to Initial Report Due when the incident is reportable, or to Evaluated when it is not. Click Evaluate again whenever the facts change.
2. Documentation Throughout Response¶
The GRC-ITSM platform serves as the authoritative record for all actions taken during an incident. At every phase (containment, eradication, and recovery) personnel document their activities within the incident ticket.
What to Document¶
- Private notes on the ticket for each action taken, including timestamps and rationale for key decisions
- Attachments uploaded directly to the ticket: screenshots, log exports, forensic outputs, and tool reports
This creates a centralized repository for investigation artifacts and evidence, and establishes the audit trail needed for compliance with applicable regulatory requirements (e.g., NIST SP 800-171 and DFARS reporting for organizations handling CUI).
3. Communication & Status Updates¶
Internal notifications are driven through the platform's ticket notification system. Update frequency is based on the ticket's priority:
| Priority | Update Frequency |
|---|---|
| Critical | At least every 4 hours |
| High | At least daily |
| Medium / Low | At each phase transition |
External Reporting¶
For incidents evaluated as a FedRAMP Reportable Incident, the PAIN rating sets the external reporting clocks (defaulting to PAIN 5 when a rating is not promptly estimated). The required reports are the Initial Incident Report (IIR), Ongoing Incident Report (OIR), and Final Incident Report (FIR), with the initial and final report deadlines tracked as OLAs (Operational Level Agreements, internal deadline commitments) on the incident ticket. See the Incident Response Policy and Procedures for the reporting timeframes.
Sending a Report¶
The ticket steps and actions for each report are:
| Ticket step | Fill-in action | Send action | After sending |
|---|---|---|---|
| Initial Report Due | Initial Report | Send FedRAMP Initial Incident Report | Moves to Ongoing Report Due |
| Ongoing Report Due | Ongoing Report | Send FedRAMP Ongoing Incident Report | Stays on Ongoing Report Due |
| Final Report Due | Final Report | Send FedRAMP Final Incident Report | Moves to AAR Due |
- Click the fill-in action to record the report content. It sends nothing and does not move the ticket.
- Click the matching Send action. A templated email opens in preview.
- Enter Reported To and the Sent At time, confirm the recipients, then press Send in the preview. Nothing goes until you press Send there.
- Click Recovery Complete when recovery finishes. The ticket moves to Final Report Due.
Notice emails print dates in UTC and label them "(UTC)". For practice runs, tick Is Exercise, type "EXERCISE: " at the start of the email subject, and address the internal mailbox. See FedRAMP Notices for the windows, checks, and daily sweep that score each report.
Record All Communications
All incident communications, both internal and external, should be tracked within the ticket to maintain a complete record for audit and compliance purposes.
4. Lessons Learned & Follow-Up Actions¶
Once the final report is sent (or, for a non-reportable incident, from Evaluated), the Incident Response Team conducts a post-incident review. Every incident ends in an After Action Report (AAR), which captures the review findings and is approved by the After Action Report Approvers CAB before the incident resolves. The AAR comes before Resolve:
- Click Complete AAR to record the report. The ticket is at AAR Due.
- Click AAR Approval. The ticket moves to AAR Pending.
- If the approvers reject the report, the ticket returns to AAR Due. If they approve it, the ticket moves to AAR Approved.
- Click Resolve.
The AAR documents:
- Root cause analysis - what caused the incident
- What worked well - effective response actions and processes
- Gaps identified - areas where the response fell short
- Recommendations - specific improvements to prevent recurrence
Follow-Up Tracking¶
Any improvement actions resulting from the review are tracked as platform items with:
- Assigned owner
- Target completion date
- Status tracking through to closure
5. Audit & Compliance¶
Annual audits of incident response compliance include a review of GRC-ITSM records to verify:
- Incidents were properly detected and tracked
- Response activities were documented at each phase
- Incidents were resolved with appropriate evidence, after the After Action Report was approved
- Every incident closed with an approved After Action Report
- Required external reporting was completed on time
DFARS Reporting Requirement
For CUI incidents where DFARS 252.204-7012 applies, DIB-CS notification must be completed within 72 hours of discovery. Verify this timeline is met as part of every CUI incident review.
Any exceptions or procedural violations identified during audit are documented in the GRC-ITSM platform with corrective actions tracked to closure.
Related documentation¶
- Incident ticket type -- the Incident record and fields
- Alert ticket type -- the Alert record and triage