CIP-007 R2 patch management for inverter, BESS and RTAC firmware
How CIP-007-6 R2 patch management works for inverter, BESS controller, RTAC and relay firmware: patch sources, 35-day cycles, mitigation plans and evidence.
Patch management guidance is usually written for Windows servers, where updates arrive on a schedule and a tool installs them. Generation sites are different. Much of what matters runs on firmware: inverters, battery management and power conversion controllers, RTACs, protective relays and the switches and firewalls between them. Updates come from many vendors, on no fixed schedule, and often can only be installed during an outage.
CIP-007-6 Requirement R2 still asks for the same process across all of it. This post covers who R2 applies to, what each of its four parts asks, how to handle firmware and vendors that publish no security patches, and what evidence to keep.
Does CIP-007 R2 apply to you?
CIP-007-6 applies to high and medium impact BES Cyber Systems. Section 4.2.3.5 exempts "Responsible Entities that identify that they have no BES Cyber Systems categorized as high impact or medium impact according to the CIP-002-5.1 identification and categorization processes." If every BES Cyber System you own is low impact, R2 does not apply to you.
- Under CIP-002-5.1a criterion 2.1, generation is medium impact when a group of generating units at a single plant location has an aggregate highest rated net Real Power capability of 1500 MW or more in a single Interconnection. Most solar, wind and battery plants are well below that and rate low impact.
- Under criterion 2.11, a Control Center or backup Control Center performing Generator Operator functions for 1500 MW or more in a single Interconnection is medium impact. An operator running a growing fleet from one control room can cross that line, and R2 then applies to that Control Center's systems.
- Where R2 applies, all four parts apply to medium impact BES Cyber Systems and their associated EACMS, PACS and PCA. Unlike some other CIP-007 parts, R2 is not limited to systems with External Routable Connectivity.
- Category 2 inverter-based resources are not BES facilities and are not subject to CIP. Registering one with NERC does not bring CIP-007 with it.
What low impact sites have instead
Low impact sites follow CIP-003-9. Its Attachment 1 has six sections: cyber security awareness, physical security controls, electronic access controls, Cyber Security Incident response, Transient Cyber Asset and Removable Media malicious code risk mitigation, and vendor electronic remote access security controls. None of them is a patch management requirement, and there is no 35-day clock at a low impact site.
The closest point of contact is Section 5. For Transient Cyber Assets you manage, the plan uses antivirus software (including manual or managed updates of signatures or patterns), application whitelisting, or other methods to mitigate the introduction of malicious code. For a vendor's laptop, review of the antivirus update level and of system hardening are among the listed options before it connects. Keeping inverter and controller firmware current is still sound practice at a low impact site; it is simply not audited under CIP-007.
The four parts of R2
- Part 2.1: a patch management process for tracking, evaluating and installing cyber security patches. The tracking portion must identify the source or sources you track for the release of cyber security patches for applicable Cyber Assets "that are updateable and for which a patching source exists."
- Part 2.2: at least once every 35 calendar days, evaluate security patches for applicability that have been released since the last evaluation from the sources identified in Part 2.1.
- Part 2.3: for applicable patches identified in Part 2.2, within 35 calendar days of the evaluation completion, apply the patches, create a dated mitigation plan, or revise an existing mitigation plan. Mitigation plans must include your planned actions to mitigate the vulnerabilities addressed by each security patch and a timeframe to complete them.
- Part 2.4: implement each mitigation plan within the timeframe it specifies, unless a revision to the plan or an extension to the timeframe is approved by the CIP Senior Manager or delegate.
Step 1: list every updateable device and its firmware
R2 depends on knowing what is installed. CIP-010-4 Part 1.1 already requires a baseline configuration for the same high and medium impact systems, including the operating system or "firmware where no independent operating system exists" (1.1.1) and "any security patches applied" (1.1.5). That baseline is the starting point for R2.
For a generation site the list typically includes inverter or power conversion system firmware, battery management and site controller software, RTACs, protective relays, network switches, firewalls, and any Windows HMIs or engineering workstations. Record model and firmware version per device, not per site: two inverters of the same model can run different firmware after a partial replacement.
Step 2: name a patch source for each device
Part 2.1 asks you to identify where you will look. The Guidelines and Technical Basis in CIP-007-6 give the National Vulnerability Database, operating system vendors and control system vendors as examples of sources. In practice, for each device type, write down:
- the vendor's security advisory page, customer support portal or notification list, and who in your team is subscribed to it;
- any third-party sources you also watch, such as CISA's ICS advisories;
- for Windows hosts inside a control system, both the operating system vendor and the control system vendor, where the control system vendor must approve an OS patch before you install it. The guidance notes that the source you document determines when the assessment clock starts;
- for devices with no updateable software or firmware, or whose vendor no longer exists, a short note saying so. The guidance says a patch source is not required for those Cyber Assets.
The Guidelines and Technical Basis section of CIP-007-6 is explanatory guidance from the drafting team, not the requirement text. Where this post draws on it, it says so.
Step 3: evaluate every 35 days, even when nothing changed
Part 2.2 is a recurring check against each source. Count 35 calendar days from the last completed evaluation, not from the first of the month, and record every evaluation, including the ones that found no new releases.
An evaluation decides applicability. The guidance says it is based primarily on whether the patch applies to a component you actually have installed in an applicable Cyber Asset, and that a non-applicable patch is documented with the reasons why. For firmware this usually means checking the release against the exact model and hardware revision: a fix for a communications card you do not have is not applicable, but write that down.
When a vendor publishes no security patches
This is common with OT firmware. Some vendors publish formal advisories; others ship a new firmware version with release notes that mention security fixes in passing; some publish nothing. A few practical steps:
- Treat firmware releases as candidates. If release notes mention a security fix, evaluate the release as a security patch.
- Ask the vendor directly how they notify customers of security fixes, and record the answer as part of your Part 2.1 source list.
- Use procurement. CIP-013-2 Part 1.2.4 requires your supply chain plan to include processes for disclosure by vendors of known vulnerabilities, and Part 1.2.5 covers verification of the integrity and authenticity of software and patches the vendor provides. New contracts are the place to ask for both.
- Where a vendor is gone or a device cannot be updated, document it under Part 2.1 and rely on the device's other CIP-007 controls, such as the ports and services it exposes, while you plan its replacement.
Step 4: apply or mitigate within 35 days
Installing inverter or relay firmware often needs an outage, a vendor visit and testing, which rarely fits inside 35 days. Part 2.3 allows for that: a dated mitigation plan is a compliant outcome. The guidance says it handles situations where patching a running system is a greater reliability risk than the vulnerability, and that timeframes can be event-based, such as "at next scheduled outage of at least two days duration."
A useful mitigation plan names the patch and the vulnerabilities it addresses, the actions already taken and those still planned, and the date or event by which they will be complete. Typical measures for firmware include restricting which systems can reach the device's management interfaces, disabling a vulnerable service or protocol the site does not use, and limiting who can connect engineering software to it. The guidance notes that measures can be cumulative: disabling one service can address several vulnerabilities at once.
The guidance also clarifies that "mitigation plans" in R2 are internal documents, not the plans submitted to Regional Entities after a violation.
Step 5: close the plan on time, or get it approved
Part 2.4 is where plans tend to go stale. Each plan has its own timeframe, and the guidance says there is no maximum timeframe in the requirement, because patching carries its own risk and may need to wait for a planned outage. What matters is that the plan is implemented by the date or event it names, or that a revision or extension is approved by the CIP Senior Manager or delegate before it lapses. Review open plans on the same 35-day rhythm as your evaluations so a missed outage is noticed in time.
A firmware update is also a baseline change
- CIP-010-4 Part 1.2: authorize and document changes that deviate from the existing baseline configuration. Installing new firmware changes item 1.1.1 and usually 1.1.5.
- CIP-010-4 Part 1.6 (high and medium impact BES Cyber Systems and their associated EACMS and PACS): before a change to baseline items 1.1.1, 1.1.2 or 1.1.5, and when the method is available from the software source, verify the identity of the software source and the integrity of the software. A published checksum or signature from the vendor is the usual way to do this.
- Update the baseline afterwards so the next Part 2.2 evaluation starts from what is really installed.
Evidence to keep
- The documented patch management process (Part 2.1).
- The list of patch sources per device or BES Cyber System, including notes for devices with no updateable firmware or no existing source.
- A dated record of each 35-day evaluation, with each release found and the applicability decision and reason.
- For applied patches: installation records, such as the firmware version read back from the device after the work.
- For everything else: each dated mitigation plan, its revisions, any CIP Senior Manager or delegate approvals, and records showing the mitigations were implemented (Part 2.4).
- The CIP-010 change authorization and software verification for each firmware change.
CIP-007-6 asks you to retain evidence of each requirement for three calendar years, unless your Compliance Enforcement Authority directs you to keep it longer. Where that period is shorter than the time since your last audit, the CEA may ask for other evidence covering the full period, so keep the 35-day records in one place that survives staff changes.
Where automated evidence collection helps
The decisions in R2 belong to people: whether a patch is applicable, whether to install it at the next outage or mitigate it, and when. What can be automated is the record those decisions rely on. Reading firmware versions from devices on a schedule gives a dated inventory without anyone typing it in, comparing each collection with the baseline shows when firmware changed, and matching published advisories against that inventory gives the evaluation a starting list. A reading taken after the work is also the installation record.
What changes next
CIP-007-6 is the version audited today. CIP-007-7, part of NERC's virtualization revisions (adopted by the NERC Board of Trustees in May 2024), keeps the same structure for R2, including both 35-calendar-day cycles. Check NERC's implementation plan for when it takes effect at your sites.