NIST SP 800-82 Rev. 3: A Practical Overview
What NIST SP 800-82 Rev. 3 covers section by section, how its OT overlay tailors SP 800-53, and how to use it with the Rev. 4 draft now out for comment.
NIST Special Publication 800-82 is the most widely cited free reference on operational technology security. Revision 3, titled Guide to Operational Technology (OT) Security, was published in September 2023 and replaced the older Guide to Industrial Control Systems (ICS) Security. The new title reflects a wider scope: it covers not only ICS such as SCADA, DCS and PLC-based systems, but also building automation, physical access control, transportation and other systems that monitor or control physical processes.
The document is over 300 pages, and most people only need parts of it. This overview walks through its structure, highlights the sections that are directly actionable, and explains where Revision 4 fits.
Status in November 2026: Rev. 3 is final, Rev. 4 is a draft
NIST released an initial public draft of SP 800-82 Revision 4 in September 2026, with public comments accepted until November 30, 2026. The draft reportedly expands coverage of OT sectors, asset management and network monitoring, aligns with Cybersecurity Framework (CSF) 2.0 and brings in zero trust principles. Until NIST finalizes Rev. 4, Rev. 3 remains the current final edition, and it is the version auditors, contracts and internal policies should cite.
Practical advice: build your program on Rev. 3, read the Rev. 4 draft to see where things are heading, and submit comments if your organization has operational experience that the draft misses. Most of what follows will carry over, since the underlying engineering advice has not changed.
Who should read which part
| You are | Start with |
|---|---|
| CISO or program owner new to OT | Sections 2 and 3 |
| Risk or compliance lead | Section 4 and Appendix F |
| Network or security architect | Section 5 and Appendix E |
| SOC, IR or operations lead | Section 6 (Detect, Respond, Recover) and Appendix C |
Section 2: OT overview
Section 2 explains how OT systems are built: SCADA, distributed control systems, PLC-based topologies, building automation, physical access control, safety systems and the industrial internet of things. If you come from IT, read section 2.4, Comparing OT and IT System Security. It lists the differences that should shape every control decision: timeliness and performance requirements, availability requirements, risk management focused on safety, physical effects, different operating skills, resource constraints, communications, change management, managed support, component lifetime and component location.
One sentence in that section is worth copying into your policy: any security measure that impairs safety is unacceptable. We expand on these differences in OT vs IT security.
Section 3: building an OT cybersecurity program
Section 3 is the management chapter. It covers:
- establishing a charter and a business case for the program, and presenting it to leadership,
- governance with a cross-functional team (operations, engineering, IT, safety, physical security, procurement),
- OT-specific policies and procedures,
- awareness training adapted to plant personnel,
- a risk management framework,
- a maintenance tracking capability,
- incident response, and recovery and restoration capabilities.
The cross-functional team is the part most programs get wrong. NIST is explicit that OT security cannot be run by IT alone: control engineers own the process knowledge and the maintenance windows. The incident response and recovery items connect directly to OT incident response.
Section 4: risk management for OT
Section 4 applies NIST's risk management concepts (framing, assessing, responding to and monitoring risk) to OT, then walks through the seven steps of the Risk Management Framework: Prepare, Categorize, Select, Implement, Assess, Authorize and Monitor. Two special areas get their own subsections: supply chain risk management and safety systems.
Even if you never run a formal RMF authorization, the Categorize and Select steps are useful. Categorize forces you to state the impact of losing each system, and Select ties that impact to a baseline of controls, which leads to Appendix F.
Section 5: OT cybersecurity architecture
This is the most technical chapter and the one architects should read in full. It describes a defense-in-depth strategy with five layers of capabilities:
- Security management: program, policies, roles, risk and asset management.
- Physical security: access to sites, cabinets, control rooms and field equipment.
- Network security: architecture, segmentation and isolation, centralized logging, network monitoring, zero trust considerations.
- Hardware security: device trust, firmware, secure boot, physical ports.
- Software security: application security, patching, configuration management.
The network guidance is concrete. NIST recommends grouping assets into levels, tiers or zones, mapping required data flows, and configuring firewalls or unidirectional gateways so that only those flows are allowed. It also states that firewall rules should only permit connections between adjacent levels, so a Purdue Level 4 system should never talk directly to Level 2, 1 or 0, and that outbound rules from the control network deserve the same rigor as inbound ones. That guidance is the basis of our OT network segmentation and industrial DMZ guide, and the level vocabulary comes from the Purdue model.
Section 5 also covers cyber-related safety considerations, availability, geographically distributed systems, regulatory requirements, field I/O (Purdue Level 0) security and IIoT, then ends with example reference architectures for DCS, DCS and PLC with IIoT, and SCADA environments.
Section 6: applying the Cybersecurity Framework to OT
Section 6 maps OT guidance onto the CSF functions and categories used at publication time (CSF 1.1): Identify, Protect, Detect, Respond and Recover, with categories such as Asset Management (ID.AM), Identity Management and Access Control (PR.AC), Security Continuous Monitoring (DE.CM) and Response Planning (RS.RP). Each subsection gives OT-specific recommendations.
Note that CSF 2.0, released in February 2024, added a Govern function and reorganized several categories, so Rev. 3's category codes do not match CSF 2.0 exactly. This is one of the main reasons for Rev. 4.
Subsections worth reading even if you skip the rest:
- Asset Management (ID.AM): why inventory comes first and how to collect it safely. See OT asset inventory with passive monitoring.
- Remote Access (under Protect): restrictions on vendor and remote engineering access, explored in secure remote access for OT vendors.
- Flaw Remediation and Patch Management: testing, compensating controls and timing. See OT vulnerability management.
- Time Synchronization: often ignored until an investigation needs correlated logs.
The appendices
- Appendix C, Threat Sources, Vulnerabilities, and Incidents: a catalog of adversarial and non-adversarial threats, policy and system vulnerabilities, and summaries of real incidents. Useful input for risk workshops and for MITRE ATT&CK for ICS mapping. The ICS attack case studies cover the major incidents in more detail.
- Appendix D, OT Security Organizations, Research, and Activities: a directory of standards bodies, sector groups and research programs.
- Appendix E, OT Security Capabilities and Tools: short, vendor-neutral descriptions of segmentation (firewalls, unidirectional gateways, VLANs, SDN), monitoring (centralized logging, passive and active scanning, malware detection, behavioral anomaly detection, deception, digital twins) and data security (backups, immutable storage, hashing, signatures, remote access).
- Appendix F, OT Overlay: tailoring of SP 800-53 Rev. 5 controls for OT.
Appendix F: the OT overlay in practice
The OT overlay is the most reused part of the document. It takes the SP 800-53 Rev. 5 control catalog and its Low, Moderate and High baselines and indicates, for each control, whether it applies to OT, how it should be tailored, and supplemental guidance specific to OT. Compensating controls are discussed where a control cannot be applied to a legacy device.
A workable way to use it:
- Categorize each OT system (or each 62443 zone) as Low, Moderate or High impact using Section 4.
- Pull the matching OT baseline from Appendix F.
- For each control, record whether it is implemented by the device, by the zone boundary, or by a compensating control. For example, many PLCs cannot enforce per-user authentication (IA-2), so you may compensate with network restrictions to the engineering workstation and strong authentication on that workstation.
- Track the gaps in your program backlog with owners and target dates.
If your organization already follows IEC 62443, you do not need to choose. SP 800-82 references 62443, and both describe zones, conduits and defense in depth. Many teams use 62443 for system design requirements and SP 800-82 with its overlay for program structure and control mapping, especially in US federal or regulated environments.
Common mistakes when applying SP 800-82
- Treating it as a checklist. It is guidance. Use the overlay for control coverage and the rest of the document for engineering judgment.
- Applying IT controls as written. Active scanning, aggressive account lockout and automatic patching are examples NIST flags as risky in OT. Test first, or use passive and compensating approaches.
- Skipping the safety link. The document repeatedly ties security to safety. Bring process safety engineers into risk assessment and change management.
- Ignoring Rev. 4 completely. You do not need to migrate until it is final, but expect future audits to reference CSF 2.0 language.
A one-page action plan from SP 800-82
If you need something to start Monday:
- Form the cross-functional OT security team and charter (Section 3).
- Build or refresh the asset inventory and data flow map (Section 6, ID.AM; Appendix E.2.2 on passive scanning).
- Draw zones and enforce adjacent-level-only firewall rules (Section 5).
- Lock down remote access with brokered, logged, multifactor sessions (Section 6, Protect).
- Centralize logs and add OT network monitoring (Section 5, Section 6 Detect).
- Write and exercise an OT incident response and recovery plan, including backups of controller logic (Section 3, Section 6 Respond and Recover).
- Map your controls against the Appendix F baseline and track gaps.
References
- NIST SP 800-82 Rev. 3, Guide to Operational Technology (OT) Security
- NIST SP 800-82 Rev. 3, full text PDF
- NIST SP 800-82 Rev. 4 initial public draft
- NIST SP 800-53 Rev. 5, Security and Privacy Controls
- NIST SP 800-53 overlay repository
- NIST Cybersecurity Framework
- CISA: Industrial Control Systems
- ISA/IEC 62443 Series of Standards
- UK NCSC: Operational technology collection