<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[GridSafe: NERC CIP and OT Security Notes]]></title><description><![CDATA[GridSafe: NERC CIP and OT Security Notes]]></description><link>https://gridsafe.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6af2a5e308a1dfdbaf63b4d5/97756c75-16ba-47c5-8c9e-5bda139ae8ce.png</url><title>GridSafe: NERC CIP and OT Security Notes</title><link>https://gridsafe.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 15:29:21 GMT</lastBuildDate><atom:link href="https://gridsafe.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[NERC CIP compliance for solar operators: where to start]]></title><description><![CDATA[Registration, impact rating, the CIP-003 low impact plan and its evidence: the order to work in when a solar portfolio comes into NERC CIP scope.]]></description><link>https://gridsafe.hashnode.dev/nerc-cip-compliance-for-solar-operators-where-to-start</link><guid isPermaLink="true">https://gridsafe.hashnode.dev/nerc-cip-compliance-for-solar-operators-where-to-start</guid><category><![CDATA[cybersecurity]]></category><dc:creator><![CDATA[GridSafe Technology]]></dc:creator><pubDate>Fri, 13 Nov 2026 21:04:14 GMT</pubDate><content:encoded><![CDATA[<p>Most solar operators meet NERC CIP the same way: a registration letter, a deadline, and a set of standards written with substations and large control centers in mind. The work is manageable if you do it in the right order. This is that order.</p>
<h2>1. Confirm what you are registered as</h2>
<p>CIP obligations follow registration. A Generator Owner (GO) or Generator Operator (GOP) on the NERC Compliance Registry has CIP obligations for the BES Cyber Systems at its facilities; an entity that is not registered does not.</p>
<p>NERC's revised registration criteria for inverter-based resources bring many solar, wind and battery storage owners onto the registry for the first time. Which standards apply to a newly registered category, and from when, is set out in NERC's implementation plan — confirm your list with your Regional Entity rather than assuming the full CIP family applies on day one. NERC's own Security Guideline for Inverter-Based Resources notes that newly registered Category 2 IBRs are not individually BES facilities and so, as of early 2026, are not subject to the existing CIP standards.</p>
<h2>2. Rate impact with CIP-002</h2>
<p>CIP-002-5.1a sorts BES Cyber Systems into high, medium and low impact using bright-line criteria in its Attachment 1. A generating plant becomes medium impact under criterion 2.1 only when the units at a single plant location add up to 1,500 MW or more in one Interconnection, so almost every individual solar site rates low impact.</p>
<p>The place to look harder is the operations center. Criterion 2.11 rates a Control Center medium impact when it performs Generator Operator functions for 1,500 MW or more in a single Interconnection. A fleet of low-impact sites can therefore be run from a medium-impact control room.</p>
<p><em>For low impact, CIP-002 asks you to identify each asset that contains a low impact BES Cyber System. A device-by-device list of low impact BES Cyber Systems is not required.</em></p>
<h2>3. Write the CIP-003 policy and low-impact plan</h2>
<p>Low impact does not mean no obligations. CIP-003-9 requires documented cyber security policies (R1), a named CIP Senior Manager (R3) whose approval the policies need at least once every 15 calendar months (R1), and one or more cyber security plans for your low impact BES Cyber Systems that cover the sections of Attachment 1 (R2):</p>
<ul>
<li>Section 1 — cyber security awareness, reinforced at least once every 15 calendar months.</li>
<li>Section 2 — physical security controls for the asset and its low impact BES Cyber Systems.</li>
<li>Section 3 — electronic access controls: permit only the routable communication that is needed, inbound and outbound, and authenticate dial-up.</li>
<li>Section 4 — cyber security incident response, including testing the plan at least once every 36 calendar months.</li>
<li>Section 5 — transient cyber assets and removable media, which at a solar site usually means O&amp;M and vendor laptops and USB drives.</li>
<li>Section 6 — vendor electronic remote access security controls, added in CIP-003-9.</li>
</ul>
<h2>4. Look for the paths nobody drew</h2>
<p>The gaps that surface at solar sites tend to be connections added for operations rather than designed in: a cellular modem an inverter or tracker vendor uses for remote support, a second internet circuit for the monitoring portal, a contractor laptop moved between sites. Each is a routable path or a transient device that Sections 3, 5 and 6 expect you to control and document.</p>
<p>Walk each site's communications with the people who installed them, and write down every path in and out with the reason it exists. That list becomes your electronic access rules.</p>
<h2>5. Plan for evidence, not just documents</h2>
<p>An auditor reads the plan and then asks to see it working: current firewall or router configurations that match the documented rules, awareness records, the incident-response test, the transient-device process in use, vendor remote-access records. Collecting that continuously is far less work than reconstructing a year of it before an audit.</p>
<h2>How GridShield helps</h2>
<ul>
<li>Collects firewall and router configurations read-only over SSH or vendor REST APIs, and receives syslog in real time.</li>
<li>Reads SunSpec and Sungrow inverters over Modbus TCP with read requests only; it never sends a write.</li>
<li>Keeps every record SHA-256 hash-chained per asset in the Evidence Vault and fills RSAW worksheets from it for your team to review.</li>
<li>CIPStart covers the CIP-003-9 low-impact plan, Attachment 1 sections 1–6.</li>
</ul>
<h2>Sources</h2>
<ul>
<li><a href="https://www.nerc.com/pa/Stand/Pages/ReliabilityStandards.aspx">NERC Reliability Standards (CIP family)</a></li>
<li><a href="https://www.nerc.com/pa/comp/Pages/Registration.aspx">NERC Compliance Registry</a></li>
<li><a href="https://www.nerc.com/globalassets/our-work/guidelines/security/1_09_sites_sg_ibr_finaldraft_clean.pdf">NERC Security Guideline: Inverter-Based Resources</a></li>
</ul>
<p>This post first appeared on the <a href="https://gridsafetech.com/blog/nerc-cip-compliance-for-solar-operators/">GridSafe blog</a>.</p>
]]></content:encoded></item><item><title><![CDATA[Low impact or medium impact? Where NERC CIP impact ratings go wrong]]></title><description><![CDATA[Five places operators of solar, wind and storage misread CIP-002, and what each mistake costs in requirements you did or did not need to meet.]]></description><link>https://gridsafe.hashnode.dev/low-impact-or-medium-impact-where-nerc-cip-impact-ratings-go-wrong</link><guid isPermaLink="true">https://gridsafe.hashnode.dev/low-impact-or-medium-impact-where-nerc-cip-impact-ratings-go-wrong</guid><dc:creator><![CDATA[GridSafe Technology]]></dc:creator><pubDate>Wed, 11 Nov 2026 15:59:06 GMT</pubDate><content:encoded><![CDATA[<p>The impact rating decides almost everything else in a NERC CIP program: which requirements apply, how much evidence you keep and what an audit looks at. CIP-002-5.1a's bright-line criteria are short, but they are easy to misread. These are the mistakes that come up most for generation operators.</p>
<h2>1. Rating the sites and forgetting the control room</h2>
<p>A single solar or wind plant reaches medium impact under criterion 2.1 only at 1,500 MW or more at one plant location in one Interconnection. That threshold is rarely met, so operators conclude the whole program is low impact.</p>
<p>Criterion 2.11 is separate: a Control Center or backup Control Center that performs Generator Operator functions for 1,500 MW or more in a single Interconnection is medium impact. As a portfolio grows, the remote operations center can cross that line while every site stays low. Re-check it every time capacity is added.</p>
<h2>2. Treating the rating as a one-time decision</h2>
<p>CIP-002 R2 requires a review of the identifications at least once every 15 calendar months, with the CIP Senior Manager's approval. New plants, repowering, a backup control center and a change of operator all move the numbers. A rating that was right at registration can be wrong two years later.</p>
<h2>3. Building a device list nobody asked for</h2>
<p>For low impact, CIP-002 R1 asks you to identify each asset — the plant or facility — that contains a low impact BES Cyber System. The standard says a discrete list of low impact BES Cyber Systems is not required.</p>
<p>An inventory is still good practice and makes the CIP-003 plan easier to defend. But it should not delay the obligations that are required: the policy, the plan and the controls in CIP-003 Attachment 1.</p>
<h2>4. Assuming low impact means little to do</h2>
<p>Low impact sites still need the CIP-003-9 plan: awareness, physical security, electronic access controls, incident response with a test every 36 calendar months, transient cyber assets and removable media, and vendor electronic remote access controls. Each of these needs evidence that it is in place, not only a written procedure.</p>
<h2>5. Ignoring External Routable Connectivity at medium impact</h2>
<p>Once a system is medium impact, many requirements apply only when it has External Routable Connectivity (ERC) — for example the interactive remote access requirements in CIP-005. CIP-015-1, the internal network security monitoring standard, applies to high impact BES Cyber Systems and to medium impact BES Cyber Systems with ERC.</p>
<p>Whether a medium impact system has ERC therefore changes both today's requirements and the monitoring you will need when CIP-015-1 takes effect. Document the routable paths and the reasoning, because the answer is something an auditor will test.</p>
<h2>What to do this quarter</h2>
<ul>
<li>List every control center and backup control center and the MW each one operates, per Interconnection.</li>
<li>Put the next CIP-002 review date on the calendar, inside 15 calendar months of the last one.</li>
<li>For each medium impact system, record whether it has External Routable Connectivity and why.</li>
<li>Check that every low impact asset is covered by a CIP-003-9 plan with all six Attachment 1 sections.</li>
</ul>
<h2>How GridShield helps</h2>
<ul>
<li>CIPStart's BES impact wizard applies the CIP-002-5.1a bright-line criteria, takes the highest match, and records an approval step.</li>
<li>CIPStart's compliance calendar tracks 15-month review cycles.</li>
<li>GridShield builds the asset inventory from read-only collection and keeps the evidence hash-chained per asset.</li>
</ul>
<h2>Sources</h2>
<ul>
<li><a href="https://www.nerc.com/pa/Stand/Pages/ReliabilityStandards.aspx">NERC Reliability Standards (CIP family)</a></li>
</ul>
<p>This post first appeared on the <a href="https://gridsafetech.com/blog/nerc-cip-low-vs-medium-impact/">GridSafe blog</a>.</p>
<p><em>One NERC CIP and OT security point a day: <a href="https://www.youtube.com/@gridsafetech">short videos on YouTube</a> and <a href="https://www.linkedin.com/company/gridsafe-technology/">posts on LinkedIn</a>.</em></p>
]]></content:encoded></item><item><title><![CDATA[BESS cybersecurity and NERC CIP: what battery storage owners should check]]></title><description><![CDATA[When a battery site is under NERC CIP, it is usually low impact. What CIP-003-9 asks of a BESS, and the vendor access paths that need the most care.]]></description><link>https://gridsafe.hashnode.dev/bess-cybersecurity-and-nerc-cip-what-battery-storage-owners-should-check</link><guid isPermaLink="true">https://gridsafe.hashnode.dev/bess-cybersecurity-and-nerc-cip-what-battery-storage-owners-should-check</guid><category><![CDATA[cybersecurity]]></category><dc:creator><![CDATA[GridSafe Technology]]></dc:creator><pubDate>Tue, 10 Nov 2026 05:34:19 GMT</pubDate><content:encoded><![CDATA[<p>Battery energy storage sites are being built fast, and many of them sit on the same interconnections as solar plants. Their security questions are a little different from a solar or wind site, because a battery does not only produce power. It charges and discharges on command, and the commands arrive over a network.</p>
<p>This post covers how to tell whether a battery site is under NERC CIP, what the low impact requirements ask of it, and where battery sites tend to have the most vendor access to account for.</p>
<h2>First: is the battery site under CIP at all?</h2>
<p>Two questions decide this.</p>
<ul>
<li>Is it a BES facility? Plants that are BES facilities, which for these resources means more than 75 MVA in aggregate connected at 100 kV or higher, are under the CIP standards. NERC's registration reference on applying the BES definition to battery storage and hybrid resources (Version 2, April 30, 2026) treats batteries as dispersed power producing resources under Inclusion I4. On a hybrid site, the solar and battery capacity count together: its example of 50 MVA of solar plus 20 MVA of storage comes to 70 MVA, below the threshold. Read it for your configuration and confirm the answer with your Regional Entity rather than assuming.</li>
<li>Is it newly registered as Category 2? Since May 15, 2026, owners and operators of smaller inverter-based resources register with NERC as Category 2 Generator Owners and Operators. Category 2 IBRs are not BES facilities and are not subject to the CIP standards today. They follow a set of operating and planning standards instead. Registration alone does not bring CIP with it.</li>
</ul>
<p>If the site is a BES facility, CIP-002 rates its BES Cyber Systems. Most generation sites, battery sites included, come out at low impact. A control center that dispatches a fleet may be rated differently, and that is a separate assessment.</p>
<h2>What a low impact battery site is asked to do</h2>
<p>For low impact BES Cyber Systems, the program lives in CIP-003-9. Requirement R1.2 sets the policy topics, and Requirement R2 requires a documented cyber security plan that includes the sections in Attachment 1:</p>
<ul>
<li>Section 1: security awareness, reinforced at least once every 15 calendar months.</li>
<li>Section 2: physical security controls for the asset (or the locations of the low impact systems within it) and for the Cyber Assets that provide the electronic access controls.</li>
<li>Section 3: electronic access controls that permit only necessary inbound and outbound electronic access, for routable communication between a low impact BES Cyber System and Cyber Assets outside the asset.</li>
<li>Section 4: a cyber security incident response plan, tested at least once every 36 calendar months.</li>
<li>Section 5: controls for Transient Cyber Assets (laptops) and Removable Media.</li>
<li>Section 6: vendor electronic remote access: methods to determine it, to disable it, and to detect known or suspected malicious communications on it.</li>
</ul>
<p>The standard also notes that an inventory of low impact BES Cyber Systems is not required. Evidence is organized by asset, meaning the site, not by device.</p>
<p>CIP-003-9 is the version in effect today. NERC's list of approved future versions has CIP-003-10 taking effect on July 1, 2028 and CIP-003-11 on July 1, 2029, so the low impact program will keep changing; we will update this post when they apply.</p>
<h2>Why battery sites need extra care on Sections 3 and 6</h2>
<p>A typical battery site has several layers of control equipment, often from different suppliers:</p>
<ul>
<li>a battery management system for each rack or container;</li>
<li>power conversion systems (the inverters);</li>
<li>a site or plant controller and an energy management system that decide when to charge and discharge;</li>
<li>auxiliary systems: HVAC, fire detection and suppression, and metering.</li>
</ul>
<p>The dispatch signal may come from a utility, an ISO or a market operator. The integrator may watch performance from its own monitoring service. A long-term service agreement may give the battery maker, the inverter maker and the O&amp;M contractor their own paths in.</p>
<p>Each of those is a routable flow crossing the site boundary, which is exactly what Section 3 asks you to justify, and several of them are vendor electronic remote access, which is what Section 6 covers. On a solar site there may be one or two vendors with remote access. On a battery site there can easily be more, and each one needs to be determined, able to be disabled, and watched.</p>
<h2>Questions to ask your integrator and service providers</h2>
<p>These are worth asking before the contract is signed, and again at commissioning:</p>
<ul>
<li>Which parties have remote access to the site, through which path, and to which systems?</li>
<li>Is any of that access always on, or is it enabled per session?</li>
<li>How do we switch a given vendor's access off quickly, and who on our side can do it?</li>
<li>What logs exist for vendor sessions, where are they kept, and can we get them without asking the vendor?</li>
<li>Does the battery or inverter maker's monitoring service connect out from the site, and what can it send in?</li>
<li>Which laptops and USB media will technicians bring for commissioning, firmware updates and augmentation, and how will we check them before they connect (Sections 5.1 to 5.3: your own laptops, vendors' laptops, and removable media)?</li>
<li>What security changes, if any, does the equipment maker support on its controllers? Avoid installing software that the maker does not support.</li>
</ul>
<h2>Records worth keeping from day one</h2>
<p>Low impact audits are about showing the plan works over time. For a battery site, that usually means:</p>
<ul>
<li>a current diagram of every routable flow in and out of the site, with the business reason for each;</li>
<li>the firewall or access-control rules that enforce it, with dated copies when they change;</li>
<li>a log of vendor remote access: who, when, to what, and when it was switched off;</li>
<li>records of laptop and removable media checks before each site visit;</li>
<li>physical access records for containers and control buildings;</li>
<li>the dated incident response test, and any plan update that followed it.</li>
</ul>
<p>CIP-003-9 asks you to keep evidence for three calendar years unless your Compliance Enforcement Authority asks for longer. Records collected as the work happens are much easier to defend than ones rebuilt before an audit.</p>
<h2>Where GridSafe fits</h2>
<ul>
<li>GridShield is being built for unstaffed generation and storage sites.</li>
<li>It collects configuration and log evidence read-only, so it does not change device settings, and compares each collection with the device's baseline so a change shows up for a person to review.</li>
<li>Records go into a hash-chained Evidence Vault, so you can show a record has not been altered since it was collected.</li>
<li>CIPStart keeps the CIP-003-9 low impact plan section by section, with a vendor-access log you can list and export to CSV.</li>
<li>GridShield is pre-launch; if you would like to see how it handles a low impact battery site, contact us through gridsafetech.com.</li>
</ul>
<h2>Sources</h2>
<ul>
<li><a href="https://www.nerc.com/pa/Stand/Reliability%20Standards/CIP-003-9.pdf">NERC Reliability Standard CIP-003-9, Cyber Security - Security Management Controls (incl. Attachments 1 and 2)</a></li>
<li><a href="https://www.nerc.com/pa/Stand/Reliability%20Standards/CIP-002-5.1a.pdf">NERC Reliability Standard CIP-002-5.1a, Cyber Security - BES Cyber System Categorization</a></li>
<li><a href="https://www.nerc.com/globalassets/programs/registration/registration-documentation/application-of-the-bulk-electric-system-definition-to-battery-energy-storage-systems-and-hybrid-resources.pdf">ERO Enterprise Registration Reference, Application of the Bulk Electric System Definition to Battery Energy Storage Systems and Hybrid Resources (Version 2, April 30, 2026)</a></li>
</ul>
<p><em>Originally published at <a href="https://gridsafetech.com/blog/bess-cybersecurity-compliance/">gridsafetech.com</a> by the GridSafe Team.</em></p>
]]></content:encoded></item></channel></rss>