IR-4(11) Incident Handling | Integrated Incident Response Team
Establish and maintain an integrated incident response team that can be deployed to any location identified by the organization within a FedRAMP-defined time period.
3
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Records of deployment or remote engagement inside the committed period · Source control / CI pipeline
governing documentDocuments that govern the control
- Incident response team charter with named roles and deployment commitments · Policy repository / GRC workspace
- On-call roster and escalation tree · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- Team is a distribution list rather than named accountable roles
- No deployment time commitment defined, so it is never measured
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet