NIST SP 1800-32: securing distributed energy resources, explained

Last updated:

NIST SP 1800-32, Securing Distributed Energy Resources: An Example of Industrial Internet of Things Cybersecurity, is a National Cybersecurity Center of Excellence (NCCoE) practice guide published in final form in February 2022. It demonstrates a reference architecture — built from commercially available products and documented in three volumes — for protecting the trustworthiness of information exchanges between an electric distribution utility and the solar, storage, and other distributed energy resources (DERs) it monitors and dispatches over Industrial Internet of Things (IIoT) connections.

What problem does this actually solve?

Distributed energy resources — solar photovoltaic inverters, battery storage, and similar grid-edge devices — exchange status and control signals with a utility's distribution management system, often over connections the utility does not fully own or secure, since many DERs belong to commercial or residential operators rather than the utility itself. NIST's own framing: a distribution utility may need to remotely communicate with thousands of DERs to monitor status and control operating points, and any attack able to "deny, disrupt, or tamper with" those information exchanges could prevent necessary control actions and diminish grid resiliency. SP 1800-32 does not try to secure DER hardware in isolation; it targets the trust and integrity of the information exchange between utility and DER/microgrid operator.

What's in each of the three volumes?

Volume A (Executive Summary) is written for business decision-makers — CISOs, risk officers, compliance and technology leads — and lays out the goals the practice guide supports: a risk-based approach to connecting and managing DERs and grid-edge devices built on NIST and industry standards, protected data and communications traffic, secure edge-to-cloud data flows, and an immutable record of control commands shareable with DER management systems, aggregators, regulators, auditors, and grid operators. Volume B (Approach, Architecture, and Security Characteristics) documents the standards-based reference architecture itself, including a defined cyber demarcation point at each DER operator site. Volume C (How-To Guides) gives step-by-step build instructions for the example solution, built in the NCCoE lab with a VPN connection to a University of Maryland collaboration site, including the utility cyber-monitoring component that inspects network and application traffic for anomalous activity.

What is the "command register," and why does it matter?

The architecture's central idea is a command register: an independent, immutable record of commands and status exchanges between the utility and each DER or microgrid operator, maintained by a third party so either side can later verify exactly what was sent and received — useful evidence for grid operators, regulators, and auditors reconstructing what happened during a disputed control action or a suspected compromise. Volume B describes implementing this with a distributed ledger, combined with the cyber demarcation point at each DER site, as the mechanism that makes independent verification possible without either party having to fully trust the other's internal systems.

What does SP 1800-32 explicitly not cover?

The guide is direct about its own scope limit: Volume C states that the reference architecture provides an approach to ensuring DER/utility information exchanges are trustworthy, but neither volume is a complete cybersecurity solution for the utility's own network, the DER or microgrid operator's network, or how either network connects to the internet. A utility or DER operator still needs the broader OT security practices covered in frameworks like NIST SP 800-82 and sector-specific programs like NERC CIP for grid assets that fall under that jurisdiction — SP 1800-32 solves the DER communication-trust problem specifically, not general distribution-grid OT security.

SoftWSP's OT snapshot assessments passively map what's actually talking to what on an operational network — including grid-edge IIoT devices and the gateways brokering DER communications — without requiring agents on equipment that was never designed to run them. See OT snapshot services for how that fits alongside a DER-focused architecture like SP 1800-32's.

This guide is based on the final NIST SP 1800-32 publication (February 2022), its NCCoE documentation site (Volumes A, B and C), and the NCCoE's Securing Distributed Energy Resources project page, all read directly for this guide. SP 1800-32 describes an NCCoE example solution and reference architecture, not a mandatory compliance standard; check the NCCoE publication page for any later revisions before treating a specific architectural detail as current.

Sources

  1. NIST SP 1800-32, Securing Distributed Energy Resources: An Example of Industrial Internet of Things Cybersecurity (final, February 2022), NVLPUBS PDF
  2. NIST SP 1800-32, DOI record
  3. NCCoE: Securing Distributed Energy Resources — project and documentation homepage
  4. NCCoE: SP 1800-32 Volume A, Executive Summary
  5. NCCoE: Securing Distributed Energy Resources — project page (Energy sector)

Frequently asked questions

What is NIST SP 1800-32?

NIST Special Publication 1800-32, Securing Distributed Energy Resources: An Example of Industrial Internet of Things Cybersecurity, is a National Cybersecurity Center of Excellence (NCCoE) practice guide, published in final form in February 2022, that demonstrates a standards-based reference architecture for protecting information exchanges between electric utilities and distributed energy resources (DERs) such as solar photovoltaic installations.

What problem is it actually solving?

A distribution utility may need to remotely monitor and control thousands of DERs, many of which it does not own or configure, using Industrial Internet of Things (IIoT) communications that often lack built-in security. The guide's own framing is that any attack able to deny, disrupt, or tamper with DER communications could prevent a utility from performing necessary control actions and diminish grid resiliency — so the practice guide targets trustworthy, monitored information exchange rather than DER hardware security in isolation.

What are the three volumes of SP 1800-32?

Volume A is the Executive Summary for business decision-makers (CISOs, risk and compliance officers). Volume B, Approach, Architecture, and Security Characteristics, documents the standards-based reference architecture and its security characteristics. Volume C, How-To Guides, gives step-by-step instructions for building the example solution, including the lab's VPN-connected vSphere environment used between the NCCoE and the University of Maryland collaboration site.

What is the 'command register' the guide describes?

A command register is an independent, immutable record of information exchanges — commands and status updates — between a distribution utility and DER or microgrid operators, maintained by a third party so both sides can verify what was actually sent and received. Volume B describes a distributed-ledger-based implementation and a defined cyber demarcation point at each DER operator site as the architectural elements that make this verification possible.

Does SP 1800-32 provide complete cybersecurity for a utility's OT network?

No — the guide is explicit about this limit. Volume C states the reference architecture and example solution provide an approach to ensuring information exchanges between a utility and a DER or microgrid operator are trustworthy, but neither volume provides a complete cybersecurity solution for the utility network, the DER or microgrid operator's own network, or how either network interfaces to the internet. It solves the DER communication-trust problem specifically, not general OT network security (see our NIST SP 800-82 OT security guide for the broader picture).

In this cluster

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.

NIST SP 1800-32: securing distributed energy resources, explained