Regulation

European open source community demands clearer guidance on EU cybersecurity rules

At Open Source Summit Europe, the OpenSSF's policy working group found that developers and manufacturers are deeply engaged with the Cyber Resilience Act but need practical help understanding how to comply.

4 min read
What Did The OpenSSF Global Cyber Policy Working Group Learn in Prague at Open Source Summit Europe?

The OpenSSF Global Cyber Policy Working Group convened a workshop at Open Source Summit Europe to present its recent work and solicit input from the open source community on future priorities. The takeaway was unmistakable: European open source practitioners are closely following cybersecurity policy developments, with particular focus on the Cyber Resilience Act (CRA). Multiple sessions throughout the conference addressed CRA topics, and a Standards and Specifications track session titled "The EU Cyber Resilience Act and Open Source: What Product Vendors Must Do," presented by Timo Perala and Gergely Csatari of Nokia, drew standing-room-only attendance.

The working group's workshop assembled equipment manufacturers, open source maintainers, foundations, and industry participants to examine three critical topics: security due diligence practices, vulnerability disclosure procedures, and collaboration between manufacturers and maintainers. The session was similarly oversubscribed.

Security due diligence: what guidance do manufacturers lack?

The OpenSSF has already released guidance for manufacturers regarding CRA reporting requirements, along with separate resources for maintainers and stewards. However, workshop participants made clear that additional direction on due diligence is essential.

Manufacturers need clearer frameworks for evaluating the open source components they incorporate and determining appropriate responses when assessments reveal problems. While tools like OpenSSF Scorecard provide a foundation, a numerical score alone does not address real-world scenarios. Manufacturers face concrete questions: what steps should they take if a project relies on a single maintainer, or if they are running an outdated version of otherwise well-maintained software? How can smaller organizations access actionable intelligence without developing proprietary assessment infrastructure?

Embedded systems present particularly acute challenges. Workshop participants expressed strong interest in pooling information across organizations to eliminate redundant effort. A key insight for the working group's roadmap emerged: existing tools and data sources should be better integrated, and valuable information should be made more discoverable and accessible.

Vulnerability reporting under the CRA: outstanding questions

The CRA's vulnerability reporting obligations, which took effect on 11 September, have generated substantial confusion. Organizations are still interpreting what the requirements mean in operational terms, including how to classify reportable vulnerabilities, execute the reporting process, and distinguish roles between manufacturers and open source stewards.

The working group has published a manufacturer reporting guide and a resource guide for stewards, but workshop discussion indicated that additional practical clarification would be valuable. Participants particularly need guidance on how upstream and downstream entities should coordinate when vulnerabilities emerge.

Bridging the gap between manufacturers and maintainers

The workshop also examined the working relationship between manufacturers and the maintainers of open source projects they depend on. Maintainers seek vulnerability reports that supply sufficient detail to reproduce issues, pinpoint affected versions, and assess severity. Manufacturers, conversely, require the ability to deliver fixes to their customers. Workshop participants strongly favored developing and releasing fixes upstream rather than maintaining proprietary patches.

Current practice often diverges from this ideal. Some manufacturers withhold fixes out of concern that disclosure would expose their component dependencies. Enterprise open source practitioners may benefit from additional guidance and support to build internal cases for upstream-first security responses, including articulating business advantages beyond CRA compliance and explaining why sharing fixes does not necessarily compromise proprietary information.

Both the due diligence and collaboration discussions surfaced the problem of unresponsive maintainers and dormant projects. Foundations and similar organizations may offer assistance, but no straightforward solutions exist. The working group's CRA guidance for maintainers and developers provides a starting point, though additional practical advice in this area would be beneficial.

Where the working group focuses next

The workshop confirmed that the community is attentive to these issues and eager to participate in addressing them. It also clarified the working group's strategic direction.

Several priorities have crystallized: producing more actionable guidance on due diligence, offering expanded support for vulnerability reporting, and establishing better mechanisms for security information flow among manufacturers, maintainers, and stewards. The working group should also coordinate with other organizations and foundations to build on existing tools and resources rather than duplicating effort. A recent joint white paper with OpenChain exemplifies this collaborative approach, and similar partnerships should be pursued.

The working group extends thanks to workshop participants for sharing their perspectives. The conversation proved valuable, and substantial work remains ahead. Those interested in these topics are encouraged to explore the working group's policy resources and consider participating in its efforts.

Source: OpenSSF · Reporting supplemented by The Silicon Ledger staff.