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

Firmware vulnerabilities & fixes

NIST SP 800-160: systems security engineering, explained

Last updated:

NIST SP 800-160 is a two-volume NIST Special Publication whose two current editions were finalized in November 2022 and December 2021, covering systems security engineering and cyber-resiliency engineering respectively. Volume 1, "Engineering Trustworthy Secure Systems" (current version Revision 1, published November 2022), states its own purpose as describing "a basis for establishing principles, concepts, activities, and tasks for engineering trustworthy secure systems," meant to be applied "within systems engineering efforts to foster a common mindset to deliver security for any system, regardless of the system's purpose, type, scope, size, complexity, or the stage of its system life cycle." Volume 2, "Developing Cyber-Resilient Systems: A Systems Security Engineering Approach" (current version Revision 1, published December 2021), narrows the focus to cyber resiliency — engineering systems that keep functioning, or degrade gracefully, under attack rather than assuming every attack can be stopped.

Key takeaways

  • NIST SP 800-160 is a two-volume NIST Special Publication whose two current editions were finalized in November 2022 and December 2021, covering systems security engineering and cyber-resiliency engineering respectively.
  • SP 800-160 Volume 1 Revision 1 collects a set of principles for trustworthy secure design in an appendix.
  • SP 800-160 Volume 2 Revision 1 frames cyber resiliency as four goals (anticipate, withstand, recover, adapt) supported by objectives and by a set of 14 techniques.
  • SP 800-160 tells you how to engineer the system.

How does Volume 1 treat security engineering as a discipline, not an afterthought?

NIST's own abstract for Volume 1 Revision 1 states the publication's intent is "to advance systems engineering in developing trustworthy systems for contested operational environments (generally referred to as systems security engineering) and to serve as a basis for developing educational and training programs, professional certifications, and other assessment criteria." The framing throughout Volume 1 is deliberately general-purpose: the same principles, concepts, activities and tasks are meant to apply "regardless of the system's purpose, type, scope, size, complexity, or the stage of its system life cycle" — in other words, Volume 1 is not a checklist for one kind of product, but a shared vocabulary and method for building security considerations into any systems-engineering effort from the start, rather than retrofitting them after a design is already fixed.

Volume 2: engineering for resiliency, not just prevention

Volume 2 Revision 1 addresses a narrower and more specific problem: how to "architect, design, develop, implement, maintain, and sustain the trustworthiness of systems" that must keep operating under adversarial conditions. NIST describes the goal as building systems able to "anticipate, withstand, recover from, and adapt to adverse conditions, stresses, attacks, or compromises." Framed in risk-management terms, cyber resiliency engineering aims to "reduce the mission, business, organizational, enterprise, or sector risk of depending on cyber resources" — an acknowledgment that some attacks will succeed regardless of preventive controls, and that systems need to be engineered to survive and recover from that outcome, not just to resist it. NIST positions Volume 2 as complementing Volume 1 and working "alongside other NIST frameworks including the Risk Management Framework (SP 800-37) and Security Controls guidance (SP 800-53)."

How the two volumes and the wider NIST stack fit together

Publication Role
SP 800-160 Vol. 1 Principles, concepts, activities and tasks for engineering security into any system's life cycle
SP 800-160 Vol. 2 Specialized companion: engineering systems to anticipate, withstand, recover from and adapt to attacks (cyber resiliency)
SP 800-37 (see our guide) Risk Management Framework — the process for selecting, implementing, assessing and authorizing controls
SP 800-53 (see our guide) The control catalog itself — the "what" that SP 800-37's process selects from

Read together, SP 800-53 is the catalog of available security and privacy controls, SP 800-37 is the process for choosing and authorizing which controls apply to a given system, and SP 800-160 is the systems-engineering discipline that determines how security requirements — including resiliency requirements — get engineered into a system's architecture and life cycle in the first place, rather than selected and bolted on afterward. For device makers and firmware teams, Volume 1's life-cycle framing is the more directly relevant starting point; Volume 2's resiliency focus becomes relevant once a product's threat model includes the expectation that some compromise will occur and the system needs to keep operating or recover gracefully.

A workable starting point

  1. Treat Volume 1 as a vocabulary and process, not a product-specific checklist— its value is in making security an engineering discipline applied from initial requirements through disposal, not a separate review step at the end.
  2. Only reach for Volume 2's resiliency concepts once your threat model assumes some attacks will succeed— resiliency engineering (anticipate/withstand/recover/adapt) is a different design goal from baseline prevention, and conflating the two leads to either over-engineering simple systems or under-engineering systems that genuinely need to survive compromise.
  3. Use SP 800-160 alongside SP 800-37 and SP 800-53, not instead of them— NIST explicitly frames the three as complementary layers (engineering discipline, risk-management process, control catalog) rather than alternative approaches to the same problem.

Which Volume 1 design principles matter most for embedded products?

SP 800-160 Volume 1 Revision 1 collects a set of principles for trustworthy secure design in an appendix. Not all of them carry equal weight on a microcontroller with a few hundred kilobytes of flash. The ones below translate most directly into firmware and hardware decisions:

Volume 1 principle Device engineering decision it drives
Least Functionality Remove debug shells, unused network services and test commands from production builds
Least Privilege Run the network stack and parsers without access to keys or the bootloader region
Minimal Trusted Elements Keep the code that verifies boot and updates small, so it can be reviewed and tested thoroughly
Protective Defaults Ship with remote access off, unique credentials and the most restrictive configuration that still works
Protective Failure When signature verification fails, refuse the image and stay on the known-good one instead of booting anyway
Protective Recovery Provide a protected recovery image so a failed update does not need a factory return
Defense in Depth Combine secure boot, signed updates, memory protection and network segmentation so one failure does not expose everything
Self-Reliant Trustworthiness A device should stay secure when the cloud service is unreachable, not only when it is online

Each row is a design requirement you can write down, trace to a test and show to a customer or assessor, which is the point of treating security as an engineering discipline.

How do Volume 2's goals and techniques apply to a device fleet?

SP 800-160 Volume 2 Revision 1 frames cyber resiliency as four goals (anticipate, withstand, recover, adapt) supported by objectives and by a set of 14 techniques. A few techniques map cleanly onto connected products:

  • Substantiated Integrity: verify firmware and configuration with cryptographic signatures and measured boot.
  • Non-Persistence: reboot into a clean image, keep secrets in volatile memory where practical and avoid storing data that is not needed.
  • Privilege Restriction: separate the application from the security services that hold keys.
  • Segmentation: keep the device's management interface on a separate network path from its data traffic.
  • Redundancy: dual firmware banks (A/B) so a corrupted image can fall back.
  • Analytic Monitoring: fleet telemetry that shows when units fail verification or reboot unexpectedly.

Volume 2 is explicit that not every technique suits every system; choose the ones your threat model and hardware budget justify, and record why the others were left out.

How does SP 800-160 relate to the SSDF, IoT baselines and product standards?

SP 800-160 tells you how to engineer the system. Other documents describe adjacent parts of the job:

  • The Secure Software Development Framework, SP 800-218, sets out secure development practices for the software you write, from protecting the code to responding to vulnerabilities.
  • NISTIR 8259 lists foundational cybersecurity activities for IoT device manufacturers, before and after the product ships.
  • ETSI EN 303 645 is the European baseline for consumer IoT, with concrete provisions such as no universal default passwords and a published vulnerability disclosure policy.

A practical reading: SP 800-160 shapes architecture and life-cycle processes, the SSDF shapes day-to-day development, and NISTIR 8259 and EN 303 645 provide the product-level outcomes that customers and regulators check.

What does security engineering look like across the product life cycle?

  1. ConceptIdentify stakeholders, assets and loss scenarios (a bricked fleet, a leaked signing key, unsafe actuator commands). Volume 1 calls these stakeholder protection needs.
  2. RequirementsTurn each protection need into a testable requirement: "the bootloader SHALL reject unsigned images".
  3. Architecture and designApply the principles in the table above; decide on secure boot, key storage, update mechanism and isolation.
  4. ImplementationFollow SSDF practices, track third-party components in a software bill of materials, and review parsers and network code.
  5. VerificationTest each requirement, including negative tests such as tampered images and malformed packets.
  6. Transition and operationProvision unique identities at manufacture, monitor the fleet and run vulnerability handling.
  7. Maintenance and disposalShip signed updates for the declared support period and provide a way to wipe keys and data at end of life.

Worked example: tracing one requirement end to end

Synthetic example, for illustration only. The product is invented.

An industrial sensor gateway team records the loss scenario "attacker installs modified firmware". The protection need becomes requirement R-07: "the gateway SHALL boot only images signed by the vendor release key, and SHALL fall back to the previous bank on failure". Design applies Minimal Trusted Elements (a small ROM-anchored verifier), Protective Failure and Redundancy (A/B banks). Implementation stores the public key in one-time-programmable memory. Verification runs three tests: valid image boots, tampered image is rejected, corrupted bank falls back. In operation, fleet telemetry reports verification failures. One requirement, traced from a loss scenario to evidence, is the kind of record an assessor or customer can follow.

What are the common pitfalls?

  • Reading Volume 1 as a checklist. It is a process and a vocabulary; the product-specific requirements are yours to write.
  • Starting resiliency work before basic hygiene. Diversity and deception techniques do little if default passwords and unsigned updates remain.
  • No traceability. Requirements that cannot be traced to a loss scenario and a test are hard to defend in an assessment.
  • Ignoring the supply chain. Third-party components and chips inherit their own vulnerabilities; keep an SBOM and watch for new advisories.
  • Stopping at release. Operation, maintenance and disposal are life-cycle stages too.

SoftWSP's device and firmware security work can help build security engineering into your product's architecture and life cycle from the start, rather than retrofitting it after design decisions are already locked in: see device & firmware security services.

This guide summarises NIST's public CSRC publication pages for SP 800-160 Volumes 1 and 2; it does not constitute legal or compliance advice.

Put this guide to work

Frequently asked questions

What is NIST SP 800-160?

A two-volume NIST Special Publication on systems security engineering. Volume 1, titled "Engineering Trustworthy Secure Systems," states its own purpose as describing "a basis for establishing principles, concepts, activities, and tasks for engineering trustworthy secure systems," applicable "within systems engineering efforts to foster a common mindset to deliver security for any system, regardless of the system's purpose, type, scope, size, complexity, or the stage of its system life cycle." Volume 2, titled "Developing Cyber-Resilient Systems: A Systems Security Engineering Approach," addresses the narrower discipline of cyber resiliency engineering — building systems able to "anticipate, withstand, recover from, and adapt to adverse conditions, stresses, attacks, or compromises."

What's the difference between Volume 1 and Volume 2?

Volume 1 (current version: Revision 1, published November 2022) is the general-purpose foundation — it sets out principles, concepts, activities and tasks for building security into systems engineering broadly, intended partly "to advance systems engineering in developing trustworthy systems for contested operational environments" and to underpin educational programs, certifications and assessment criteria. Volume 2 (current version: Revision 1, published December 2021) is the specialized companion focused specifically on cyber resiliency: how to architect and sustain systems that keep operating, or degrade gracefully, under adversarial conditions rather than systems security engineering in general.

Why does cyber resiliency need its own volume?

Because resiliency is a distinct engineering goal from baseline security. SP 800-160 Vol. 2 Rev. 1 frames cyber resiliency, from a risk-management perspective, as aiming to "reduce the mission, business, organizational, enterprise, or sector risk of depending on cyber resources" — the assumption is not that every attack can be prevented, but that systems must keep functioning, recover, or adapt when some attacks succeed. That is a different design question from the general security-engineering principles in Volume 1, which is why NIST split it into its own volume rather than folding it in as a chapter.

How does SP 800-160 relate to SP 800-37 and SP 800-53?

NIST positions the three as complementary layers rather than overlapping ones: SP 800-160 Vol. 2 Rev. 1 is described as working "alongside other NIST frameworks including the Risk Management Framework (SP 800-37) and Security Controls guidance (SP 800-53)." In practice, SP 800-53 (see our [guide](/guides/nist-sp-800-53-security-privacy-controls/)) supplies the catalog of security and privacy controls, SP 800-37 (see our [Risk Management Framework guide](/guides/nist-sp-800-37-risk-management-framework/)) supplies the process for selecting, implementing, and authorizing those controls, and SP 800-160 supplies the systems-engineering discipline — how security requirements get engineered into a system's architecture and life cycle in the first place, including resiliency-specific engineering in Volume 2.

Sources

  1. NIST SP 800-160 Volume 1 Revision 1: Engineering Trustworthy Secure Systems (final, November 2022) — CSRC publication page
  2. NIST SP 800-160 Volume 2 Revision 1: Developing Cyber-Resilient Systems: A Systems Security Engineering Approach (final, December 2021) — CSRC publication page
  3. Wikipedia: ISO/IEC 15288 — Systems and software engineering, System life cycle processes (the systems-engineering life cycle standard Volume 1 supplements with security extensions)
  4. NIST SP 800-160 Vol. 1 Rev. 1 — full text (principles for trustworthy secure design)
  5. NIST SP 800-160 Vol. 2 Rev. 1 — full text (cyber resiliency goals, objectives and 14 techniques)
  6. NIST SP 800-218: Secure Software Development Framework (SSDF) Version 1.1
  7. NIST: NISTIR 8259, Foundational Cybersecurity Activities for IoT Device Manufacturers
  8. ETSI EN 303 645 V3.1.3: Cyber Security for Consumer Internet of Things — Baseline Requirements
Was this guide helpful?

In this cluster