NIST published the initial public draft of SP 800-82 Revision 4, its guide to operational technology (OT) security, on 21 September 2026. Comments are due 30 November 2026, about two weeks from now. This briefing summarizes what NIST says has changed. It is based on NIST’s publication page and announcement; we have not read the full draft line by line, so check specifics against the document.
Status
- The draft is open for public comment until 30 November 2026. NIST’s page provides a comment template (spreadsheet) and a call for patent claims.
- Authors listed are Stouffer, Pease and Tang (NIST) and Hahn, Gilsinn, Rebori-Carretero, Alexander, Fialk and Silva (MITRE).
- Revision 3 (September 2023) remains the final edition in force until the revision is finalized. NIST’s Rev. 3 page lists it as published September 2023 (final, 09/28/23) and links to the Rev. 4 draft without showing supersession.
Reported changes
Wider scope. NIST describes expanded sector coverage, including building automation and control systems, water and wastewater, food and agriculture, freight rail and maritime vessels, plus guidance on the convergence of industrial IoT and cloud.
Cybersecurity Framework 2.0 structure. The document is reorganized around CSF 2.0, with risk management placed under the Govern function.
OT and enterprise risk alignment. The draft aligns OT risk with enterprise risk management, with reference to NIST IR 8286r1, and places the Risk Management Framework in Appendix F.
More operational guidance. NIST describes expanded material on asset management and on network monitoring and detection, and architecture guidance on protecting system-management functions and applying zero trust.
What asset owners should check
- Governance mapping. If your OT program is organized around Rev. 3, test how it maps to CSF 2.0’s Govern function and who owns OT risk in the enterprise register.
- Asset inventory. The expanded asset-management guidance is the easiest place to find gaps in your current inventory.
- Monitoring. Compare your passive network monitoring coverage with the draft’s expanded detection guidance.
- Management planes. Protecting engineering workstations, remote-access paths and other system-management functions is highlighted; this matches the recurring theme in current ICS advisories.
- Sector fit. If you operate rail, maritime or building systems, read the new sector material for realism.
Reading the draft efficiently
The document is long. A practical order: read the new sector sections that apply to you, then the asset-management and monitoring sections, then the architecture material on system-management functions, and only then the framework mapping. Note each gap as a candidate comment as you go, using NIST’s template so entries can be submitted as they are.
Why comment
Practitioner comments shape final text. Useful comments are specific: a paragraph reference, the problem, and a proposed change. NIST’s template is built for that.
Our assessment
This is a draft, not requirements; it does not create a compliance obligation by itself. Its practical value for most teams is as a benchmark for program reviews now, ahead of the final text.