IR-4(2) Incident Handling | Dynamic Reconfiguration
Include FedRAMP-defined types of dynamic reconfiguration for FedRAMP-defined system components as part of the incident response capability.
3
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
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
- Exercise records showing dynamic reconfiguration actually performed · Document repository
governing documentDocuments that govern the control
- Incident response plan section naming the components that can be dynamically reconfigured · Policy repository / GRC workspace
- Runbooks for isolation, rule changes or rerouting during an incident · 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
- Capability exists technically but is not written into the incident response plan
- Never exercised, so the achievable change window is unknown
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 sheetIR-4(1) Automated Incident Handling Processes · IR-4(4) Information Correlation