Two operators at a control-room desk with a row of monitors, a laptop and keyboards

OT/ICS security

NIST SP 800-82 Rev. 3: the Guide to Operational Technology (OT) Security, explained

Last updated:

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:

  1. It is a partial tailoringThe overlay adds OT discussion and changes baselines; it does not reprint the 800-53 control text.
  2. 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.
  3. Privacy-only controls are removedControls that appear only in the privacy baseline are taken out; privacy stays a separate risk decision.
  4. 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."
  5. 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.

  1. 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.
  2. 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?
  3. 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.
  4. 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.
  5. 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?

  1. 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.
  2. 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).
  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.
  4. 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

  1. NIST CSRC: SP 800-82 Rev. 3, Guide to Operational Technology (OT) Security — final publication page
  2. NIST: NIST Publishes Guide to Operational Technology (OT) Security (announcement, September 2023)
  3. NIST CSRC: Operational Technology Security — project publications page
  4. NIST: NIST.SP.800-82r3 — full text PDF
  5. NIST CSRC: SP 800-82 Rev. 3 — DOI landing page
  6. NIST CSRC: SP 800-82 Rev. 4 (Initial Public Draft), Guide to Operational Technology (OT) Security, 21 September 2026
  7. NIST: NIST.SP.800-82r4.ipd — initial public draft PDF
  8. NIST CSRC: SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations
  9. NIST CSRC: SP 800-53B, Control Baselines for Information Systems and Organizations
  10. NIST CSRC: SP 800-53 overlay repository
  11. NIST: Cybersecurity Framework
Was this guide helpful?

All guides in this cluster: OT/ICS security

Australia's Security of Critical Infrastructure (SOCI) Act: cyber obligations, explainedWhat the Security of Critical Infrastructure Act 2018 actually requires: the 11 sectors, the Critical Infrastructure Risk Management Program (CIRMP), 12-hour/72-hour mandatory cyber incident reporting, and Enhanced Cyber Security Obligations for Systems of National Significance.BACnet protocol security: why building automation runs unauthenticated, and what BACnet/SC changesBACnet/IP, the protocol behind most commercial building automation, broadcasts commands in plaintext with no authentication by default. What ASHRAE Addendum 135-2016bj's BACnet/SC actually fixes, and what a decade of CISA advisories against Siemens, KMC Controls and SCADA Engine shows about where BACnet deployments actually fail.CAN bus security: what ISO 11898 does and doesn't protect in machines and vehiclesCAN — the broadcast bus Bosch released in 1986 and ISO standardized as ISO 11898 — has no authentication, encryption or message-origin field by design. What two real CISA ICS alerts found, what CAN FD and CAN XL change (and don't), and what machine builders should check first.CC-Link IE TSN protocol security: the 2025–2026 CVE record, explainedCC-Link IE TSN is Mitsubishi Electric and the CLPA's flagship Ethernet/TSN industrial network for smart factories. Two Mitsubishi-disclosed CVEs in 2025 and 2026 show what happens when a deterministic fieldbus protocol built for speed, not authentication, meets a network attacker — and what mitigations actually exist today.CISA BOD 23-02: what it requires, and what OT/ICS operators should take from an IT-only directiveCISA's Binding Operational Directive 23-02 gives federal civilian agencies 14 days to fix exposed management interfaces. It binds no one in OT/ICS or the private sector — but 2026's real PLC exposure incidents show exactly why the same pattern matters there too.CISA Secure by Demand: 12 priority considerations for OT product buyersWhat CISA's Secure by Demand joint guide (13 January 2025) tells OT owners and operators to require from manufacturers when buying PLCs, HMIs and RTUs: the 12 priority security elements, the ISA/IEC 62443 reference, and the April 2025 fact sheet.DDS security: what the core spec leaves out, and what the 2021 multi-vendor disclosure foundDDS (Data Distribution Service) is the default middleware behind ROS 2 robots, medical devices and industrial control systems, but core DDS carries no mandatory security of its own. What the separate OMG DDS Security spec adds, and what a 2021 coordinated disclosure found across six independent DDS implementations.DNP3 protocol security: what Secure Authentication covers, and what it doesn'tDNP3 runs most of North America's grid and water telecontrol — and like Modbus, its base protocol has no authentication. What IEEE 1815-2012's optional Secure Authentication layer actually adds, and what a decade of CISA advisories (IOServer, GE Proficy, Triangle MicroWorks) shows about where DNP3 stacks actually fail.DNP3 Secure Authentication (SAv5): IEEE 1815's challenge-response layerDNP3 Secure Authentication v5 mandates SHA-256 and AES-256 Key Wrap as its default algorithms, but a 2017 Tamarin-prover formal analysis and practitioner reporting both point to the same bottleneck: key management, not cryptography, is why SAv5 stays rare in the field.EtherCAT security: no native authentication in the wire protocol, and what fills the gapEtherCAT's base protocol (ETG.1000, IEC 61158 Type 12) carries no authentication or encryption of its own — security depends on hardware frame processing, a closed topology, and now an IEC 62443-3-3 Security Level 2 certification layered on top. What academic MITM research and the one confirmed CISA advisory touching EtherCAT actually found.EtherNet/IP and CIP Security: why Rockwell's most-deployed protocol still ships unauthenticated by defaultEtherNet/IP and the Common Industrial Protocol (CIP) it carries run a large share of North American discrete manufacturing, and CIP has no authentication unless a site explicitly deploys ODVA's CIP Security extension. What CIP Security's five profiles actually add, what a 2021-to-2026 run of Rockwell Automation CISA advisories shows about real failures, and the controls that compensate where it isn't deployed.GE Vernova UR relay vulnerabilities: the 2025 CVE chain, explainedNozomi Networks disclosed five 2025 CVEs in GE Vernova's UR protection-relay family and EnerVista UR Setup software, two of which chain into a man-in-the-middle-to-malicious-firmware attack.HART and WirelessHART protocol security: what's protected, and what still isn'tHART runs over a 4-20mA loop with no authentication at all; WirelessHART (IEC 62591) added mandatory AES-128 encryption and key management. What CISA advisories on HART DTMs and WirelessHART gateways show about where the real risk sits.ICCP/TASE.2 protocol security, explainedHow the Inter-Control Center Communications Protocol (ICCP, IEC 60870-6/TASE.2) moves real-time data between power-grid control centers, why the base protocol has no built-in authentication or encryption, and where NERC CIP and IEC 62351-4 fit.IEC 60870-5-104 security: the protocol Industroyer2 used to attack a power gridIEC 60870-5-104 carries telecontrol traffic for power grids and water utilities in cleartext with no built-in authentication. Industroyer2's own code confirms it spoke nothing but IEC-104 to attack Ukraine's grid in 2022, and Hitachi Energy RTU500 advisories show the gap is still being found in 2026.IEC 61511 cybersecurity: what Clause 8.2.4's security risk assessment requiresWhat IEC 61511-1 Clause 8.2.4's security risk assessment requires, what ISA-TR84.00.09 and IEC 62443 add, and why TRITON/TRISIS made it urgent.IEC 61850 security: what GOOSE, Sampled Values and MMS do and don't protectIEC 61850 standardizes substation automation communication — GOOSE, Sampled Values and MMS — but the base protocol was not designed with cryptographic security in mind. What IEC 62351-6 adds, and what two 2026 CISA ICS advisories against real IEC 61850 implementations actually found.IEC 62351: data and communications security for power system protocols, explainedWhat the IEC 62351 series actually covers: the 20 published parts, what each one secures (TLS profiles, GOOSE/SMV signing, RBAC, key management), and how it differs from NERC CIP-013 and IEC 62443.IEC 62443-1-1 (Terminology, concepts and models), explainedWhat IEC TS 62443-1-1:2009 actually defines: the IACS reference model, zones/conduits vocabulary, Security Level concept, seven foundational requirements, and why it's still a Technical Specification 16+ years on.IEC 62443-2-1: security program requirements for IACS asset owners, explainedWhat IEC 62443-2-1's 2024 edition requires of IACS asset owners: the eight Security Program Elements, the shift to a maturity model, and how it fits the wider 62443 series.IEC 62443-2-2 (IACS security protection scheme), explainedWhat IEC PAS 62443-2-2:2025 actually covers: the Security Protection Scheme (SPS), the target/implemented/operated Security Protection Rating (SPR) model, the five principal roles, and how it links 62443-2-1's maturity model to 62443-3-3's security levels.IEC 62443-2-3 (Patch management in the IACS environment), explainedWhat IEC TR 62443-2-3:2015 actually covers: the patch lifecycle model, recommended requirements for asset owners and IACS product suppliers, and the VPC exchange format for vendor patch compatibility data.IEC 62443-2-4 (security program requirements for IACS service providers), explainedIEC 62443-2-4:2023 Edition 2.0 — the part of the ISA/IEC 62443 series that sets security requirements for system integrators and maintenance providers, its 12 Security Program functional areas, Profiles mechanism, and how it pairs with IEC 62443-2-1.IEC TR 62443-3-1 (security technologies for IACS), explainedWhat IEC/TR 62443-3-1:2009 actually covers: the eight categories of cybersecurity technology it surveys, the eight-point framework used to assess each one, and why it is the series' most dated part.IEC 62443-3-2 (security risk assessment for system design), explainedIEC 62443-3-2:2020's seven Zone and Conduit Requirements (ZCR 1-7), how zones, conduits and target security levels (SL-T) get set, and how the output hands off to IEC 62443-3-3.IEC 62443-3-3: system security requirements and security levels, explainedISA/IEC 62443-3-3 explained from the standard's own scope text: the seven foundational requirements, capability vs target vs achieved security levels (SL-C/SL-T/SL-A), and where it sits in the 62443 series.IEC 62443-4-1: the secure product development lifecycle, explainedWhat IEC 62443-4-1 requires of a maker's development process: its eight practices, maturity levels, SDLA certification, and how it relates to 4-2.IEC 62443-4-2: the four component types and ISASecure CSA certification, explainedIEC 62443-4-2's own component taxonomy — software application, embedded device, host device and network device — plus the four ISASecure CSA assessment elements and capability levels that certify against it.IEC 62443 and SBOM for industrial automation: what the standard asks and what to shipWhere SBOMs fit in IEC 62443-4-1 (SM-9, SM-10, DM, SUM), 4-2 and 2-3, how an automation OEM builds one from firmware, and reuse for CRA and FDA.ISA100.11a wireless industrial protocol security, explainedISA100.11a (IEC 62734) builds AES-128 encryption and device authentication in. What 2025 CVEs in Honeywell's OneWireless WDM show it doesn't protect.ISO 15118 security: Plug & Charge PKI, TLS, and the SLAC MITM gapCISA's CVE-2025-12357 advisory confirms an ISO 15118-2 SLAC-pairing flaw lets an attacker inject a man-in-the-middle wirelessly via electromagnetic induction, while the separate Brokenwire attack can abort a charging session from 47 meters using under 1 watt of RF power.ISO/IEC 27019: information security controls for the energy utility industry, explainedWhat ISO/IEC 27019 actually adds on top of ISO/IEC 27002 for energy utility process control systems: scope, exclusions (nuclear, telecom), structure, and what changed in the 2024 edition.KEV and EPSS: a practical way to prioritise vulnerabilities in OT and device fleetsHow to combine CISA's KEV catalog and FIRST's EPSS score to triage vulnerabilities in OT and device fleets, with CISA's BOD 26-04 deadlines and SSVC.KNX protocol security: what KNX Secure fixes, and why classic KNX cannot be patchedThe classic KNX bus that runs most commercial building automation carries no authentication or encryption — and ABB's own 2026 advisory, republished by CISA, says legacy KNX products cannot be fixed with a software update. What KNX Data Secure and KNX IP Secure actually add, and what two documented ETS and BCU-key vulnerabilities show about where real KNX deployments fail.MITRE ATT&CK for ICS: the adversary tactics and techniques matrix, explainedMITRE's ATT&CK for ICS knowledge base — the 12 tactics and current technique/sub-technique counts in the v20 matrix, how it differs from ATT&CK Enterprise, and how asset owners use it.Modbus protocol security: why it has none, and what to do about itWhy Modbus — still the most common OT/ICS protocol on the plant floor — has no built-in authentication or encryption, what CISA's and vendors' advisories show that gap actually costs, and the segmentation, function-code filtering and Modbus/TCP Security options that compensate for it.NERC CIP-002: BES Cyber System categorization, and the CIP-002-8 revision already on the wayWhat NERC Reliability Standard CIP-002-5.1a requires for identifying and categorizing BES Cyber Systems as high, medium or low impact — why CIP-002-6 was withdrawn in 2021, and how the FERC-approved CIP-002-7 and CIP-002-8 revisions, both effective 2028, fit together.NERC CIP-003: security management controls, explainedWhat NERC Reliability Standard CIP-003-9 requires — the 15-month cyber security policy review, the CIP Senior Manager and delegation requirements, Attachment 1's six-section low impact cyber security plan — plus the FERC-approved CIP-003-11 successor and its 2029 compliance date.NERC CIP-004: personnel & training for BES cyber systems, explainedWhat NERC Reliability Standard CIP-004-7 requires — security awareness, the nine-topic cyber security training program, seven-year personnel risk assessments, access management and the 24-hour/next-day/30-day access revocation timelines — plus the FERC-approved CIP-004-8 virtualization revision coming in 2028.NERC CIP-005: Electronic Security Perimeter(s), and the CIP-005-8 revision already on the wayWhat NERC Reliability Standard CIP-005-7 requires for Electronic Security Perimeters, Remote Access Management and vendor remote access — plus FERC Order No. 919 (March 2026), which already approved the CIP-005-8 virtualization revision for a 2028 compliance date.NERC CIP-006: physical security for BES cyber systems, explainedWhat NERC Reliability Standard CIP-006-6 requires — the Physical Security Plan's ten requirement parts, the Visitor Control Program, PACS maintenance and testing, 90-day log and three-year evidence retention — plus the FERC-approved CIP-006-7.1 virtualization revision effective 2028.NERC CIP-007: system security management requirements, explainedWhat NERC Reliability Standard CIP-007-6 actually requires — ports/services, patch management, malicious code prevention, security event monitoring, system access control — and the FERC-approved CIP-007-7.1 revision coming in 2028.NERC CIP-008: cyber security incident reporting and response planning, explainedWhat NERC Reliability Standard CIP-008-6 requires — documented incident response plans, the 15-month test cadence, lessons-learned updates and the 1-hour/next-day E-ISAC and NCCIC reporting timelines — plus the FERC-approved CIP-008-7.1 virtualization revision coming in 2028.NERC CIP-009: recovery plans for BES cyber systems, explainedWhat NERC Reliability Standard CIP-009-6 requires — backup and recovery plan specifications, the 15-month and 36-month testing cadences for high-impact systems, and lessons-learned updates — plus the FERC-approved CIP-009-7.1 virtualization revision coming in 2028.NERC CIP-010: configuration change management and vulnerability assessments, explainedWhat NERC Reliability Standard CIP-010-4 requires — baseline configuration, change authorization, configuration monitoring, periodic vulnerability assessments and Transient Cyber Asset/Removable Media control — plus the FERC-approved CIP-010-5 virtualization revision coming in 2028.NERC CIP-011: information protection for BES cyber systems, explainedWhat NERC Reliability Standard CIP-011-3 requires — the two-part information protection program, BES Cyber System Information (BCSI) identification and handling, Cyber Asset reuse and disposal sanitization, three-year evidence retention — plus the FERC-approved CIP-011-4.1 virtualization revision coming in 2028.NERC CIP-012 (communications between Control Centers), explainedNERC CIP-012-2 — the currently enforceable standard protecting confidentiality, integrity and availability of Real-time Assessment/Real-time monitoring data between Control Centers. Requirement R1's five-part plan, the FERC Order No. 866 availability gap that drove the 2024 revision, and the 1 July 2026 effective date that retired CIP-012-1.NERC CIP-013-2 (Cyber Security — Supply Chain Risk Management), explainedWhat NERC Reliability Standard CIP-013-2 actually requires: the six security concepts every supply chain plan must address, the R1-R3 requirements verbatim, and the FERC Order 829/850 history behind it.NERC CIP-014 (physical security of transmission stations), explainedNERC CIP-014-3 — the risk assessment, third-party verification, physical security plan and third-party review cycle protecting critical Transmission stations, substations and primary control centers from physical attack — plus the FERC-approved CIP-014-4 successor's 1,500-foot proximate-facility rule and 1 October 2028 compliance date.NERC CIP-015-1 (internal network security monitoring), explainedWhat NERC CIP-015-1 actually requires: FERC Order No. 907's approval, the three-requirement text (data feeds, detection, evaluation, retention, protection), the staggered 1 October 2028 / 2030 compliance dates, and the CIP-015-2 expansion already underway.Niagara Fox protocol security: why building systems are still exposedTridium's Fox protocol runs building-automation and OT traffic between Niagara Framework stations. What the 2012 Niagara AX research found, what the FBI and Censys have found exposed since, and what Niagara 4's encrypted FoxS actually changes.NIST SP 1800-32: securing distributed energy resources, explainedWhat NIST SP 1800-32's reference architecture actually protects in DER and grid-edge IIoT communications, its three volumes, the command register concept, and what it does not cover.OCPP protocol security: why plaintext WebSockets keep showing up in CISA advisoriesOCPP 1.6J's own default Security Profile 1 allows an unencrypted WebSocket with optional basic auth, and in 2026 CISA published at least seven ICS advisories — Monta (CVSS 9.4), Everon (9.4), Hydro-Québec (9.8) — for exactly that gap: unauthenticated OCPP WebSocket endpoints.OPC UA security: built in, often unused, and what breaks when it isOPC UA was designed with security in its own spec — authentication, signing and encryption, defined policies and modes — unlike Modbus or classic OPC DA. What CISA's and the OPC Foundation's own 2026 research says about why most deployments still run without it, and the implementation CVEs in Kepware, Softing and open62541 that fill the gap.OT/ICS security for small and mid-sized manufacturers: where to start with no dedicated teamWhere a small factory with no OT security team should start: a passive asset inventory first, CISA's prioritized goals second, and IEC 62443-2-1 as the growth path — without installing agents on the shop floor.PROFIBUS DP security: a 1989 serial fieldbus with no authentication, still running 71 million devicesPROFIBUS DP, standardized in IEC 61158 Type 3, predates PROFINET by over a decade and has no authentication, encryption or session concept in its base protocol. What PI's own technical documentation does and doesn't say about security, what published research found, and why RS-485 wiring changes the practical response.PROFINET protocol security: the DCP weakness behind a decade of CISA advisoriesPROFINET runs a large share of the world's factory floors on Ethernet, and its Discovery and Configuration Protocol (DCP) has no authentication. What PI's three Security Classes actually add, what a decade of CISA advisories against Siemens PROFINET devices shows about real failures, and the segmentation controls that compensate.The Purdue Model for OT/ICS network architecture, explainedWhat the Purdue Model actually is: its 1990s manufacturing origin, the Level 0-5 hierarchy plus the Level 3.5 industrial DMZ, and why CISA and NIST still reference it even as cloud and remote access erode strict segmentation.S7comm protocol security: why Siemens S7 PLCs keep showing up in CISA advisoriesS7comm, the protocol Siemens S7 PLCs speak over TCP port 102, was built with no authentication for an era of isolated plant networks. What CISA's August 2026 joint advisory on AI-assisted S7 exploitation actually found, what S7CommPlus changes, and what an asset owner should check first.Sparkplug B protocol security: what MQTT's SCADA layer protects, and what it doesn'tSparkplug B's own specification calls its security chapter 'guidance only' and 'non-normative' — authentication, encryption and access control are left entirely to the MQTT broker. What that means for Birth/Death certificates, sequence numbers, a real Ignition vulnerability, and the AI analytics increasingly built on top of Sparkplug data.TriStation protocol security: the protocol TRITON/TRISIS exploitedTriStation is the proprietary protocol Schneider Electric's Triconex safety controllers speak with no built-in authentication. What CISA's HatMan report and the 2017 TRITON/TRISIS attack actually found, and the keyswitch and network controls that remain the only defense.TSA Pipeline Security Directives: what covered operators must doWhat TSA's two pipeline cybersecurity directive series actually require: 24/7 coordinators and incident reporting under SD-01, and the Cybersecurity Implementation/Incident Response/Assessment Plans under SD-02C, SD-02D and SD-02E, with effective dates.UDS (ISO 14229) security: the protocol that can reflash an ECU, and what guards itUDS — ISO 14229, run over ISO 15765-2 CAN transport — is the service set a dealer tool uses to read trouble codes and reflash ECU firmware. Its SecurityAccess (0x27) seed-key gate has a documented history of weak OEM implementations. What the Jeep Cherokee research actually found about it, what a 2024 academic paper demonstrated on a real truck, and what NHTSA recommends.UL 2900-2-2 (industrial control systems cybersecurity), explainedUL 2900-2-2 (Outline of Investigation, Issue 1, March 2016) — its ICS-specific scope on top of UL 2900-1, and why ISA's 2019 appeal kept it from ever becoming an ANSI-approved standard.Wi-SUN protocol security: the CVE record behind smart grid mesh networksWi-SUN mesh networking runs the field area networks behind smart electricity, gas and water meters worldwide. Three disclosed CVEs against Silicon Labs' Wi-SUN stack — two missing MAC-layer authorization checks and one predictable-key handshake flaw — show what happens when a utility-scale mesh protocol's security model has gaps.Z-Wave protocol security, explainedHow Z-Wave's S0 and S2 security frameworks actually work, why S2 became mandatory for certification in April 2017, the 2018 Z-Shave (CVE-2018-25029) downgrade attack, and what ITU-T G.9959 standardization means for building-automation deployments.

NIST SP 800-82 Rev. 3: the Guide to Operational Technology (OT) Security, explained