ICS
2Respond and manage

Resources

NIMS resource management is how an incident gets the right people and equipment, and gives them back. It has three parts: a common way to describe resources, a record of who is qualified, and one process for every request.

Typing

NIMS describes a resource by kind, what it is, and type, how capable it is. Typing lets a request say exactly what is needed and lets a supplier confirm it can deliver. Define your cyber resources the same way before the incident.

Example

ResourceKindType 1Type 2
Incident CommanderPersonnelHas commanded a Type 2 or larger incidentHas commanded a Type 3 incident
Forensic analystPersonnelLeads host and memory forensics and defends the findingsCollects and processes evidence under supervision
Rebuild strike teamTeamFive technicians with imaging rights and a staging areaThree technicians with imaging rights
Clean administration kitEquipmentHardened workstation, break-glass credentials, offline toolsHardened workstation

Qualification and credentialing

NIMS separates qualifying a person for a position, certifying that they meet the standard, and credentialing them so other organizations can trust it. FEMA's qualification system uses position task books, which list the tasks a person must show they can do in a role. Write a one-page task book for each seat you fill, and sign it off after an exercise or a real incident.

FEMA's IS-703.b course calls the position task book a basic tool of the NIMS performance-based qualification process. An evaluator initials each task as the trainee performs it. The codes come from FEMA's task books.

Sample task book: Operations Section Chief, cyber incident

POSITION TASK BOOK (after the FEMA NQS position task book)
Position: Operations Section Chief, cyber incident
Trainee:                          Opened:          Complete by:
Codes: T tabletop, F functional exercise, I incident, J daily job

#   Task                                              Codes   Evaluator, date
1   Agrees with the IC which containment actions      T F I
    need approval before they run
2   Builds groups of three to seven, each with a      T F I
    named supervisor
3   Builds the ICS 215 at the tactics meeting         F I
4   Gets engineering sign-off before containment      T F I
    touches a physical process
5   Orders by kind and type on the resource request   F I
6   Delivers the ICS 204s at the operations briefing  F I
7   Reports to Planning on the IAP cadence            F I
8   Hands over from the shift handover checklist,     T F I
    with 30 minutes of overlap
9   Keeps an ICS 214 activity log                     T F I J

Evaluation record
#   Evaluator (name, position)   Incident or exercise   Dates
    Recommendation: ready / more practice needed
Final evaluator: every task initialed; position filled on (incident
or functional exercise):              Signed:          Date:
Certified by (program lead or CISO):                   Date:

The resource management process

NIMS runs every incident resource through six steps. Several resources can be at different steps at once.

StepIn a cyber incident
Identify requirementsOperations states what it needs, by kind and type, at the tactics meeting
Order and acquireLogistics orders from inside the organization, the retainer or mutual aid. Finance/Admin approves the spend
MobilizeCheck-in, assignment, access granted, briefing
Track and reportThe Resources unit keeps status: assigned, available, resting, released
DemobilizeCheck-out: access revoked, evidence handed over, hardware returned
Reimburse and restockInvoices paid, insurance claim filed, licenses and spares replaced

Requesting a resource

Every request uses one form, whatever the source. As on FEMA's ICS 213 RR, the requester fills in the top, Logistics the middle and Finance/Admin the bottom. NIMS asks managers to plan demobilization as they mobilize, so each request says when the resource can go.

Resource request (after ICS 213 RR)

RESOURCE REQUEST (after ICS 213 RR)
Incident name:                    Request number:
Date, time, time zone:
REQUESTER
  Qty   Kind   Type   Description (skills, tools, licenses, clearances)
        Needed by   Estimated arrival   Estimated cost
  Report to (bridge, room, channel, site):
  Suitable substitutes and suggested sources:
  Access needed, and for how long:
  Release when (condition or date):
  Requested by (name, position):
  Priority:   urgent / routine / low
  Section chief approval:
LOGISTICS
  Order number:
  Supplier and contact (name, phone, email):
  Retainer or contract number:
  Notes:
  Approved by (Logistics):                  Date, time:
  Ordered by:   Logistics / Finance/Admin procurement
FINANCE/ADMIN
  Reply and comments (spend authority, insurer approval, cost code):
  Signed:                                   Date, time:

Tracking status

The Resources unit keeps one board for everything checked in. ICS marks each resource assigned, available or out of service, and a responder resting until relief is out of service. Whoever changes a status tells the Resources unit at once.

Example

ResourceKind, typeSource, requestAssigned toStatus, sinceNext changeAccess ends
Forensic analyst, response firmPersonnel, Type 1Retainer, RR-004Investigation groupAssigned, 07:00Relief at 19:0018:00 Friday
Rebuild strike team BTeam, Type 2Service desk, RR-002Rebuild groupOut of service, resting, 19:10Back at 07:00Kept

Activating a retainer

#ItemOwner
1Retainer number, hotline, authorized callers and contract end date on the offline rosterFinance/Admin
2Activation decided within delegated authority, logged, and called in by an authorized callerIncident Commander
3Insurer notified, and the firm confirmed on its panel or approved in writing before work startsFinance/Admin
4Where privilege matters, counsel engages the firm or confirms in writing that it directs the workLegal advisor
5Scope written: systems, questions, deliverables and who receives themOperations
6Hours tracked from the first call, with a daily report and an alert at three quarters of the prepaid hoursFinance/Admin
7The firm's people checked in, verified by voice, given access with an end date, and briefedLogistics

Script for activating a retainer

This is [name], [title] at [organization], an authorized caller on
retainer [number]. I am activating it for a suspected [incident
kind], declared at [time and time zone]. Our Incident Commander is
[name]. [Counsel and firm] will engage you, and your reports go to
counsel. Our insurer is [carrier], notice number [number]. Please
confirm you are on its panel. We need [kind, type, number] by
[time], first to [scope]. Send hours used daily to [Finance/Admin
contact]. Call back on [out-of-band number] with your lead's name
and arrival time.

Mutual aid

Mutual aid agreements let organizations lend each other resources on terms agreed in advance. For cyber, the sources are your sector's ISAC, peer organizations, technology partners, and government support, which varies by sector and state. Agree the terms before you need them: who can ask, what is provided, who pays, and how access and confidentiality work.

An ISAC can share indicators and connect you with members who have seen the same activity. A peer can lend people, checked in and released like any other resource. Label what you share with FIRST's Traffic Light Protocol, such as TLP:AMBER.

Script for a mutual aid request

This is [name], [position] at [organization], a member of [ISAC or
agreement]. We have an active [kind] incident, declared at [time
and time zone]. We ask for [indicators and advice / people by kind,
type and number] for [duration], from [time], under [agreement].
People you send report to [name] on [out-of-band channel], and
their access ends at release. What we share is [TLP label]. Costs
follow [the agreement's terms]. Please confirm by [time] on
[callback number].

Built from NIMS, third edition (October 2017), on resource management; FEMA's IS-703.b course on position task books; FEMA's ICS 213 RR form; the task codes in FEMA National Qualification System task books; FEMA's Planning Section Chief course (E/L 962) on resource status; and FIRST's Traffic Light Protocol 2.0. The layouts, task list, checklist and scripts are additions to this guide.

Adapted from the National Incident Management System, Third Edition (FEMA, 2017). Cyber adaptation, examples and templates by Habib Tora, licensed under CC BY 4.0. Not published by, endorsed by, or affiliated with FEMA or the Department of Homeland Security. Structure after Google's SRE Incident Management Guide. Companion to PIVTR-D.