Seeded demo · auth off · no application database · GitLab SoT / GitHub twin · not an ATO
CC7.4 — Incident response program execution
NIST SP 800-53 Revision 5 · assessed by internal audit
Data as of23 Aug 2026
What this requires
In plain language: the outcome this security requirement is meant to achieve.
The entity responds to identified security incidents by executing a defined incident response program.
How we check it
Review post-incident reviews for the period; confirm each contains root cause and corrective actions.
Source mappings
Traceability from this Rev. 5 control to DAAG, organizational guidance, and DCSA supplemental guidance.
DAAG reference
Not supplied in uploaded sources
Organization document
Not supplied in uploaded sources
Implementation narrative
Not supplied in uploaded SSP
DCSA supplemental guidance
Not supplied in uploaded sources
Proof
Documents and records that show this requirement is met.
| Artifact | Kind | Status | Collected | Expires | Source | Digest |
|---|---|---|---|---|---|---|
| Post-incident review — INC-2291 Manual114 KB | Policy document | Valid | 18 Jun 2026 | 18 Dec 2026 | Confluence Hannah Feld | 50b61c72d83e… |
| Post-incident review — INC-2340 Manual | Policy document | Missing | — | — | Confluence Dana Okafor | unhashed |
Problems
Open issues tied to this requirement. 1 total.
FND-1018MediumOpen
Post-incident review missing for INC-2340
A severity-2 incident from June closed without a documented post-incident review, so root cause and corrective actions were never recorded.
Remediation Produce the retrospective review and block incident closure in the tooling until the review is attached.
Manual testINC-2340opened 18 Jun 2026due 18 Jul 2026
Test record
- Framework
- NIST 800-53 5.1.1
- Domain
- Incident Response
- Test method
- Manual
- Last tested
- 18 Jun 2026
- Next due
- 18 Aug 2026
- Retest window
- 5d overdue
Accountable owner
Audit period
NIST SP 800-53 Revision 5
- Window
- — – —
- Authority
- NIST
- Assessor
- Internal audit