Demobilization
Demobilization releases people and resources in order, and closes out access, evidence custody and hours for every person. Planning writes the demobilization plan as soon as the end is in sight, and the IC approves it.
NIMS sets its goal as the orderly, safe and efficient return of each resource to its original location and status.
Exit criteria
The Incident Commander ends the incident when every item below is met and recorded.
| # | Item | Owner |
|---|---|---|
| 1 | Each objective met, or moved to the remediation project by a recorded decision | Incident Commander |
| 2 | Technical closure signed on PIVTR-D T5, with the monitoring kept and its end date | Operations |
| 3 | Residual risks accepted by the risk owner on PIVTR-D T6, with the conditions that would reopen the incident | Incident Commander |
| 4 | Restored systems accepted by their owners and running normally | Operations |
| 5 | Every notification made, or assigned to a named owner with its deadline | Legal advisor |
| 6 | Every open action and outside commitment closed, or given an owner outside the incident | Planning |
| 7 | Closeout meeting completed with the executive who delegated authority: lasting consequences, unfinished records, their concerns | Incident Commander |
Work that outlasts the incident becomes a remediation project, run through normal project and change management. Before the stand-down, record three things: an owner who has accepted the work, a backlog, and a first review date at the incident review board.
The backlog gives each item a priority and a source such as a T6 compensating control. Work without an owner stays in the incident.
Stepping down
- Fold a section back when the person above it can carry its remaining work for a full operational period.
- Make each change at the start of an operational period, and write it in the IAP.
- Keep Planning until the records are consolidated, Liaison until every outside commitment is closed, and Finance/Admin until final invoices are requested.
- At Type 4 the ICS 201 is the plan again.
- Handing back from a larger or outside team is a transfer of command. In FEMA's ICS 300 course, the type is reduced, with any transfer of command, when the Agency Administrator agrees.
The Incident Commander announces each change on the command bridge and in the next status summary, naming who now carries each folded duty.
Release order
Release outside responders and borrowed staff as their objectives close. Keep core responders until eradication is verified. Keep monitoring capacity after that, at the level the recovery plan calls for.
Check-out, per person (after ICS 221)
| # | Item |
|---|---|
| 1 | Assignment handed to a named person, or closed |
| 2 | Activity log submitted to Documentation |
| 3 | Notes, evidence and media handed over, with custody recorded |
| 4 | Temporary accounts, access and tokens revoked |
| 5 | Loaner hardware and licenses returned |
| 6 | Hours submitted to Finance/Admin |
| 7 | Rest before the next shift or return to normal duty |
Closing the incident organization
| # | Item |
|---|---|
| 1 | IC declares the end of the incident, with the time |
| 2 | Final status summary issued |
| 3 | Emergency changes reviewed and closed or made permanent |
| 4 | Outside engagements ended in writing and final invoices requested |
| 5 | Records consolidated by Documentation and indexed |
| 6 | Costs totaled by Finance/Admin, insurer's claim file updated |
| 7 | After-action review scheduled, run as the PIVTR-D debrief |
Writing the plan
One plan covers the incident, adapted from the sections of the ICS demobilization plan. Each person's release goes on an ICS 221, and each decision to keep a containment measure goes in the decision register.
Demobilization plan
DEMOBILIZATION PLAN Incident name and number: Date: Prepared by (Planning): Exit criteria met, with the record for each: Objectives met or moved: Technical closure (T5): Residual risk accepted (T6): Notifications made or assigned: Open actions and commitments assigned: Resources to release, in order: # Resource or group Release after Released by ICS 221 done What stays, and until when: Monitoring (rules, watch list, alert route): until: On-call contact: until: Containment measures kept, by recorded decision: Records to file, and where: Activity logs, IAPs, decision register, evidence register, final ICS 209, T5, T6: Handoff: Remediation project: Owner: Backlog at: First review date: Stand-down announcement (date, time, time zone): Approved by (Incident Commander): Date, time: Accepted by (remediation owner): Date, time: Agreed by (Agency Administrator): Date, time:
Standing down
The Incident Commander reads the stand-down on the command bridge at the planned time, then posts it in the incident channel and the final status summary.
Script for announcing the stand-down
This is [name], Incident Commander for [incident name]. As of [time and time zone], the incident is closed and the incident organization stands down. The exit criteria are met and signed. [Owner name] owns the remaining work as [project name], with a first review on [date]. Monitoring continues until [date]. Report any new sign of this incident to [on-call contact], who can reopen it. Submit activity logs and hours by [time]. The after-action review is on [date].
Retained monitoring
- Detection rules written during the incident stay enabled, and their alerts reach the on-call team tagged with the incident name.
- A named analyst checks a daily watch list of the accounts, hosts, indicators and third-party connections from scope, with the T6 conditions that would reopen the incident beside it.
- The end date is set at closure. Start with 30 days, and 90 where the attacker had privileged access. On that date the owner ends the monitoring, extends it once, or makes the rules permanent detection content.
Responder recovery
- Anyone who worked past the maximum shift length, or more days in a row than the agreed limit, takes at least one full day off before normal duty. Their manager protects it.
- Each manager runs a one-to-one check-in with each responder within a week of release: sleep, workload, anything that still weighs on them, and where to get support, such as the employee assistance program.
- Compensatory time or pay follows HR policy, from the hours Finance/Admin recorded.
Built from NIMS, third edition (October 2017), and FEMA's ICS 300 course, Unit 7, for the plan's sections, the closeout meeting and reducing the type. The exit criteria, step-down rules, plan layout, script, monitoring and recovery steps are additions to this guide.