Join our Newsletter — 33% off our NHI Course
Home› Guides› NIST IR 8259 IoT Device Cybersecurity Baseline Guide:…
Guide OT & IoT Security

NIST IR 8259 IoT Device Cybersecurity Baseline Guide: Rev. 1 Activities, Core Baselines and Federal Use

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 12 min read
On this page

Most connected devices are bought on features and price, and the buyer finds out afterwards that the device cannot be uniquely identified, cannot be updated safely and cannot be configured securely. NIST's IR 8259 family is the US reference answer: a set of manufacturer activities plus two core baselines that say which technical and non-technical capabilities an IoT product should offer. The family underpins the consumer profile behind the US Cyber Trust Mark and the federal IoT requirements in SP 800-213. This guide explains the current documents, including IR 8259 Rev. 1 published in April 2026, the six device capabilities and four supporting capabilities, how federal buyers apply them, and how manufacturers can produce evidence. It is for product security teams, IoT architects and procurement and security teams in organisations that buy connected devices at scale.

Key takeaways

  • IR 8259 Rev. 1 replaced the 2020 original. NIST withdrew IR 8259 on 20 April 2026 and published Rev. 1, "Foundational Cybersecurity Activities for IoT Product Manufacturers", the same day. IR 8259A and 8259B remain the core baselines.
  • The scope is now the whole product. Rev. 1 defines an IoT product as the device plus other components such as backends, companion apps and gateways, so capabilities can be delivered by any of them.
  • Six technical and four non-technical capabilities. 8259A covers device identification, configuration, data protection, logical access to interfaces, software update and cybersecurity state awareness; 8259B covers documentation, information and query reception, information dissemination, and education and awareness.
  • Baselines are starting points, not certifications. NIST publishes no test scheme; profiles such as IR 8425 (consumer) and SP 800-213 (federal) tailor the baselines to a context.
  • Identity is the first capability for a reason. Unique logical and physical identifiers, restricted interface access and authenticated updates are what let an organisation manage devices as non-human identities rather than anonymous endpoints.

What it is and who it applies to

The IR 8259 family is NIST guidance, not regulation. It is voluntary for manufacturers, but it becomes binding indirectly when a buyer or a labelling programme adopts it. The documents, as listed on the NIST CSRC site on 27 October 2026:

DocumentTitleStatus and datePrimary audience
IR 8259 Rev. 1Foundational Cybersecurity Activities for IoT Product ManufacturersFinal, 20 April 2026 (drafts May and September 2025); supersedes IR 8259 (May 2020), now withdrawnManufacturers
IR 8259AIoT Device Cybersecurity Capability Core BaselineFinal, May 2020Manufacturers, integrators, buyers
IR 8259BIoT Non-Technical Supporting Capability Core BaselineFinal, August 2021Manufacturers and supporting third parties
SP 800-213IoT Device Cybersecurity Guidance for the Federal Government: Establishing IoT Device Cybersecurity RequirementsFinal, November 2021Federal agencies and their system owners
SP 800-213AIoT Device Cybersecurity Requirement CatalogFinal, November 2021Federal agencies; also usable by any buyer
IR 8425Profile of the IoT Core Baseline for Consumer IoT ProductsFinal, September 2022Consumer product makers; basis of the US Cyber Trust Mark

Federal agencies use SP 800-213 and its catalog to set device requirements in acquisitions; SP 800-213 is tagged on the NIST site to the IoT Cybersecurity Improvement Act of 2020, which directs federal IoT security standards and restricts agency procurement of non-compliant devices. Consumer products use IR 8425 through the label covered in the US Cyber Trust Mark Guide. Enterprises outside government use 8259A and 8259B as a vendor questionnaire and contract annex.

Structure and key requirements

IR 8259 Rev. 1: nine manufacturer activities

PhaseActivityPractical output
Pre-market0. Prioritize cybersecurity and maintain cybersecurity postureManufacturer's own systems, development process and supply chain secured; ability to respond and recover assessed
Pre-market1. Identify expected customers and define expected use casesWho buys and uses the product, how, where and for how long
Pre-market2. Research customer cybersecurity needs and goalsRisk-based analysis, applicable regulations and standards, customer research
Pre-market3. Determine appropriate means to support customer needs and goals in the context of the IoT productDecision on which component (device, app, backend, customer) delivers each need, within product constraints
Pre-market4. Define IoT product cybersecurity capabilities based on appropriate meansCapability list with required robustness
Pre-market5. Plan for adequate support of customer needs and goalsHardware, software and procedures planned to deliver the capabilities
Post-market6. On-going support of product cybersecurity throughout the lifecycle and through end-of-lifeVulnerability remediation and support until end of life
Post-market7. Define approaches for communicating to customersChannels and methods for security information
Post-market8. Decide what to communicate to customers and how to communicate itContent of routine notices and required disclosures

Activity 0 is new in Rev. 1 and makes the manufacturer's own security a prerequisite. The revision also mentions the EU Cyber Resilience Act and Singapore's Cybersecurity Labelling Scheme, which signals the intended alignment with other regimes.

IR 8259A: six device cybersecurity capabilities

CapabilityCore elements (paraphrased from 8259A)Typical buyer test
Device IdentificationUnique logical identifier; unique physical identifier accessible to authorised entitiesCan each unit be told apart in the management platform and on the label?
Device ConfigurationChange configuration settings; restrict changes to authorised entities; restore a secure configurationIs there a documented secure default and a reset to it?
Data ProtectionSecure cryptographic modules with standard algorithms for stored and transmitted data; ability to make all data inaccessible; configurable cryptographyIs traffic encrypted to the backend, and can the device be wiped at disposal?
Logical Access to InterfacesDisable unnecessary local and network interfaces; restrict access to each network interface; lockout or delay after failed attemptsCan Telnet, debug ports and unused services be turned off?
Software UpdateRemote or local update; verify and authenticate updates before install; roll back; restrict updating to authorised entities; enable or disable updates; configure how updates start and notifyAre updates signed and verified on device, and can the owner control timing?
Cybersecurity State AwarenessReport the device's cybersecurity state; distinguish normal from degraded state; restrict and protect the state information; make it available to other servicesDoes the device send logs or health status to a collector?

IR 8259B: four non-technical supporting capabilities

  • Documentation: development assumptions (customers, use cases, data, applicable laws, support lifespan), capability descriptions and configuration, secure development and supply chain practices, and maintenance requirements.
  • Information and Query Reception: channels to receive maintenance and vulnerability reports, such as bug reporting and bug bounty programmes, and answers to customer security questions.
  • Information Dissemination: notices on updates, end of support, vulnerabilities and fixes, and breaches with remediation steps.
  • Education and Awareness: guidance on identifiers, configuration, access control and updates; secure reprovisioning and disposal; shared responsibilities; dependencies on connectivity and third-party services.

Identity and NHI requirements

Every connected device is a non-human identity: it holds credentials, talks to a backend and often acts on behalf of a user. The baselines translate into identity requirements as follows:

  • Unique identity per unit: Device Identification requires a unique logical identifier. In practice this means a per-device certificate or key provisioned at manufacture, not a shared credential baked into the firmware. See the Device and IoT Identity Guide.
  • No shared or hard-coded admin logins: Logical Access to Interfaces requires access to be restricted to authorised entities. A shared, unchangeable credential defeats this. The HPE Aruba Instant On hard-coded credentials case (CVE-2025-37103, firmware 3.2.0.1 and earlier) is exactly this failure: every device shared the same admin login, which the owner could not change.
  • Authenticated updates: Software Update requires updates to be verified and authenticated before installation and restricted to authorised entities, which makes the signing key and the update service privileged non-human identities in their own right.
  • Backend and app identities: because Rev. 1 treats the product as device plus backend and companion app, API keys, OAuth clients and cloud service accounts used by the product are in scope. See the Identity for IoT Fleets Guide.
  • Lifecycle: Data Protection's ability to make data inaccessible, and 8259B's reprovisioning and disposal guidance, cover credential revocation at transfer or end of life.

Implementation steps

For manufacturers

  1. Run Activities 0 to 2 as a documented product security context: customers, use cases, support lifespan and applicable regimes (federal buyers, Cyber Trust Mark, EU CRA, ETSI EN 303 645).
  2. Map each 8259A and 8259B element to a component: device, gateway, app, backend or customer (Activity 3). Record gaps.
  3. Fix identity and update first: per-device credentials, interface lockdown and signed updates usually need hardware or bootloader changes and have the longest lead time.
  4. Publish the non-technical deliverables: security documentation, a vulnerability reporting channel, a declared support period and an advisory process.
  5. Test before claiming: verify each capability on a production build, including rollback and factory reset to a secure state.

For buyers (federal or enterprise)

  1. Follow SP 800-213: understand how the device fits the system and its risk, then select requirements from the SP 800-213A catalog.
  2. Put the selected capabilities into the tender as mandatory or scored items, with evidence requested per item.
  3. Pilot: test a small batch in a lab segment: identifier, interface lockdown, update verification and log export. Reject or apply compensating controls for failures, and record them as risk exceptions.
  4. Roll out with inventory: enrol each device into asset inventory and identity management at deployment, and plan replacement before the declared end of support.

Small versus large organisations: a small business can use IR 8425 or the Cyber Trust Mark as a shortcut when buying consumer-grade products. A large enterprise or agency buying thousands of devices should build a tailored profile from SP 800-213A and test samples, because consumer profiles assume a home network, not a managed estate.

Evidence and assessment

NIST does not certify against IR 8259. Evidence therefore depends on who is asking:

Evidence routeWhat it showsLimits
Manufacturer self-attestation mapped to 8259A and 8259BClaimed capability per element, with configuration guidanceUnverified; ask for test evidence
Buyer lab testingCapabilities work in your environmentCostly; sample based
US Cyber Trust Mark (IR 8425 based)Independent testing by an accredited lab for consumer productsConsumer wireless products only; programme still settling
Other schemes such as ETSI EN 303 645 assessmentsThird-party test against a related baselineMap provisions to 8259A elements yourself

Measures that show the baseline is working in an estate:

  • Percentage of IoT devices in inventory with a unique identifier bound to an owner.
  • Percentage of devices with default credentials changed or none present.
  • Percentage of devices on a supported firmware version, and median days from vendor release to deployment.
  • Percentage of device models whose update signature verification has been tested.
  • Percentage of devices sending state or logs to a collector, and devices past declared end of support.

Monitoring should look for new devices without an inventory record, logins to device management interfaces from unexpected sources, and failed update verification events. See the IoT Security Guide.

Mapping to other frameworks

8259A or 8259B capabilityNIST SP 800-53 Rev. 5NIST CSF 2.0
Device IdentificationIA-3 Device Identification and Authentication; CM-8 System Component InventoryPR.AA-01
Device ConfigurationCM-6 Configuration SettingsPR.PS-01
Data ProtectionSC-8, SC-13, SC-28; MP-6 Media SanitizationPR.DS-01; PR.DS-02
Logical Access to InterfacesAC-3 Access Enforcement; AC-7 Unsuccessful Logon Attempts; CM-7 Least FunctionalityPR.AA-01
Software UpdateSI-2 Flaw Remediation; SI-7 Software, Firmware, and Information IntegrityPR.PS-02
Cybersecurity State AwarenessAU-2 Event Logging; SI-4 System MonitoringDE.CM-09
Documentation; Information Dissemination (support period)SA-4 Acquisition Process; SA-22 Unsupported System ComponentsID.AM-08; GV.SC-06
Information and Query ReceptionSR-5 Acquisition Strategies, Tools, and MethodsGV.SC-07

SP 800-213A itself cross-references each catalog capability to SP 800-53 controls, so federal teams should use its mapping as the authoritative one. Outside the US, the baselines line up with ETSI EN 303 645 and the EU CRA essential requirements: see the ETSI EN 303 645 Consumer IoT Guide and the EU Cyber Resilience Act Guide. Federal vulnerability disclosure handling is covered separately in NIST SP 800-216.

Common pitfalls

  • Citing the withdrawn 2020 IR 8259: contracts and questionnaires written before April 2026 should be updated to Rev. 1 and its nine activities.
  • Treating the baseline as a pass mark: 8259A is a minimum starting point; a camera in a high-risk site needs more than the core baseline.
  • Checking the device and ignoring the backend: the product includes the cloud service and app. A secure device behind a backend with shared API keys is not a secure product.
  • Accepting "supports updates" as an answer: ask whether updates are signed, verified on device, can be rolled back and can be controlled by the owner.
  • No support period: buyers that do not require a declared end-of-support date end up with unpatchable devices with no replacement budget.
  • Inventory without identity: listing IP addresses is not identification; without a unique identifier bound to an owner, devices cannot be revoked or tracked across networks.

Practitioner checklist

  • Update policy, questionnaires and contracts to cite IR 8259 Rev. 1, IR 8259A and IR 8259B.
  • Build a device profile from SP 800-213A for each major device class you buy.
  • Require unique per-device identifiers and no shared or hard-coded credentials.
  • Require signed, verified updates with owner control and a declared support period.
  • Test interface lockdown, factory reset and update verification on sample units before rollout.
  • Enrol every device in inventory with an owner at deployment, and track end-of-support dates.
  • Collect device state or logs centrally and alert on unknown devices and failed updates.
  • For products you make, run Activities 0 to 8 and publish the 8259B documentation set.

Standards and references

Related NHI Mgmt Group resources: US Cyber Trust Mark Guide · IoT Security Guide · Device and IoT Identity Guide · ETSI EN 303 645 Consumer IoT Guide · IoT Security Buyer's Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.