A collaborative approach to applying cybersecurity standards to distributed renewables

A California working group agreed minimum cybersecurity requirements for smart inverters and distributed energy management systems, based on international equipment standards.

About this good practice

The CPUC Smart Inverter Operationalization Cybersecurity (SIO-CS) subgroup was formed under Track 3 Phase 1 of the California Public Utilities Commission’s rulemaking to modernise the grid for a high distributed energy resources future (R.21-06-017). It answers one question: which existing cybersecurity standards should apply to smart inverter operationalisation and distributed energy resources’ management systems, so that communications between equipment and management systems are secure.

Facilitated by Xanthus Consulting International and Verdant Associates on behalf of the CPUC, the group met bi-weekly from May 2022 until early 2024. About 80 people joined, including DSOs (PG&E, SCE and SDG&E), distributed energy resource aggregators and owners, consultants, academics and CPUC staff. Members assessed each item in Section 5 of IEEE Std 1547.3-2023, the only distributed energy resource-focused cybersecurity standard at the time, as ‘shall’, ‘should’ or not applicable, and Phase 1 kept only the items all parties agreed should be ‘shall’ requirements. These cover network security, access control, data security, security management and logging of security events; no risk-assessment items reached consensus.

The group recommended three parallel paths: the CPUC recommends, without mandating, that DSOs use the Phase 1 requirements in the short term (Path F); it launches a Phase 2 working group and a cybersecurity coordination forum (Path G); and it endorses testing and certification programmes such as those being developed by UL and SunSpec (Path H). SCE agreed with the requirements but not with Path F.

The requirements state what must be met, not how, so DSOs would still need to specify details such as default cryptographic suites and logging formats to ensure interoperability.

Read more about the good practice

Want to learn more about this best practice? Follow the links below.