NIST SP 800-82 Revision 3, "Guide to Operational Technology (OT) Security," is the US National Institute of Standards and Technology's primary reference for securing the systems that monitor and control physical processes — not just traditional IT. NIST's own publication page states the document "provides guidance on how to improve the security of OT while addressing their unique performance, reliability, and safety requirements." Published in September 2023, Rev. 3 supersedes Revision 2 (3 June 2015), which carried the narrower title "Guide to Industrial Control Systems (ICS) Security." The rename signals the document's central change: its scope grew from industrial control systems specifically to operational technology as a whole.
Key takeaways
- Rev. 3 has six numbered sections and seven appendices, per the table of contents of the NIST PDF.
- Because availability, safety and timing come first, and many OT devices cannot carry typical IT controls.
- Appendix C sorts typical vulnerabilities and predisposing conditions into six tables (Tables 15–20), from architecture and design to sensors and field assets.
- The overlay starts from the SP 800-53 Rev.
From "ICS" to "OT": why did the title change?
NIST's own definition, carried in the current publication, states that OT "encompasses a broad range of programmable systems or devices that interact with the physical environment (or manage devices that interact with the physical environment)," and that these systems and devices "detect or cause a direct change through the monitoring and/or control of devices, processes, and events." NIST's examples extend well past the classic ICS categories (SCADA, DCS, PLCs) to include building automation systems, transportation systems, physical access control systems, and physical environment monitoring and measurement systems. A reader who only knows Rev. 2 should expect Rev. 3 to apply to a wider set of systems than "industrial control systems" alone would suggest — including, for example, a building's HVAC controllers or an access-control panel, not only a factory floor's PLCs.
What did Rev. 3 change from Rev. 2?
Per NIST's own September 2023 announcement of the publication, the major updates in Revision 3 are:
| Change | What it means |
|---|---|
| Scope expansion | From industrial control systems (ICS) specifically to the broader category of operational technology (OT) |
| Updated threats and vulnerabilities | Revised descriptions of what typically threatens OT and where OT systems are typically weak |
| Updated risk management guidance | Revised recommended practices and reference architectures for managing OT risk |
| SP 800-53 alignment | New tailoring guidance for NIST SP 800-53 Rev. 5 controls, plus a dedicated OT overlay giving tailored control baselines for low-, moderate- and high-impact OT systems |
| Cross-framework alignment | Closer alignment with the NIST Cybersecurity Framework (CSF) and other OT security standards and guidelines |
NIST's own page for the publication confirms the structural approach stays consistent with earlier revisions: the guide "provides an overview of OT and typical system topologies, identifies typical threats to organizational mission and business functions supported by OT, describes typical vulnerabilities in OT, and provides recommended security safeguards and countermeasures to manage the associated risks." The full Rev. 3 PDF places the OT overlay in Appendix F; for an audit, cite the control and enhancement numbers from that appendix, not from a secondary summary.
How is the Rev. 3 document organised?
Rev. 3 has six numbered sections and seven appendices, per the table of contents of the NIST PDF. Most suppliers only need four of them.
| Part | What it covers | Most useful to |
|---|---|---|
| §2 OT Overview | SCADA, DCS, PLC topologies, building automation, physical access control, safety systems, IIoT; §2.4 compares OT and IT security | Everyone; product managers writing a security concept |
| §3 OT Cybersecurity Program Development | Charter, business case, governance, training, incident response, recovery | Asset owners |
| §4 Risk Management for OT Systems | Framing and assessing OT risk, supply chain risk (§4.2.1), safety systems, the NIST Risk Management Framework steps | Asset owners; suppliers answering risk questionnaires |
| §5 OT Cybersecurity Architecture | Defense-in-depth layers (security management, physical, network, hardware, software), Purdue Level 0, reference models for DCS, PLC with IIoT, SCADA | Machine builders and system integrators |
| §6 Applying the Cybersecurity Framework to OT | Guidance per CSF 1.1 category (ID.AM, PR.AC, DE.CM …), remote access, patch management, time synchronisation | Both sides |
| Appendix C | Threat sources, vulnerabilities and predisposing conditions, threat events | Device makers (product requirements) |
| Appendix E | Capabilities and tools: segmentation, monitoring, passive and active scanning, data security | Both sides |
| Appendix F | The OT overlay of SP 800-53 Rev. 5 controls (Table 22 summarises the baselines) | Organisations that already run SP 800-53 |
The architecture section is where the Purdue model and zone thinking appear, and it is the part a machine builder's customer will hold the network design against.
Why does OT need different security from IT, per NIST?
Because availability, safety and timing come first, and many OT devices cannot carry typical IT controls. Section 2.4 of the Rev. 3 PDF lists the considerations; several translate directly into product requirements.
| NIST consideration (§2.4) | What it means for a device or machine maker |
|---|---|
| Timeliness and performance: deterministic responses, delay and jitter limits | Security functions (encryption, logging) must not break the control cycle; document their timing cost |
| Availability: outages are scheduled "days or weeks in advance"; rebooting is "usually not acceptable" | Updates must be installable in a maintenance window, with rollback |
| Risk management: "Any security measure that impairs safety is unacceptable" | Lockouts, session timeouts and fail-closed behaviour need a safety review |
| Resource constraints: legacy devices may lack "encryption capabilities, error logging, and password protection" | Plan memory and CPU headroom for security features in new hardware |
| Change management: updates "need to be thoroughly tested by both the vendor and the end user" | Ship release notes and test evidence that let the customer requalify quickly |
| Component lifetime: often "10 to 15 years and sometimes longer" | Support periods and component end-of-life tracking must match that horizon |
Which product weaknesses does SP 800-82 list for OT?
Appendix C sorts typical vulnerabilities and predisposing conditions into six tables (Tables 15–20), from architecture and design to sensors and field assets. Several entries describe the product, not the plant:
| Appendix C entry | Table | Product-side reading |
|---|---|---|
| Improper data validation, leading to "buffer overflows, command injections, cross-site scripting, and path traversals" | 18 Software development | Input validation in web UIs, protocol parsers and file import |
| "Installed security capabilities are not enabled by default" | 18 | Ship secure defaults, or at least report disabled features |
| Inadequate authentication and access control in configuration and programming software | 18 | Authenticate engineering tools, not only the HMI |
| "Many OT protocols have no authentication at any level" | 19 Communication and network | Offer authenticated protocol variants where they exist |
| Plaintext telnet, FTP, HTTP and NFS | 19 | Disable plaintext services by default |
| Vendor patches arrive "long after security vulnerabilities are found"; some legacy OT never gets them | 16 Configuration and maintenance | Publish interim mitigations and a support period |
| Hardware, firmware and software not under asset or configuration management | 16 | Give customers exact firmware versions and component lists |
The configuration-and-maintenance rows are why asset owners ask suppliers for component lists. A firmware SBOM answers the "what is inside this version" question that Table 16 says organisations often cannot.
How does the OT overlay tailor SP 800-53?
The overlay starts from the SP 800-53 Rev. 5 catalogue and the Low, Moderate and High baselines in SP 800-53B, then adjusts them for OT. Appendix F explains the mechanics:
It is a partial tailoringThe overlay adds OT discussion and changes baselines; it does not reprint the 800-53 control text. Table 22 marks every changeBold means an OT discussion was added; underline means the overlay added a control or enhancement to a baseline; strikethrough means it removed one compared with SP 800-53B. NIST's own example: enhancement 1 of AU-4 (Audit Storage Capacity) is added to all three baselines and gets an OT discussion. Privacy-only controls are removedControls that appear only in the privacy baseline are taken out; privacy stays a separate risk decision. It applies to federal agencies and is voluntary for everyone elseAppendix F.2 says the overlay "may be used by non-governmental organizations on a voluntary basis." It can be tailored furtherNIST expects sector overlays (pipeline, energy) and even system-specific ones, and lists overlays in its overlay repository.
For a supplier, this means a federal or critical-infrastructure customer may send a questionnaire organised by 800-53 control families (AC, IA, SI, SR …). Map product features to those families once and reuse it.
What does the Rev. 4 draft change?
NIST released an initial public draft of Rev. 4 on 21 September 2026, with comments due 30 November 2026. Rev. 3 stays the final version until a final Rev. 4 is published. The draft page lists these updates:
- an expanded introduction to OT sectors, adding building automation and control systems, water and wastewater, food and agriculture, freight rail, maritime vessels, and IIoT and cloud convergence;
- a restructure around the NIST Cybersecurity Framework 2.0, including a reorganised risk management section that focuses on the CSF Govern function;
- expanded discussion of how OT risk management aligns with enterprise risk management (NIST IR 8286r1);
- discussion of adopting the NIST Risk Management Framework, in Appendix F;
- expanded guidance on asset management and on network monitoring and detection;
- architecture guidance focused on protecting system management functions and applying zero trust principles.
For suppliers. Rev. 3 §6 is organised by CSF 1.1 categories (ID.AM, PR.AC …). If you keep a mapping of product features to SP 800-82 sections, plan for its §6 references to change when Rev. 4 is final.
Who wrote it, and where does it fit?
SP 800-82 Rev. 3 was produced jointly by NIST's Smart Connected Systems Division and Computer Security Division, with co-authors from MITRE; the FAQ below lists the names. NIST's September 2023 announcement notes the series "has been downloaded more than 3 million times since its initial release" in 2006, which makes it a common reference well beyond the US federal agencies it formally applies to. Appendix D points readers to related work such as ISA/IEC 62443, CISA ICS advisories and MITRE ATT&CK for ICS.
Where does this sit next to IEC 62443 and the CRA?
SP 800-82 is a risk-management and reference-architecture guide, not a certifiable requirements standard: it describes what OT risk typically looks like and how to tailor general-purpose controls such as SP 800-53 to OT's safety and availability constraints. The ISA/IEC 62443 series sets testable requirements at the system level (see our IEC 62443-3-3 guide) and the component level (see IEC 62443-4-2 vs the Cyber Resilience Act). EU product law such as the Cyber Resilience Act and the RED delegated act (EN 18031) imposes legal obligations on products placed on the EU market. The documents meet directly: §4.1.1 of the Rev. 3 PDF names FIPS 199 and an approach based on ISA 62443-3-2 as two ways to define OT impact levels (see IEC 62443-3-2). A plant can use SP 800-82 to decide which IEC 62443 security levels matter per zone; a device maker selling into the EU still tracks the CRA and EN 18031, and a machine builder the Machinery Regulation.
Worked example: how would a controller maker read SP 800-82?
Synthetic example: "RTU-40" and its maker are invented for illustration. RTU-40 is a remote terminal unit for water pump stations, with Modbus TCP and DNP3, a web configuration page and an LTE modem. A US utility asks how it supports the utility's SP 800-82 programme.
Locate the product in §2 and §5RTU-40 is a field device in a SCADA topology (§2.3.2), sitting at a remote site reached over a wide-area link — the geographically distributed case in §5.3.3. Turn Appendix C into a requirements checkTable 18: are all web and protocol inputs validated, are security features enabled by default? Table 19: can DNP3 run with authentication, is the web page HTTPS-only, is telnet off? Table 16: does each release ship with its component list? Answer the utility's overlay questions by familyIA (identification and authentication): local accounts, no shared default password. AU: which events RTU-40 logs, and whether logs can be forwarded. SI: how firmware updates are signed and verified. SR: where the components come from. Address supply chain risk (§4.2.1)NIST asks buyers to check "a product's provenance, pedigree, and composition" and how hard replacement parts and updates will be to get over the product's life. The maker attaches an SBOM, the support period and its vulnerability disclosure contact. Run a known-vulnerability check before answeringIn this synthetic case the SBOM shows an old embedded web server with published CVEs; the maker upgrades it in the next release and documents an interim mitigation (restrict the web page to the management VLAN), as Table 16 recommends.
Takeaway. Organise the product security file by Appendix C and the 800-53 families, and it answers most SP 800-82 questions.
What is a workable starting point?
Re-scope your asset inventory from "ICS" to "OT"If your existing inventory only captures SCADA/DCS/PLC assets, Rev. 3's broadened definition is a prompt to check whether building automation, physical access control, or environmental monitoring systems on the same networks have been left out. Prefer passive discovery on live networksAppendix E.2.2 notes passive scanning adds no traffic, "which is ideal for sensitive devices," but cannot see silent devices or encrypted traffic and "will often take days." Active scans "may cause device instability" and belong in scheduled outages (E.2.3). Use the OT overlay as a starting baseline, not a final one, if your organization already maintains an SP 800-53 Rev. 5 control set — tailor from the overlay rather than building an OT control baseline from scratch. Confirm any specific control-ID or appendix citation against the published PDFbefore relying on it in an audit, and record whether you cite Rev. 3 or the Rev. 4 draft.
What are the common pitfalls?
- Treating SP 800-82 as a certification. There is no SP 800-82 certificate; the overlay is guidance, voluntary outside federal agencies.
- Citing the Rev. 4 draft as final. Until NIST publishes the final Rev. 4, Rev. 3 is the current guidance.
- Applying IT practice unchanged. Automatic reboots, aggressive account lockout and active scans can each stop a process; §2.4 says so explicitly.
- Answering for the product with plant controls. A firewall at the plant boundary does not fix a device that ships with telnet enabled.
SoftWSP's OT Snapshot works from Zeek protocol logs of a factory's own traffic capture, so nothing is sent to the OT network: it builds a host inventory, shows which hosts speak Modbus, S7comm, DNP3, EtherNet/IP or BACnet, and flags interactive remote-access sessions (SSH, Telnet, RDP, VNC) for an engineer to review — see OT Snapshot. For the product side, SoftWSP extracts a firmware SBOM as CycloneDX JSON, matches its components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and drafts a cited report for engineer review: see device firmware security.
This guide summarises a public NIST publication; it does not constitute legal or compliance advice.
Put this guide to work
Frequently asked questions
What is NIST SP 800-82?
Special Publication 800-82, "Guide to Operational Technology (OT) Security," is NIST's primary guidance document for securing OT systems. NIST's own publication page states the current version, Revision 3, "provides guidance on how to improve the security of OT while addressing their unique performance, reliability, and safety requirements," and was published in September 2023. It supersedes Revision 2, published 3 June 2015, which was itself titled "Guide to Industrial Control Systems (ICS) Security" — the renaming reflects the scope change described below.
What changed in Revision 3?
Per NIST's own September 2023 announcement, the headline change is a scope expansion from industrial control systems (ICS) specifically to the broader category of operational technology (OT), plus updates to OT threats and vulnerabilities, OT risk management guidance, recommended practices and architectures, and closer alignment with the NIST Cybersecurity Framework and other OT security standards. Rev. 3 also adds new tailoring guidance for SP 800-53 Rev. 5 controls, including an OT overlay providing tailored control baselines for low-, moderate- and high-impact OT systems.
How does SP 800-82 define "OT", and how is that different from "ICS"?
NIST's own text defines OT as encompassing "a broad range of programmable systems or devices that interact with the physical environment (or manage devices that interact with the physical environment)," which "detect or cause a direct change through the monitoring and/or control of devices, processes, and events." That is deliberately broader than industrial control systems alone: NIST's examples of OT include industrial control systems, building automation systems, transportation systems, physical access control systems, and physical environment monitoring and measurement systems — categories that Rev. 2's ICS-only title did not explicitly cover.
Who wrote it, and is it free?
SP 800-82 Rev. 3 is published by NIST's Smart Connected Systems Division (Networked Control Systems Group) together with NIST's Computer Security Division; the listed authors are Keith Stouffer, Michael Pease, CheeYee Tang, Timothy Zimmerman, Victoria Pillitteri and Suzanne Lightman of NIST, with Adam Hahn, Stephanie Saravia, Aslam Sherule and Michael Thompson of MITRE. It is a free, public US government publication, available as a PDF from NIST's own site; per NIST's September 2023 announcement, the series has been downloaded more than 3 million times since the original 2006 release.
Sources
- NIST CSRC: SP 800-82 Rev. 3, Guide to Operational Technology (OT) Security — final publication page
- NIST: NIST Publishes Guide to Operational Technology (OT) Security (announcement, September 2023)
- NIST CSRC: Operational Technology Security — project publications page
- NIST: NIST.SP.800-82r3 — full text PDF
- NIST CSRC: SP 800-82 Rev. 3 — DOI landing page
- NIST CSRC: SP 800-82 Rev. 4 (Initial Public Draft), Guide to Operational Technology (OT) Security, 21 September 2026
- NIST: NIST.SP.800-82r4.ipd — initial public draft PDF
- NIST CSRC: SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations
- NIST CSRC: SP 800-53B, Control Baselines for Information Systems and Organizations
- NIST CSRC: SP 800-53 overlay repository
- NIST: Cybersecurity Framework
About this guide
SoftWSP OT/ICS Desk
Covers the OT/ICS security cluster: 67 guides.

All guides in this cluster: OT/ICS security
Questions about this page?
