NIST 800-82 Rev. 4 draft: what an OT engineer should read first

On September 21, 2026, NIST published the initial public draft of SP 800-82 Rev. 4, the Guide to Operational Technology (OT) Security. Comments are open until November 30, 2026. That is the whole event. Nobody was breached, nothing was disclosed, and no ICS security incident sits behind it.

I'm writing about it anyway, because guidance documents are where the next incident gets decided, one budget meeting at a time. And I don't buy the usual line that a new revision means a new era.

What the publication page confirms

The draft is on the NIST publication page for Rev. 4, with a PDF and a comment template spreadsheet. The authors are from NIST and MITRE. The document history on that page has two entries, both labeled "Draft": one dated January 22, 2026 and one dated September 21, 2026. The page title and the comment-period text call the September document the "initial public draft". The page does not explain the January entry, and its link points to a different path than the September one, so I won't guess what it was.

The page does not say which document the draft supersedes. The Rev. 3 page does: Rev. 3 was published on September 28, 2023 and replaced Rev. 2 from June 3, 2015. That page now carries a planning note pointing at the new draft.

What the Rev. 4 page does not give you is an itemized comparison with Rev. 3, and neither page lists chapters. So this is not a section-by-section diff. It is the comparison the two pages support: their abstracts and NIST's own list of changes. Rev. 3 describes industrial control systems, building automation, transportation, physical access control, and environmental monitoring and measurement. The Rev. 4 abstract names building automation, freight rail, maritime vessels, water and wastewater, IIoT and cloud, and ties its countermeasures to NIST CSF 2.0. The loud version of a release like this is "a new era for OT security", and a chapter-by-chapter "what changed" published within days is a claim the pages above do not back. What is confirmed is wider scope and a CSF 2.0 framing. The rest I can't confirm from the pages, and I haven't diffed the two PDFs.

What NIST says changed

The page lists six things:

  1. More sectors in the introduction: building automation, water and wastewater, food and agriculture, freight rail, maritime vessels, and the convergence of IIoT and cloud with OT.
  2. A restructure around NIST CSF 2.0, with risk management reorganized under the Govern function.
  3. A longer discussion of tying OT risk management to enterprise risk management (NIST IR 8286r1).
  4. The Risk Management Framework, discussed in Appendix F.
  5. Expanded guidance on OT security controls, named explicitly as asset management and network monitoring and detection.
  6. Architecture guidance on protecting system management functions and applying zero trust.

What to read first

Not the sector list. If you run a plant, you already know which sector you are in.

Start with asset management and with monitoring and detection. In the Triconex rant on this site, one of the questions was "Did we start monitoring communications between PLCs and their controllers?" A guide that now names those two controls outright is at least pointing at the right gap, and that is the part you can act on without a project charter: a list of what is on the network, and a baseline of who talks to whom.

Next, the architecture material on protecting system management functions. Whoever can reach the engineering workstation or the remote access path can change the process, so a guide that says "protect the management functions" is pointing at the right door. I would rather read that than "segment the network" for the tenth time.

Appendix F and the Govern restructuring come last, and only if you own the paperwork. They matter for audits and funding.

Where it stops being useful

A draft is a draft. Section numbers can move before the final text, and the two history entries, January and September, are a reminder that this document has already been republished once. Do not cite section numbers in your internal policy yet.

NIST publishes a comment template and takes comments by email until November 30, 2026.

The guide will be read. The question, as with every one of these, is whether anyone takes the asset inventory off the shelf.