Respond and manage
Google's incident guide warns that an unmanaged response turns chaotic, and recommends running the response like a project, with planning, a deliberate choice of who is involved, and a written record. ICS is the structure for that project.
ICS came out of the California wildfires of the 1970s, when agencies fighting the same fire used different terms, different radios and different plans. Cyber incidents break down in the same places.
Nobody is sure who decides, three people brief executives with three different numbers, and responders reach hour 30 with no relief. A vendor, counsel and an insurer each run their own version of the response.
Coordinate, communicate, control
Google's incident management system, IMAG, is built on ICS and organizes around three Cs. Each maps onto NIMS positions.
| C | What it means | Owned by |
|---|---|---|
| Coordinate | One set of objectives and one plan, with every responder working to it | Incident Commander, Planning |
| Communicate | Every audience hears the same facts on a schedule, and incoming requests have one door | Public Information Officer, Liaison |
| Control | Clear assignments, a manageable span of control, and changes made through command | Incident Commander, Operations |
Start with three roles
Most incidents need three seats filled. Google's guide names the same three.
| NIMS position | Google IMAG | Owns |
|---|---|---|
| Incident Commander | Incident Commander (IC) | The overall response: objectives, priorities, decisions, handover |
| Public Information Officer | Communications Lead (CL) | Regular updates to every audience, and the single contact for incoming questions |
| Operations Section Chief | Operations Lead (OL) | Mitigating the issue, limiting impact, resolving the problem |
Incident roles go to whoever knows the systems and the situation best. Day-job reporting lines pause until the incident closes.
The full organization
When the incident runs past one shift or one team, the rest of the structure fills in around those three.
Getting more help
NIMS describes Incident Management Teams, which are rostered groups of ICS-qualified people, typed by capability, who deploy to manage incidents that outgrow local capacity. Google has Incident Response Teams it can activate for additional support during major incidents. In cyber, the equivalents are an internal major-incident team drawn from across the organization, the incident response firm on retainer, and an executive crisis team for decisions above the Incident Commander's authority.
Decide in advance who activates each one, and how.
In this section
| Page | Covers |
|---|---|
| Principles | The 14 NIMS management characteristics, in cyber terms |
| The organization | Every seat, what it owns, who fills it |
| Position checklists | A job aid for each seat: on taking it, every period, before handing over |
| Sizing the response | Complexity types, and when to grow or shrink |
| The planning cycle | Operational periods, the meetings, the Incident Action Plan |
| Unified command | Several parties with authority running one response |
| Partner-run infrastructure | Commanding your response when a cloud or hosting partner caused the failure |
| By incident type | What each incident type and regulated sector adds to command |
| Above the incident | The crisis team, the executive group and the joint information system |
| Resources | Typing, qualification, the six-step resource process, mutual aid |
| Communications and information | Channels, cadence, what every update answers, the common operating picture |
| Command and handover | Taking command, transferring it, shift change |
| Extended incidents | Working limits, rotating command and a slower cycle for incidents that run for weeks |
| Demobilization | Releasing people and closing the incident organization |