Engineer working on a laptop connected to a device test rig, surrounded by wiring harnesses and test hardware

Firmware vulnerabilities & fixes

NIST SP 800-34: Contingency Planning Guide, explained

Last updated:

NIST SP 800-34 (Contingency Planning Guide for Federal Information Systems) organizes information system recovery planning into a seven-step process — from a contingency planning policy statement through business impact analysis, preventive controls, recovery strategy, plan development, testing/training, and plan maintenance — for US federal organizations and, by widespread adoption, many others. Its own abstract states it "assists organizations in understanding the purpose, process, and format of information system contingency planning development through practical, real-world guidelines." The current edition is Revision 1 (May 2010, updated November 2010), authored by Marianne Swanson, Pauline Bowen, Amy Phillips, Dean Gallup and David Lynes; it supersedes the original June 2002 release and, per NIST's own keyword list for the publication, sits alongside — but distinct from — incident response plans and disaster recovery plans.

Key takeaways

  • The full text of SP 800-34 Rev.
  • The guide is precise about what an ISCP is and is not.
  • Cold sites — "typically facilities with adequate space and infrastructure (electric power, telecommunications connections, and environmental controls)" but without pre-installed systems.
  • The business impact analysis in SP 800-34 Rev.

What the guide covers

Per its official abstract, the document "provides background information on interrelationships between information system contingency planning and other types of security and emergency management-related contingency plans, organizational resiliency, and the system development life cycle," and "provides guidance to help personnel evaluate information systems and operations to determine contingency planning requirements and priorities." In other words, it is not a single plan template — it is a framework for deciding which systems need a contingency plan, how detailed that plan needs to be, and how it connects to an organization's broader resiliency and development-lifecycle processes.

What does the seven-step process look like?

The full text of SP 800-34 Rev. 1 lays out seven progressive steps, intended to be integrated into each stage of the system development life cycle rather than treated as a one-off project:

Step Focus
1 Develop the contingency planning policy statement
2 Conduct the business impact analysis (BIA)
3 Identify preventive controls
4 Create contingency strategies
5 Develop an information system contingency plan
6 Ensure plan testing, training, and exercises
7 Ensure plan maintenance

The business impact analysis (step 2) is the step that determines everything downstream: it identifies which systems and components are critical to mission/business processes, which in turn drives how much a recovery strategy (step 4) is allowed to cost and how fast it needs to work.

Information System Contingency Plan vs. incident response vs. disaster recovery

The guide is precise about what an ISCP is and is not. Its own definition: "An ISCP provides established procedures for the assessment and recovery of a system following a system disruption. The ISCP provides key information needed for system recovery, including roles and responsibilities, inventory information, assessment procedures, detailed recovery procedures, and testing of a system." NIST's keyword list for the publication names "incident response plan," "disaster recovery plan," and "information system contingency plan" as related but separate document types — an incident response plan governs detection and immediate handling of a security event (see our NIST SP 800-61 incident response guide), a disaster recovery plan typically governs facility-level or regional disruptions, and the ISCP governs recovery of a specific information system once a disruption has already occurred.

Alternate-site strategy options

For system-level recovery strategies (step 4), SP 800-34's full text describes a range of alternate-site options organizations can choose between, trading cost against recovery speed:

  • Cold sites — "typically facilities with adequate space and infrastructure (electric power, telecommunications connections, and environmental controls)" but without pre-installed systems.
  • Warm sites — "partially equipped office spaces that contain some or all of the system hardware, software, telecommunications, and power sources."
  • Hot sites — "facilities appropriately sized to support system requirements and configured with the necessary system hardware, supporting infrastructure, and support personnel."
  • Mobile sites — "self-contained, transportable shells custom-fitted with specific telecommunications and system equipment."
  • Mirrored sites — "fully redundant facilities with automated real-time information mirroring."

Where this fits for device and firmware fleets

SP 800-34 was written for federal information systems in general, not embedded devices specifically, but the same logic transfers directly to a fleet of connected devices or industrial equipment: a BIA-style exercise identifies which device classes or control-system functions are mission-critical, preventive controls and recovery strategies are sized to that criticality, and the resulting plan is tested and maintained rather than written once and filed away. Teams already building out incident response (see NIST SP 800-61) or continuous monitoring (see NIST SP 800-137) programs can treat contingency planning as the missing third leg: what happens, concretely, once monitoring detects a disruption that incident response cannot simply patch around.

How do MTD, RTO and RPO work for a device fleet?

The business impact analysis in SP 800-34 Rev. 1 uses three time values. They were defined for information systems, and each has a direct meaning for a fleet of connected products and the cloud services behind them:

SP 800-34 term Definition in the guide (paraphrased) Device-fleet reading
Maximum Tolerable Downtime (MTD) Total time a business process can be disrupted before the impact becomes unacceptable How long customers can run without the companion app, cloud control or remote monitoring before contracts, safety or reputation suffer
Recovery Time Objective (RTO) Maximum time a system resource can stay unavailable before it affects other resources and the MTD Time to restore the update server, device-management backend or licence service; must be shorter than the MTD
Recovery Point Objective (RPO) Point in time to which data must be recoverable after an outage How much telemetry, configuration and device-registration data you can afford to lose; drives backup frequency

Two values matter for devices that the federal text does not name: the time to roll back a bad firmware release across the fleet, and the time to reprovision a device whose credentials or firmware cannot be trusted. Record both alongside the RTO for each backend service.

What should the plan's three recovery phases contain?

SP 800-34 Rev. 1 organises the Information System Contingency Plan into an Activation and Notification phase, a Recovery phase and a Reconstitution phase, framed by supporting information and appendices such as contact lists and procedures. For a device maker the phases become concrete steps:

  1. Activation and notificationName who can declare a fleet incident (for example, a failed update bricking units or a signing-key compromise), the criteria for declaring it, and who is called: firmware lead, cloud operations, support and the people who talk to customers.
  2. RecoveryOrdered procedures: pause the update campaign, restore the update and device-management services from backup, ship a corrective or rollback image, and guide customers through any manual recovery.
  3. ReconstitutionVerify that devices and services are back to normal operation, validate data, close the incident and document what happened before standing down.

How do firmware resiliency and update design support recovery?

Recovery planning is easier when the product itself can recover. NIST SP 800-193, Platform Firmware Resiliency Guidelines, organises firmware resiliency around three principles: protecting platform firmware from unauthorised changes, detecting when it has been corrupted, and recovering it to a known-good state. A device that has a protected recovery image and authenticated updates turns a potential truck roll into a remote fix.

On the update path, RFC 9019, the IETF architecture for firmware updates on IoT devices, describes signed manifests, the roles of author, distribution system and device, and status reporting back to the operator. Those status reports are what tells the contingency team how many units have taken a bad image and how many have recovered.

At the programme level, the NIST Cybersecurity Framework 2.0 places restoration activities under its Recover function, which is a convenient place to link the contingency plan to the rest of a security programme.

How should a device fleet plan be tested and maintained?

SP 800-34 expects contingency plans to be exercised and kept current, and points to SP 800-84, Guide to Test, Training, and Exercise Programs, for the exercise formats. A workable cadence for a small device maker:

  • Tabletop exercise (discussion-based) once a year, walking through a scenario such as a signing-key leak.
  • Functional exercise on a test fleet: deliberately push a faulty image to lab units and time the rollback against your targets.
  • Plan review whenever the architecture changes: a new cloud region, a new update mechanism, a new manufacturing partner.
  • Contact list check every quarter; out-of-date phone numbers are the most common reason activation is slow.

Worked example: a failed firmware rollout

Synthetic example, for illustration only. The company and figures are invented.

A maker of connected irrigation controllers sets an MTD of 72 hours for remote scheduling, an RTO of 8 hours for its update service and an RPO of 1 hour for device configuration. A new release corrupts settings on a subset of units. The on-call firmware lead activates the plan, pauses the rollout and checks update status reports to size the affected population. The team restores configuration from the hourly backup, ships the previous signed image as a rollback, and tells affected customers how to confirm their schedules. In reconstitution they compare restored configurations against backups, then hold a review that adds a staged rollout percentage to the release checklist.

What are the common pitfalls?

  • Planning only for the data centre. The fleet in the field is the hardest part to recover; plan for it explicitly.
  • No rollback path. If the device cannot accept a previous signed image, the RTO for a bad release is "unknown".
  • Backups of the backend but not of signing infrastructure. Losing the code-signing key or its hardware module can stop all updates.
  • Untested plans. A plan that has never been exercised against a lab fleet tends to fail on its first real use.
  • Confusing contingency with incident response. Incident response handles the attack; contingency planning restores service. Both need owners.

SoftWSP's device and firmware security work can help translate SP 800-34's planning process into something scoped to a real device fleet rather than a generic federal system: see device & firmware security services.

This guide summarises a public NIST publication; it does not constitute legal or compliance advice.

Put this guide to work

Frequently asked questions

What is NIST SP 800-34?

Contingency Planning Guide for Federal Information Systems, a NIST Special Publication whose official abstract states it "assists organizations in understanding the purpose, process, and format of information system contingency planning development through practical, real-world guidelines" and "provides background information on interrelationships between information system contingency planning and other types of security and emergency management-related contingency plans, organizational resiliency, and the system development life cycle." The current version is Revision 1, published May 2010 and updated 11 November 2010, authored by Marianne Swanson, Pauline Bowen, Amy Phillips, Dean Gallup and David Lynes; it supersedes the original June 2002 edition.

What is the seven-step contingency planning process?

NIST SP 800-34 Rev. 1 organizes its guidance around seven steps: (1) develop the contingency planning policy statement, (2) conduct the business impact analysis (BIA), (3) identify preventive controls, (4) create contingency strategies, (5) develop an information system contingency plan, (6) ensure plan testing, training, and exercises, and (7) ensure plan maintenance. The guide describes these as progressive steps meant to be integrated into each stage of the system development life cycle rather than a one-time exercise.

What is an Information System Contingency Plan (ISCP)?

Per the guide's own definition, "An ISCP provides established procedures for the assessment and recovery of a system following a system disruption. The ISCP provides key information needed for system recovery, including roles and responsibilities, inventory information, assessment procedures, detailed recovery procedures, and testing of a system." It sits alongside — and is distinct from — incident response plans and disaster recovery plans, which the guide's keyword list names as related but separate document types.

What alternate-site strategies does the guide describe?

The guide describes a spectrum of recovery facility options, including cold sites ("typically facilities with adequate space and infrastructure" but little or no pre-installed equipment), warm sites ("partially equipped office spaces that contain some or all of the system hardware, software, telecommunications, and power sources"), hot sites ("facilities appropriately sized to support system requirements and configured with the necessary system hardware, supporting infrastructure, and support personnel"), mobile sites ("self-contained, transportable shells custom-fitted with specific telecommunications and system equipment"), and mirrored sites ("fully redundant facilities with automated real-time information mirroring"). Organizations select among these based on recovery time requirements and cost.

Sources

  1. NIST CSRC: SP 800-34 Rev. 1 — Contingency Planning Guide for Federal Information Systems (publication detail, abstract, keywords)
  2. NIST: Contingency Planning Guide for Federal Information Systems [including updates through 11/11/2010] (authors, publication date)
  3. NIST SP 800-34 Rev. 1 — full text (seven-step process, ISCP definition, alternate-site types)
  4. NIST: Contingency Planning Guide for Information Technology Systems (original 2002 edition, superseded)
  5. NIST SP 800-193: Platform Firmware Resiliency Guidelines
  6. IETF RFC 9019: A Firmware Update Architecture for Internet of Things
  7. NIST CSWP 29: The NIST Cybersecurity Framework (CSF) 2.0
  8. NIST SP 800-84: Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities
Was this guide helpful?

In this cluster