For most of the past decade, cybersecurity in energy projects was treated as a corporate IT matter. It sat with the chief information officer and was largely invisible to the engineers, lenders and grid operators who decided whether a wind farm, solar plant or battery park could be built and connected. That separation is breaking down.
As inverter-based generation, grid-scale storage and remotely operated assets multiply, the operational technology (OT) that runs a power plant has become both more connected and more consequential. A compromised corporate laptop is a data problem. A compromised plant controller can be an availability, safety and, in the wrong circumstances, system stability problem. Grid operators, insurers and lenders have noticed.
The result is a shift in where cyber resilience sits in the delivery of an energy asset. It is moving out of the IT department and into connection agreements, procurement specifications, commissioning checklists and due-diligence files. For developers, cyber assurance is becoming a condition of doing business rather than a matter of good practice.
The attack surface has moved to the asset
Modern renewable and storage plants are software-defined in ways their predecessors were not. Power conversion systems, plant controllers, SCADA platforms, weather and performance monitoring, remote diagnostics and vendor support tunnels all form part of the operating architecture. A battery site may be supervised from a control centre hundreds of kilometres away.
Each of those connections is useful, and each is a potential path into the plant. The exposure is compounded by aggregation: a single monitoring or dispatch platform may sit above dozens of distributed assets, so a weakness in one layer can reach many sites. Many new assets are also lightly staffed and heavily remote, which makes secure remote access a central design question rather than an add-on.
There is also a physical dimension. Inverter-based resources depend on control systems and communications to deliver the behaviour the network expects. Loss of visibility or an unexpected control action does not simply interrupt generation; it can change how the asset behaves at the point of connection. That is why the conversation has moved to grid operators.
What operators and financiers now ask to see
The evidence requested is becoming more specific. Grid operators assessing a connection application increasingly want to understand the architecture of the plant's control and communications systems and how IT and OT networks are separated. In practice that means documented inventories of assets and network paths, multi-factor authentication and session logging for remote users, time-limited vendor access, and a clear record of who did what and when.
Patch management is a recurring theme, and a difficult one. Control systems cannot always be updated on the same cadence as office software, and some equipment runs for decades. Reviewers therefore ask less about the frequency of patching than about whether there is a managed process, a risk assessment for systems that cannot be updated promptly, and compensating controls where a fix is unavailable.
Incidents response and recovery are examined alongside prevention. Operators want to know how an event would be detected, who would be contacted, how reporting obligations would be met and how control would be restored. Lenders and insurers add their own questions, often framed around business interruption and contractual liability. Supply-chain assurance belongs in the same file: whether manufacturers follow secure development practices, how they disclose vulnerabilities, whether they provide software bills of materials, and how long they will support embedded firmware.
Much of this maps to established references. IEC 62443 provides a common language for industrial automation and control system security, ISO/IEC 27001 covers information security management, and regional regimes such as NERC's critical infrastructure protection standards in North America and the European Union's NIS2 framework set expectations in those markets. The value lies less in choosing one label than in demonstrating that a coherent control set exists and is maintained.
Contracts become the place where cyber risk is allocated
Technical controls only hold if the commercial arrangements around them are clear. In many projects, responsibility for cybersecurity is spread thinly across an owner, an operations and maintenance contractor, an equipment manufacturer and a remote monitoring provider, with no single party accountable for the whole.
The gaps appear at predictable points. Who applies a firmware update issued by the manufacturer? How quickly must a vendor notify the owner of a vulnerability affecting equipment in service? What happens when a product reaches end-of-support during the financing term? What are the liability caps if a remote access channel is misused?
Where these questions are left unanswered, they resurface during commissioning, when a grid operator asks for evidence nobody contracted to produce, or after an incident, when the cost is disputed. Clear allocation of cyber obligations in supply, service and connection agreements is becoming as routine a part of project documentation as performance guarantees and liquidated damages.
Fragmented rules raise the cost of operating across borders
For developers active in several markets, the regulatory picture is uneven. Incidents reporting timelines, definitions of critical infrastructure, security requirements for connected products and the scope of regulated entities all differ between jurisdictions. A portfolio owner may face several reporting regimes for a single event, each with its own threshold and format.
The compliance burden is manageable where a common control framework is used and mapped against local requirements, so that evidence gathered once serves several purposes. Multi-market developers have responded by standardising the questions they ask suppliers and the evidence they retain, then adapting the reporting layer to each jurisdiction.
Assurance as a commissioning discipline
The projects that handle this best treat cyber resilience like any other commissioning requirement. Security obligations are written into procurement specifications rather than added afterwards, tested at factory and site acceptance, and evidenced alongside protection settings and performance tests. The output is a package that can be handed to the operator at takeover and shown to a lender or insurer without a scramble.
Retrofitting later is slower and more expensive, and it often lands mid-connection, when timelines are already tight. Early engagement with the network operator on its security expectations, and with suppliers on support commitments, reduces the risk of a late surprise.
None of this makes cybersecurity a purely technical pursuit. It is a project discipline touching design, procurement, contracts and operations, and the Global Energy Awards category covers work on exactly that ground.
The direction of travel is clear. A grid connection is no longer granted on the strength of capacity, protection and compliance with technical codes alone. Developers are being asked to show that the systems running their assets can be trusted, accessed under control and supported over time. Cyber resilience has become one of the conditions on which energy projects are connected, procured and financed — and it is being tested long before the first megawatt flows.
