Eclipse Foundation Launches Free Training Hub to Prepare for EU Cyber Resilience Regulation
On June 30th, in Brussels, the Eclipse Foundation—one of the world’s largest open-source software organizations—announced the launch of a free online training center called the ORC Learning Hub, aimed at preparing the open-source ecosystem for the European Cyber Resilience Act (CRA). This training initiative is designed for developers, maintainers, product teams, and compliance officers, and features an accessible platform hosted at orcwg.org.
The urgency of this training is underscored by the fact that the initial obligations of the CRA will come into effect in September 2026. Up to this point, available guidance has been fragmented, particularly for the open-source community. Yet, open source has become nearly ubiquitous, with over 96% of commercial codebases containing open-source components, according to OpenLogic’s 2026 report on the state of open source. Although the regulation mainly targets the European market, its influence extends globally, as any organization that distributes software products within the EU must comply.
What the CRA Means for the Software Supply Chain
The CRA establishes mandatory cybersecurity requirements for products featuring digital elements sold in the EU, including those developed with or relying on open-source software. It places new responsibilities on manufacturers and distributors of these products. Key obligations include reporting known vulnerabilities, managing patches, and ensuring transparency regarding components.
A notable aspect of the regulation is the introduction of the role of the open-source software manager. This new role will be responsible for adopting secure development practices, maintaining traceability of components, and addressing vulnerabilities throughout the software supply chain. Responsibility now extends beyond the commercial publisher to include the communities that create the foundational software components used downstream.
A Modular Program Tailored by Role
The training center is structured around five modules designed to guide organizations through compliance step by step. The first module introduces the CRA as it pertains to open-source software, while the second focuses on manufacturers. The remaining three modules cover Software Bill of Materials (SBOM), vulnerability management in open source, due diligence under the regulation, and practical aspects of vulnerability remediation.
At launch, two modules are immediately available: one for open-source developers and another for manufacturers. These modules provide tailored entry points depending on the audience, from developers to legal professionals. The components focusing on SBOM, due diligence, and remediation will be released subsequently. The Open Regulatory Compliance Working Group (ORC WG) consists of over fifty members, including open-source foundations, international companies, and sectoral stakeholders, with their initial focus on the CRA.
Why CIOs Should Pay Attention
Chief Information Officers (CIOs) encounter open source in nearly all their applications. Consequently, the CRA’s scope directly impacts their supply chain, even if they do not produce any proprietary software. Mapping these dependencies, requiring a component inventory, and verifying supplier due diligence are becoming concrete compliance tasks.
“The CRA changes the rules around how software is developed and delivered on a global scale,” said Mike Milinkovich, Executive Director of the Eclipse Foundation. “Compliance must happen where the software is actually built.” For Chief Information Security Officers (CISOs), this role-based training fosters a common language among development teams, legal departments, and compliance officers as accountability for cybersecurity increasingly rises to the executive level.
As the September 2026 deadline approaches, the window for preparation shrinks. By launching a free resource tailored specifically for the open-source community, the Eclipse Foundation and the ORC are addressing a gap left by broader guidance. Now, organizations must translate these modules into internal actions, from component inventorying to continuous vulnerability monitoring, before the initial obligations become enforceable.



