Key takeaways
- SP 800-82 Rev. 3 is free, practical and written for OT. It is the best single starting reference for a plant team with no OT security background.
- It covers OT architectures, program development, risk management, defense-in-depth architecture and how to apply the CSF to OT.
- Appendix F is an OT overlay of NIST SP 800-53 Rev. 5 controls, with low, moderate and high baselines and OT-specific tailoring notes.
- Use it as a reference library, not a compliance checklist. Pair it with IEC 62443 for zone design and supplier requirements.
- NIST released an initial public draft of Rev. 4 on September 21, 2026, restructured around CSF 2.0. Rev. 3 remains the final version until Rev. 4 is published.
If your controls engineer asks "where do I start reading about OT security?", the honest answer is NIST SP 800-82. It is free, it is written for people who run industrial systems, and it explains why OT security is different from IT security without assuming you already know. This page covers what is in Rev. 3, how the OT overlay works and how a mid-market plant can use it without turning it into a 300-page compliance exercise.
What it is
NIST Special Publication 800-82 Revision 3, Guide to Operational Technology (OT) Security, was published on September 28, 2023. It replaced Rev. 2 from 2015, which was titled around industrial control systems. The new title reflects a wider scope: NIST describes OT as programmable systems and devices that interact with the physical environment, including industrial control systems, building automation, transportation systems, physical access control and environmental monitoring and measurement systems.
The guide explains how to secure OT while respecting its performance, reliability and safety requirements. It gives an overview of OT and typical topologies, identifies common threats and vulnerabilities, and recommends countermeasures.
Note: NIST released the initial public draft of Rev. 4 on September 21, 2026, with comments due November 30, 2026. As of November 2026, Rev. 3 is still the final version. See the section on Rev. 4 below.
What is inside Rev. 3
| Part | What you get | Who should read it |
|---|---|---|
| OT overview | How SCADA, DCS and PLC-based systems are built; safety systems; IIoT; how OT and IT security differ | Anyone new to OT, including IT staff |
| Program development | Building a business case, charter, cross-functional team, policies, training, incident response and recovery | Plant manager, CISO |
| Risk management | Framing, assessing, responding to and monitoring OT risk; supply chain and safety systems; applying the NIST Risk Management Framework | CISO, risk owner |
| Cybersecurity architecture | Defense-in-depth layers, network segmentation, architecture models for DCS, PLC with IIoT, and SCADA | OT engineers, network team |
| Applying the CSF to OT | Identify, Protect, Detect, Respond, Recover in an OT context | CISO, OT lead |
| Appendices | Threat sources and incidents, OT security organizations, capabilities and tools, the OT overlay | Reference |
Rev. 3 uses the five functions of CSF 1.1. CSF 2.0, published in February 2024, added Govern. If you have adopted NIST CSF 2.0, map the program development and risk management chapters to Govern yourself.
The OT overlay (Appendix F)
The overlay is the part most people have heard of and fewest have used properly.
NIST SP 800-53 Rev. 5 is a large catalog of security and privacy controls written mainly for federal information systems. Appendix F of SP 800-82 Rev. 3 tailors that catalog for OT. For each relevant control, it gives:
- whether the control applies to OT at all,
- which baseline it belongs to (low, moderate or high impact),
- OT-specific supplemental guidance, for example where a control cannot be run on a legacy controller and a compensating measure is needed.
The overlay covers control families from Access Control through Supply Chain Risk Management.
How a manufacturer should use it: pick the baseline that matches the consequence of compromise for a zone (a packaging line versus a reactor with a SIS), then read the OT tailoring notes. Use them to check your own controls and integrator designs. Do not try to implement every control in the high baseline across every plant.
Plant-floor reality: Many 800-53 controls assume you can install agents, enforce password complexity or patch monthly. Half your PLCs and HMIs cannot do that. The overlay's value is that it tells you when that is expected and what to do instead: compensate at the network, the conduit or the procedure.
How a plant uses SP 800-82 in practice
A mid-market plant does not "implement" SP 800-82 end to end. It uses it in four ways.
1. As a shared reference for IT and OT
Give the OT overview chapter to every IT person who will touch the plant network. It explains why you cannot reboot an HMI during a batch, why availability and safety come first, and why scanning a controller network can stop a line. It saves a lot of arguments.
2. As an architecture checklist
The defense-in-depth chapter describes layers from security management through physical security, network security, hardware security and software security. Use it to review your current design:
Enterprise network (Level 4-5)
|
[ firewall ] ---- OT DMZ (historian mirror, patch server,
| remote access jump host)
[ firewall ]
|
Supervisory (Level 2-3): SCADA, HMI, engineering WS
|
Control (Level 1): PLCs, drives, safety controllers
|
Process (Level 0): sensors, actuators
Check: is there a DMZ? Does remote access terminate there? Can a laptop on the office Wi-Fi reach a PLC? The zones and conduits guide turns these questions into a design.
3. As the source for your OT risk method
The risk management chapter adapts the NIST framing-assessing-responding-monitoring cycle for OT and calls out safety systems and the supply chain. If you have no OT risk method today, borrow this one, or combine it with the zone-based approach from IEC 62443-3-2.
4. As an evidence base for regulators and customers
EU manufacturers in NIS2 scope need risk-management measures that reflect the state of the art. Pointing to a recognized, free and current NIST guide helps show your measures are reasonable. US manufacturers in defense or federal supply chains will see SP 800-53 language in contracts, and the overlay is the bridge.
SP 800-82 next to other frameworks
| Framework | Role for a manufacturer |
|---|---|
| NIST SP 800-82 | Free explanatory guide; OT overlay of 800-53 controls |
| NIST CSF 2.0 | Top-level structure and board reporting |
| IEC 62443 | Zones and conduits, security levels, integrator and product requirements |
| ISO/IEC 27001 | Certifiable management system umbrella |
| NIS2, CRA | EU legal duties |
The framework crosswalk workbook maps these against each other so one control can satisfy several references.
What changes in Rev. 4 (draft)
NIST released the initial public draft of SP 800-82 Rev. 4 on September 21, 2026, with comments due November 30, 2026. According to NIST's announcement, the draft:
- is restructured around CSF 2.0, with the former risk management material reorganized under the Govern function,
- widens sector coverage in the introduction, including food and agriculture, building automation and Industrial IoT with cloud convergence,
- expands guidance on how OT risk fits into enterprise risk management,
- discusses adopting the Risk Management Framework in Appendix F,
- adds guidance on asset management, network monitoring and detection, protecting system management functions and applying zero trust principles.
Drafts change. Keep using Rev. 3 for decisions and contracts until Rev. 4 is final, and check the NIST CSRC page before citing either.
How AI and analytics fit
Rev. 3 already covers IIoT and the convergence of OT with cloud services in its architecture models. The same principles apply to AI use cases such as predictive maintenance or vision inspection:
- Data leaves the control network through the DMZ, not around it.
- The edge device or gateway is an OT asset. Put it in the inventory and patch plan.
- Write-back from an AI model to setpoints is a control function and needs the same rigor as an engineering workstation.
See securing AI in OT networks for reference designs.
Effort and cost
- Reading: the OT overview and architecture chapters are a few days of focused reading for an engineer. Budget it as training time.
- Architecture review against the guide: 1 to 2 weeks per site for a controls engineer and a network engineer together.
- Overlay gap check: worthwhile only for high-consequence zones at first. Expect several days per zone.
- Cost: the document is free. The spend comes from what the review finds: firewalls, a DMZ, remote access tooling, monitoring.
Common mistakes
- Treating the overlay as a mandatory control list and drowning a small team in 800-53 controls.
- Handing the guide to IT and assuming they will apply it to the plant without engineering input.
- Skipping the asset inventory. Every chapter assumes you know what you have. Start with the OT asset inventory.
- Waiting for Rev. 4 instead of acting on Rev. 3.
- Forgetting safety systems. The guide treats SIS as a special case. So should you.
Where to start: Monday-morning checklist
- Download Rev. 3 from NIST CSRC. Share the OT overview chapter with IT and engineering.
- Sketch your current architecture against the defense-in-depth layers.
- List every path into Level 1 and Level 2. Mark which go through a DMZ.
- Pick your highest-consequence zone and read the overlay guidance for access control and remote access.
- Note the Rev. 4 comment deadline and decide whether to comment through your industry association.
- Run the OT security maturity assessment to rank sites.
NIST guidance is voluntary for private companies. If you rely on it to meet a legal duty, confirm the approach with counsel.
Sources and further reading
- NIST SP 800-82 Rev. 3, Guide to Operational Technology (OT) Security (NIST CSRC)
- NIST SP 800-82r3 full text (PDF)
- NIST requests comments on draft SP 800-82r4 (NIST, September 2026)
- NIST SP 800-82 Rev. 4 initial public draft (NIST CSRC)
This guide is general information for manufacturers, not legal advice. Confirm regulatory obligations with qualified counsel.
FAQ
Frequently asked questions
Is NIST SP 800-82 a standard I can be certified against?
No. SP 800-82 is guidance. There is no certification scheme for it. US federal agencies use the OT overlay as part of the NIST Risk Management Framework, but private manufacturers use the guide voluntarily. If you need a certificate, look at ISO/IEC 27001 for the management system or ISASecure for 62443 products and systems.
What is the difference between NIST SP 800-82 and IEC 62443?
SP 800-82 is a free, explanatory guide with an overlay of NIST SP 800-53 controls. IEC 62443 is a paid series of consensus standards with defined roles, zones and conduits, security levels and product requirements that suppliers can certify against. Many plants read SP 800-82 to understand the problem and use 62443 to specify requirements to integrators and OEMs.
Does SP 800-82 apply to manufacturers outside the US?
It is written by a US agency but is not tied to US law for private companies. The architectures, threats and countermeasures it describes apply to any plant with PLCs, SCADA or DCS. EU manufacturers often use it alongside IEC 62443 to support NIS2 risk-management measures, since it is free and readable.
Should I wait for SP 800-82 Rev. 4?
No. NIST released the Rev. 4 initial public draft on September 21, 2026 with comments due November 30, 2026. Drafts can change and the final date is not set. Use Rev. 3 now. The core architecture and defense-in-depth guidance will not become wrong, and moving later to a CSF 2.0 structure is a reorganization, not a restart.
Related guides
Frameworks
NIST CSF 2.0 for manufacturers: one language for IT, OT and the board
NIST Cybersecurity Framework (CSF) 2.0 is a voluntary, outcome-based framework that organizes cybersecurity into six functions: Govern, Identify, Protect, Detect, Respond and Recover.
Guide · 7 min read
Frameworks
IEC 62443 for mid-market manufacturers: a practical guide
ISA/IEC 62443 is the main international series for securing industrial automation and control systems.
Guide · 8 min read
OT Security
OT asset inventory: the foundation for OT security and AI governance
An OT asset inventory is a maintained list of every device, system and connection in your control environment, with the attributes you need to make security decisions.
Guide · 6 min read
OT Security
IEC 62443 zones and conduits: a walkthrough for a mid-size plant
Zones group assets that share security requirements; conduits are the controlled paths between them.
Guide · 8 min read