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

Firmware vulnerabilities & fixes

NIST IoT device cybersecurity requirements: NISTIR 8259 and SP 800-213

Last updated:

NIST's IoT Cybersecurity Program finalized NISTIR 8259 Revision 1 in April 2026, broadening its scope from "IoT devices" to "IoT products" and formally superseding the original 2020 baseline — the headline change in a program that otherwise publishes two linked families of guidance under a congressional mandate: the NISTIR 8259 series, written for device manufacturers, and SP 800-213 / SP 800-213A, written for the federal agencies that buy IoT devices. Together they define what a "reasonably secure" connected device looks like for anyone selling into the US federal market. SP 800-213 Revision 1, by contrast, is still an open draft as of this writing, so a device maker reading only the 2020-2021 baseline risks missing where the ground is already shifting.

Key takeaways

  • The Internet of Things Cybersecurity Improvement Act of 2020 (Public Law 116-207, H.R.
  • Section 7 of the Act is the part with consequences for a device maker.
  • Source: NIST CSRC publication records, read 12 November 2026.
  • NIST IR 8425, the consumer profile, rephrases the same ten areas as outcomes for a whole product, so a manufacturer that maps evidence to 8259A/B once can reuse it.

Where does the mandate come from?

The Internet of Things Cybersecurity Improvement Act of 2020 (Public Law 116-207, H.R. 1668) was enacted 4 December 2020. Section 4 directed NIST to publish, within 90 days, "standards and guidelines for the Federal Government on the appropriate use and management by agencies of Internet of Things devices owned or controlled by an agency," including "minimum information security requirements for managing cybersecurity risks associated with such devices." Those guidelines had to stay consistent with NIST's work on secure development, identity management, patching and configuration management. Section 5 separately required NIST guidelines, within 180 days, on reporting and coordinating security vulnerabilities in federal information systems, including IoT devices; NIST answered with SP 800-216 in May 2023.

Section 4(b) then has the Director of OMB review agency security policies against NIST's guidelines and issue policies to make them consistent. Section 4(c)(1) builds in a standing review clock: NIST must revisit its standards and guidelines "not later than 5 years after" first publishing them "and not less frequently than once every 5 years thereafter" — the clause that is driving the 2025-2026 revision cycle described below. The NIST documents are not regulations, but the Act ties federal buying to them.

What happens if an agency's IoT device cannot meet NIST's guidelines?

Section 7 of the Act is the part with consequences for a device maker. Since 4 December 2022, two years after enactment, the head of an agency is "prohibited from procuring or obtaining, renewing a contract to procure or obtain, or using" an IoT device if the agency's Chief Information Officer, during a contract review, determines that using it "prevents compliance with" the section 4 standards or the section 5 disclosure guidelines. The prohibition also applies to contracts below the simplified acquisition threshold.

The agency head can waive it when the CIO determines that:

  • the waiver is necessary in the interest of national security;
  • the device is needed for research purposes; or
  • the device "is secured using alternative and effective methods appropriate to the function of such device."

OMB sets the waiver process, and GAO reports to Congress on waivers granted. For a manufacturer, the practical point is that a federal CIO will look for evidence against NIST's baseline and for a working vulnerability disclosure process; a product that cannot supply either depends on a waiver.

What is in the NISTIR 8259 series?

Document Title Status (CSRC, 12 November 2026)
NIST IR 8259 Rev. 1 Foundational Cybersecurity Activities for IoT Product Manufacturers Final, April 2026; supersedes the May 2020 original
NISTIR 8259A IoT Device Cybersecurity Capability Core Baseline Final, May 2020
NISTIR 8259B IoT Non-Technical Supporting Capability Core Baseline Final, August 2021
NISTIR 8259C Creating a Profile Using the IoT Core Baseline and Non-Technical Baseline Initial public draft, December 2020
NISTIR 8259D Profile Using the IoT Core Baseline and Non-Technical Baseline for the Federal Government Withdrawn 29 November 2021; content moved into an SP 800-213A appendix

Source: NIST CSRC publication records, read 12 November 2026.

NIST IR 8259 "describes recommended activities related to cybersecurity that manufacturers should consider performing before their IoT products are sold to customers" — the process. NISTIR 8259A supplies the technical content: it "defines an Internet of Things (IoT) device cybersecurity capability core baseline, which is a set of device capabilities generally needed to support common cybersecurity controls." NISTIR 8259B adds the non-technical side, the support a manufacturer gives around the device. NISTIR 8259C describes a profiling process that starts from the 8259A/B baselines and adds sector- or customer-specific requirements; the federal profile it was used for now lives in SP 800-213A.

Which capabilities do 8259A and 8259B list?

Six technical and four non-technical capabilities make up NIST's core baseline:

Baseline Capability What a buyer will look for
8259A Device identification A unique logical and physical identifier per unit
8259A Device configuration Authorized users can change settings; defaults can be restored
8259A Data protection Stored and transmitted data protected, for example with encryption
8259A Logical access to interfaces Local and network interfaces restricted to authorized users and processes
8259A Software update Firmware and software updatable through a secure, configurable mechanism
8259A Cybersecurity state awareness The device can report and log its own security state
8259B Documentation Security-relevant design, support and end-of-life information
8259B Information and query reception A way to receive security questions and vulnerability reports
8259B Information dissemination Notices of updates, vulnerabilities and support status
8259B Education and awareness Guidance customers need to use the security features

NIST IR 8425, the consumer profile, rephrases the same ten areas as outcomes for a whole product, so a manufacturer that maps evidence to 8259A/B once can reuse it.

What changed in NIST IR 8259 Revision 1?

The Act's five-year review clock lands in this period, and NIST's response is a visible scope change rather than a minor refresh. NIST IR 8259 Revision 1 went through an initial public draft (13 May 2025) and a second public draft (30 September 2025) before final publication in April 2026, when it superseded the 2020 original. NIST's announcement of the first draft called it "a pivotal change to addressing the full IoT product scope as well as broadening consideration of maintenance, support and end of life considerations for IoT products." The second draft split and added activities, expanded the emphasis on risk assessment and threat modelling, and made the links to other references explicit.

The 2020 text had six activities, four pre-market and two post-market. Revision 1 has nine, numbered 0 to 8, "six of the activities primarily impact decisions and actions performed by the manufacturer before a product is sent out for sale (pre-market), and the remaining three" after sale:

  1. Prioritize cybersecurity and maintain cybersecurity posture
  2. Identify expected customers and define expected use cases
  3. Research customer cybersecurity needs and goals
  4. Determine appropriate means to support customer needs and goals in the context of the IoT product
  5. Define IoT product cybersecurity capabilities based on appropriate means
  6. Plan for adequate support of customer needs and goals
  7. On-going support of product cybersecurity throughout the lifecycle and through end-of-life
  8. Define approaches for communicating to customers
  9. Decide what to communicate to customers and how to communicate it

Activity 8 lists what customers need to know, including support and lifespan expectations, software updates, product retirement options and product composition. On composition, it notes that a software bill of materials (SBOM) and hardware bill of materials (HBOM) "can be considered as a way to communicate this and similar information to customers consistently and effectively."

What do SP 800-213 and SP 800-213A add for federal buyers?

SP 800-213, "IoT Device Cybersecurity Guidance for the Federal Government," published November 2021, is addressed to the agency doing the buying, not the manufacturer. It "provides IoT-specific guidance for federal organizations in understanding and defining their IoT cybersecurity requirements" and "explains the role of IoT devices as elements of federal systems and provides guidance for addressing the unique risks such devices can present," framed inside the NIST Risk Management Framework (RMF) rather than as a standalone checklist. Its companion, SP 800-213A, "IoT Device Cybersecurity Requirements Catalog," is the reference table: it "provides a catalog of internet of things (IoT) device cybersecurity capabilities" and non-technical supporting capabilities, and "cross references the capabilities in the catalog to the cybersecurity controls in NIST SP 800-53," including an IoT profile built on the SP 800-53B low baseline. In practice, an agency uses SP 800-213 to reason about risk and 800-213A as the lookup table of concrete capabilities to put in a solicitation or system security plan. For the controls themselves, see the SP 800-53 guide.

Is SP 800-213 Revision 1 final?

No. NIST released the initial public draft, retitled "IoT Product Cybersecurity Guidelines for the Federal Government," on 24 June 2026, with public comments accepted through 24 August 2026. The draft states that "an IoT product is a system element," extending the earlier device-centric guidance to treat IoT products — hardware, embedded software and any inseparable cloud/mobile-app components — as a single unit for risk assessment, and gives "general considerations of how IoT products may impact an information system's risk assessment and subsequent allocation of controls." As of this guide's update date, CSRC lists no final version; SP 800-213 (2021) remains the current version, and a manufacturer or integrator should track NIST's SP 800-213 series page before assuming the product-scoped revision applies.

How do NIST IR 8425 and the Cyber Trust Mark fit in?

NIST IR 8425 (September 2022) is the consumer profile of the same core baseline, written for "IoT products for home or personal use" and phrased as outcomes "intended to apply to the entire IoT product." The FCC adopted it as the technical basis of its voluntary U.S. Cyber Trust Mark. NIST IR 8425A (September 2024) adds requirements for consumer-grade routers. A device maker selling both to households and to agencies therefore works from one family: 8259A/B for the baseline, 8425 for the consumer label, and SP 800-213A for the federal catalog.

How does NIST's IoT guidance fit with other device obligations?

NIST's IoT guidance is US federal-procurement-focused and non-regulatory; it sits alongside, not instead of, other device obligations. A connected product sold into several markets will typically need the Cyber Resilience Act's Annex I requirements and vulnerability-handling duties, firmware SBOM evidence, a working PSIRT for coordinated disclosure, ETSI EN 303 645 for the UK and EU consumer market, and the password floor in California's SB-327. Treat NISTIR 8259A and SP 800-213A as one more capability checklist to satisfy with the same underlying engineering evidence, not a separate compliance track.

Worked example: what evidence does a federal buyer ask for?

Synthetic example for illustration, not a customer product. A maker of a PoE building-access controller bids on a federal facilities contract. The agency's security team maps the controller to SP 800-213A and asks for:

  1. Device identification:proof that each unit carries a unique serial and a unique device certificate.
  2. Logical access to interfaces:a port and service list, with Telnet removed and SSH disabled by default.
  3. Software update:how firmware images are signed and verified, and how an administrator schedules updates. See the OTA update security guide.
  4. Cybersecurity state awareness:which security events go to syslog, and in what format.
  5. Information and query reception and dissemination (8259B):a vulnerability disclosure policy consistent with SP 800-216, an advisory feed, and the published end-of-support date.
  6. Documentation:an SBOM for the shipped firmware with known vulnerabilities triaged.

The maker answers items 1–4 with design documents and test results, and items 5–6 with its PSIRT process and SBOM. If any item is missing, the CIO either rejects the device under section 7 or records a waiver.

SoftWSP covers part of that evidence: it normalises a device's SBOM into components and matches each one against NVD, CISA KEV, EPSS and vendor CSAF advisories, with AI drafting the triage summary for an engineer to review. It does not test whether a device implements the 8259A capabilities; that stays with the manufacturer's design and test records. See device firmware security.

This guide summarises public NIST and US federal legislative documents; it does not constitute legal or compliance advice.

Put this guide to work

Frequently asked questions

What law requires NIST's IoT device cybersecurity guidance?

The Internet of Things Cybersecurity Improvement Act of 2020 (Public Law 116-207, H.R. 1668), enacted 4 December 2020. Section 4 directed the NIST Director to "develop and publish... standards and guidelines for the Federal Government on the appropriate use and management by agencies of Internet of Things devices owned or controlled by an agency" within 90 days, covering secure development, identity management, patching and configuration management. Section 4(c)(1) also requires NIST to review and revise those standards "not later than 5 years" after publication and "not less frequently than once every 5 years thereafter." Section 5 separately required guidelines on coordinated vulnerability disclosure for federal IoT systems.

What is NISTIR 8259 and how is it different from NISTIR 8259A?

NISTIR 8259, "Foundational Cybersecurity Activities for IoT Device Manufacturers" (originally published 29 May 2020), recommends pre-market and post-market cybersecurity activities manufacturers should perform before selling IoT devices. NISTIR 8259A, "IoT Device Cybersecurity Capability Core Baseline" (also 29 May 2020), is the companion document that defines the actual technical baseline: "a set of technical device abilities generally needed to support common cybersecurity controls." 8259 describes the process; 8259A defines the minimum technical capabilities that process should produce.

What do NISTIR 8259B, 8259C and 8259D add?

NISTIR 8259B defines a non-technical supporting capability core baseline, "a set of non-technical supporting capabilities generally needed from manufacturers" (documentation, patch notification, end-of-life disclosure, and similar). NISTIR 8259C describes a profiling process, usable by any organization, that starts from the 8259A/8259B core baselines and explains how to tailor them with organization- or application-specific requirements. NISTIR 8259D was a draft worked example of applying that 8259C process to the federal government customer space; NIST withdrew it on 29 November 2021 and moved its content into an appendix of SP 800-213A, where FISMA and the SP 800-53 control catalog apply.

What do SP 800-213 and SP 800-213A add on top of the NISTIR 8259 series?

SP 800-213, "IoT Device Cybersecurity Guidance for the Federal Government" (published 29 November 2021), is written for the acquiring federal agency rather than the manufacturer: it explains how to evaluate an IoT device's integration into a federal information system and define device cybersecurity requirements, "the abilities and actions an organization will expect from an IoT device and its manufacturer and/or third parties." SP 800-213A is the companion "IoT Device Cybersecurity Requirements Catalog," a catalog of technical and non-technical capabilities cross-referenced to NIST SP 800-53 controls, including a profile built on the SP 800-53B RMF low-impact baseline.

What changed in NIST's 2026 update, and has it fully replaced the 2020-2021 documents?

Only partially, as of this guide's publication. NIST IR 8259 Revision 1 went through two public drafts (an initial public draft dated 13 May 2025 and a second public draft from 30 September 2025) before being finalized in April 2026, when it formally superseded and withdrew the original 2020 NISTIR 8259. The Rev. 1 title and text broaden scope from "IoT devices" to "IoT products" and add maintenance, support and end-of-life considerations the Act's five-year review mandate was meant to surface. SP 800-213 itself is mid-revision: NIST released SP 800-213 Revision 1 as an initial public draft, "IoT Product Cybersecurity Guidelines for the Federal Government," on 24 June 2026 with a comment period that closed 24 August 2026; as of this writing it remains a draft, so the final 2021 SP 800-213 is still the current, binding-for-planning-purposes version. Device makers and federal buyers should track NIST's SP 800-213 series page directly rather than assume Revision 1 is final.

Sources

  1. Public Law 116-207, Internet of Things Cybersecurity Improvement Act of 2020, govinfo.gov
  2. NIST: IoT Device Cybersecurity Requirement Catalogs — background
  3. NIST: SP 800-213 Series page
  4. NIST CSRC: NISTIR 8259 (Foundational Cybersecurity Activities for IoT Device Manufacturers)
  5. NIST CSRC: NISTIR 8259A (IoT Device Cybersecurity Capability Core Baseline)
  6. NIST CSRC: SP 800-213 (IoT Device Cybersecurity Guidance for the Federal Government)
  7. NIST CSRC: SP 800-213A (IoT Device Cybersecurity Requirements Catalog)
  8. NIST CSRC: SP 800-213 Revision 1 initial public draft
  9. NIST CSRC: NIST IR 8259 Revision 1 (final, April 2026)
  10. NIST IR 8259r1 PDF: Foundational Cybersecurity Activities for IoT Product Manufacturers (April 2026)
  11. NIST CSRC: NIST IR 8259 Revision 1 initial public draft (13 May 2025)
  12. NIST CSRC: NISTIR 8259B (IoT Non-Technical Supporting Capability Core Baseline)
  13. NIST CSRC: NISTIR 8259D (withdrawn; content moved to SP 800-213A)
  14. NIST CSRC: NIST IR 8425 (Profile of the IoT Core Baseline for Consumer IoT Products)
  15. NIST CSRC: SP 800-216 (Recommendations for Federal Vulnerability Disclosure Guidelines)
  16. NIST CSRC news: NIST Releases SP 800-213r1 ipd
Was this guide helpful?

In this cluster

NIST IoT device cybersecurity requirements: NISTIR 8259 and SP 800-213