November 19, 2026
FERC Order 912 is reshaping utility supply chain risk management and driving NERC’s work on proposed CIP-013-4. The order directs NERC to strengthen how utilities assess and reassess vendor risk, respond to identified risks, and extend protections to additional cyber assets.
For compliance, cybersecurity, procurement, and operational leaders, the message is clear: vendor risk cannot end when the purchase order is approved.
What Does FERC Order 912 Mean for CIP-013?
FERC Order 912 directs NERC to strengthen existing supply chain risk management requirements in several important areas:
- Establish clearer timing between an initial risk assessment and deployment.
- Require periodic reassessment of vendors, products, and services.
- Address supply chain risks associated with spare equipment and emergency repairs.
- Improve how identified risks are documented, tracked, and addressed.
- Extend applicable supply chain protections to Protected Cyber Assets (PCAs).
NERC is addressing these directives through Project 2025-06 Supply Chain Risk Management, which includes development work involving CIP-013 and CIP-010.
However, one distinction is critical: CIP-013-2 is currently subject to enforcement, with CIP-013-3 scheduled to be enforceable on July 1, 2028. Utilities should monitor the progress of the proposed CIP-013-4 as Project 2025-06 evolves.
Therefore, utilities should prepare for the regulatory direction without treating proposed requirements as final.
A Failed First Ballot and Pressure to Reach Agreement
The initial ballot showed how much work remained. When voting closed on July 17, 2026, proposed CIP-013-4 received only 30.64% approval, according to NERC’s published ballot statistics. The associated implementation plan received 31.14%. The proposal therefore fell well short of approval, leaving the standard drafting team with substantial work to build industry consensus.
That setback does not remove FERC’s directive. Order 912 requires NERC to submit new or modified standards within 18 months of its September 18, 2025 issuance, placing the filing deadline in March 2027. Early 2027 is therefore a consequential development window as the team works to resolve comments, revise the language, and complete the approval process
Why CIP-013-4 Points Toward Lifecycle Vendor Risk Management
Utilities already evaluate cyber supply chain risk during procurement. However, risk does not remain static.
For example, a vendor can experience a cyber incident. A new vulnerability can emerge. Ownership can change. Remote access privileges can expand. Software can reach end of life. In addition, a service that once presented limited exposure can become operationally critical.
As a result, compliance teams increasingly need to look beyond the question:
“Did we assess this vendor?”
Instead, they need to answer:
“Is the assessment still valid, what has changed, what risk remains, who owns it, and what did we do about it?”
Existing AssurX guidance on NERC CIP-013 supply chain risk management highlights areas such as vendor incident notification, vulnerability disclosure, access revocation, software integrity, remote access, and documentation.
FERC Order 912 moves that conversation further toward lifecycle vendor risk management rather than a point-in-time procurement exercise.
Supply Chain Risk Goes Beyond the Vendor
A vendor assessment alone cannot explain every exposure associated with the technology a utility uses. The evaluation also needs to reach the specific product or service, its version, and how it is deployed. A reputable supplier can still provide a product with a vulnerability that requires action.
Consider Microsoft as a familiar example. An assessment of Microsoft as a company does not establish the security of every deployment of Word, SharePoint, or Excel. A vulnerability affecting a particular Excel version requires a different evaluation from a SharePoint configuration or support issue. The organization needs to identify the affected product, determine where it is used, assess exposure, and document its response. These examples illustrate the assessment approach; CIP applicability depends on the systems and assets in scope.
For utilities, the same principle applies to control system software, network equipment, firmware, and supporting services. Vendor oversight remains necessary, but product-level context makes it possible to connect a security advisory to the assets and operations that could be affected.
Why FERC Order 912 Makes Supply Chain Risk a Compliance Management Problem
Most utilities already have significant vendor information. The problem is often where that information lives.
For example, vendor assessments may be stored in spreadsheets. Contracts may be maintained by procurement or legal. Meanwhile, vulnerabilities may be tracked in cybersecurity tools, asset information may reside elsewhere, and supporting evidence may sit in SharePoint, email, or department folders.
Consequently, fragmentation becomes a problem when leadership needs to know:
Which vendors currently represent elevated risk? Which products or systems are affected? When was each vendor last assessed? What mitigation is underway? Who owns the next action? And can we prove the process was followed?
FERC Order 912 increases the importance of answering those questions quickly and consistently.
How Should Utilities Prepare for FERC Order 912?
Utilities do not need to wait for CIP-013-4 to become final before preparing for the direction established by FERC Order 912.
1. Establish a Reliable Vendor Inventory
First, identify vendors, products, software, and services that may affect BES reliability or cybersecurity.
Then, establish consistent criteria for classifying vendor risk. Higher-risk suppliers should receive greater due diligence and more frequent oversight.
2. Define Reassessment Triggers
Next, determine what should cause a vendor or product to be reassessed.
Periodic reviews should not depend solely on a calendar. For example, vulnerabilities, cyber incidents, ownership changes, new deployments, remote access changes, major product updates, or end-of-life notifications may justify another review.
3. Connect Vendor Risk to Affected Assets
A vendor risk score provides only part of the picture.
Therefore, teams should understand which products, services, systems, or applicable assets could be affected. That context helps compliance and cybersecurity teams evaluate the actual operational impact of an identified risk.
4. Build a Traceable Risk-Response Process
When a supply chain risk is identified, the process should support a clear sequence:
Identify → Assess → Assign → Respond → Document → Monitor → Close or Accept
As a result, the organization creates both accountability and a defensible record of how the risk was addressed.
5. Bring Stakeholders Into One Governance Process
Finally, supply chain risk should not remain solely within the compliance department.
CIP compliance, cybersecurity, procurement, legal, IT, operations, asset owners, and enterprise risk may all contribute to a single vendor decision.
Therefore, the underlying process should support collaboration without creating another isolated repository of compliance data.
What Should Utilities Look for in Supply Chain Risk Management Technology?
As proposed CIP-013-4 continues to develop, compliance technology should do more than store vendor documentation.
Utilities evaluating a compliance platform should consider whether it can:
- Connect requirements, vendors, risks, controls, activities, and evidence.
- Schedule or trigger recurring risk assessments.
- Assign responsibilities and escalate overdue activities.
- Track mitigation, risk acceptance, and corrective actions.
- Maintain a defensible history of approvals and decisions.
- Provide dashboards for open risks, status, deadlines, and trends.
- Adapt workflows as NERC requirements change.
- Support multiple registered entities or business units.
In other words, the question is not simply whether a system can document CIP-013 compliance.
The more important question is whether it can sustain the process as risks and requirements change.
Building a More Connected Supply Chain Risk Program
AssurX ECOS connects NERC compliance, risk, controls, evidence, mitigation activities, dashboards, and reporting within configurable workflows designed for energy and utility compliance programs.
This connected approach becomes increasingly important as supply chain risk management shifts from a procurement event toward an ongoing compliance process.
Instead of rebuilding the history of a vendor decision before an audit, utilities can establish repeatable workflows in which responsibilities, evidence, risk decisions, mitigation, and follow-up are captured as the work happens.
Additionally, centralized visibility can help compliance leaders identify overdue assessments, unresolved risks, mitigation status, and broader trends without manually reconciling data from multiple systems.
Preparing for What Comes Next
Ultimately, FERC Order 912 reflects a larger reality for the energy industry: supply chain risk changes over time.
Vendors change. Technology changes. Vulnerabilities emerge. Access changes. Regulatory expectations evolve.
Likewise, if the current regulatory direction is ultimately reflected in CIP-013-4, utilities will need processes capable of reassessing risk, documenting decisions, coordinating stakeholders, and producing defensible evidence over the vendor lifecycle.
Organizations that strengthen those capabilities now will be better positioned to adapt as the next generation of CIP supply chain requirements takes shape.
Kathryn Wagner is Vice President, Industry Solutions, Energy & Utilities at AssurX. Kathryn brings more than 25 years of experience in manufacturing systems integration and compliance while being responsible for the development and evolution of product offerings for NERC compliance and related systems that focus on reliability and resilience.


