NIST opens the SP 800-82 Rev. 4 pre-draft process

What the source establishes

NIST published the pre-draft call on January 22, 2026. The comment period closed February 23, 2026. NIST says it intends to align the revision with current frameworks, standards, practices, and the evolving OT threat landscape. OT Defense Review records the named source, date, status, affected market layer, and evidence class separately so an announcement, authority record, or provider study is not silently converted into an independently verified operating conclusion.

The source establishes the revision process and questions only; Rev. 3 remains the final guide at the seed date. The maintained record distinguishes the fact of the publication or event from forward-looking statements, provider characterization, later implementation, and conditions that the source does not establish.

The industrial-defense consequence

Programs should inventory every policy, assessment, architecture standard, provider mapping, control library, training asset, contract, and audit artifact that references Rev. 3. They can prepare for change without inventing Rev. 4 requirements, dates, or mappings before a draft exists.

The practical review should follow the change into system boundaries, accountable roles, asset populations, architecture, data collection, access, detection, response, recovery, provider dependencies, retained evidence, and the operating constraints that could alter safety or reliability. That is where a headline becomes a defensible program decision.

What asset owners should test next

Ask providers and advisers how they distinguish current final guidance, pre-draft questions, draft text, final publication, local policy adoption, and historical evidence. Verify that a mapping is versioned and that earlier decisions retain the source governing them at the time.

The pre-draft notice does not establish the Rev. 4 text, publication date, final structure, or a transition requirement. Preserve which facts came from the authority or organization, which behaviors were independently observed under a disclosed method, which depend on configuration or services, and which remain not established. Do not use a public article as authorization to probe, scan, block, patch, isolate, or reconfigure a live industrial environment.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

OT Defense Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.