<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/what-did-the-openssf-global-cyber-policy-working-group-learn-in-prague-at-open-source-summit-europe--zyifdqzu2" -->

---
title: What Did The OpenSSF Global Cyber Policy Working Group...
description: The OpenSSF Global Cyber Policy Working Group held a workshop at Open Source Summit Europe in Prague to gather community feedback on CRA compliance work....
canonical: https://daily.dev/posts/what-did-the-openssf-global-cyber-policy-working-group-learn-in-prague-at-open-source-summit-europe--zyifdqzu2
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: What Did The OpenSSF Global Cyber Policy Working Group Learn in Prague at Open Source Summit Europe? | daily.dev
og:description: The OpenSSF Global Cyber Policy Working Group held a workshop at Open Source Summit Europe in Prague to gather community feedback on CRA compliance work....
og:url: https://daily.dev/posts/what-did-the-openssf-global-cyber-policy-working-group-learn-in-prague-at-open-source-summit-europe--zyifdqzu2
og:image: https://api.daily.dev/og/posts/zYIfDqZU2.png
og:image:alt: What Did The OpenSSF Global Cyber Policy Working Group Learn in Prague at Open Source Summit Europe?
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

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

**[OpenSSF](https://daily.dev/sources/openssf)** · 5 min read · 0 upvotes · 0 comments

## Summary

The OpenSSF Global Cyber Policy Working Group held a workshop at Open Source Summit Europe in Prague to gather community feedback on CRA compliance work. Attendees focused on three areas: security due diligence for manufacturers, vulnerability reporting under the Cyber Resilience Act, and collaboration between manufacturers and maintainers on fixes. CRA reporting requirements took effect on 11 September, and many attendees are still working out what they mean in practice. Participants favored upstream-first fixes over private patches, though some manufacturers withhold fixes to avoid revealing which components they use. The group plans more practical guidance on due diligence and vulnerability reporting, building on a recent joint white paper with OpenChain.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://openssf.org/blog/2026/11/19/what-did-the-openssf-global-cyber-policy-working-group-learn-in-prague-at-open-source-summit-europe>

## Questions this post answers

### When did the EU Cyber Resilience Act reporting requirements start applying?

The Cyber Resilience Act reporting requirements started applying on 11 September. Many organizations are still working through what the requirements mean in practice, including how to identify reportable vulnerabilities, how the reporting process works, and how responsibilities differ between manufacturers and open source stewards.

_Track CRA compliance developments and guidance updates as they evolve on daily.dev._

### Why would a manufacturer not want to share a security fix upstream?

Some manufacturers hold back fixes because they worry it reveals which open source components they use in their products, even though there is a clear preference for upstream-first fixes over private patches. Guidance is needed to show the business benefits of sharing fixes beyond compliance, and why doing so does not necessarily expose trade secrets.

_Developers weighing upstream contributions against vendor concerns follow this debate on daily.dev._

### Is an OpenSSF Scorecard score enough to assess the security of an open source dependency?

No, a Scorecard score alone is not enough for due diligence. Manufacturers still need to judge cases such as a project with only one maintainer, or a well-maintained component being used at an outdated version, which a single score does not capture.

_Anyone vetting open source dependencies can keep up with evolving due diligence guidance on daily.dev._

## Similar posts on daily.dev

- [Bridges of Prague: Open Source Summit Europe 2026 Recap](https://daily.dev/posts/bridges-of-prague-open-source-summit-europe-2026-recap-3uosbczsu) · OpenSSF · 0 upvotes · 0 comments
- [OpenSSF Newsletter – July 2026 – Open Source Security Foundation](https://daily.dev/posts/openssf-newsletter-july-2026-open-source-security-foundation-pfg1vkjsr) · OpenSSF · 0 upvotes · 0 comments
- [Making the Cyber Resilience Act Work for Open Source](https://daily.dev/posts/making-the-cyber-resilience-act-work-for-open-source-ri1ckviqk) · The New Stack · 0 upvotes · 0 comments
- [Taking Stock of the State of European Cyber Resilience Act \(CRA\) Compliance: An Urgent Wake-up Call for the Open Source Ecosystem](https://daily.dev/posts/taking-stock-of-the-state-of-european-cyber-resilience-act-cra-compliance-an-urgent-wake-up-call--6yezrqnee) · Linux Foundation · 0 upvotes · 0 comments
- [FOSDEM 2026: Open Source Supply Chains, CRA Compliance, and the Future of Software](https://daily.dev/posts/fosdem-2026-open-source-supply-chains-cra-compliance-and-the-future-of-software-rkr6n5bnz) · Foojay.io · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#open-source](https://daily.dev/tags/open-source)

[View this post on daily.dev](https://daily.dev/posts/what-did-the-openssf-global-cyber-policy-working-group-learn-in-prague-at-open-source-summit-europe--zyifdqzu2)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"What Did The OpenSSF Global Cyber Policy Working Group Learn in Prague at Open Source Summit Europe?","url":"https://daily.dev/posts/what-did-the-openssf-global-cyber-policy-working-group-learn-in-prague-at-open-source-summit-europe--zyifdqzu2","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/what-did-the-openssf-global-cyber-policy-working-group-learn-in-prague-at-open-source-summit-europe--zyifdqzu2"},"datePublished":"2026-11-19T21:23:18.864Z","dateModified":"2026-11-19T21:28:23.315Z","description":"The OpenSSF Global Cyber Policy Working Group held a workshop at Open Source Summit Europe in Prague to gather community feedback on CRA compliance work....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/4e0fea3b3bf18fab9d2985f254f8bce0?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/4e0fea3b3bf18fab9d2985f254f8bce0?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"OpenSSF","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"OpenSSF","logo":"https://media.daily.dev/image/upload/s--l6RJ5uPj--/f_auto,q_auto/v1774959959/logos/openssf?_a=BAMAMiWQ0","url":"https://daily.dev/sources/openssf"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/what-did-the-openssf-global-cyber-policy-working-group-learn-in-prague-at-open-source-summit-europe--zyifdqzu2","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,open-source","timeRequired":"PT5M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"OpenSSF","item":"https://daily.dev/sources/openssf"},{"@type":"ListItem","position":3,"name":"What Did The OpenSSF Global Cyber Policy Working Group Learn in Prague at Open Source Summit Europe?"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/what-did-the-openssf-global-cyber-policy-working-group-learn-in-prague-at-open-source-summit-europe--zyifdqzu2#faq","mainEntity":[{"@type":"Question","name":"When did the EU Cyber Resilience Act reporting requirements start applying?","acceptedAnswer":{"@type":"Answer","text":"The Cyber Resilience Act reporting requirements started applying on 11 September. Many organizations are still working through what the requirements mean in practice, including how to identify reportable vulnerabilities, how the reporting process works, and how responsibilities differ between manufacturers and open source stewards. Track CRA compliance developments and guidance updates as they evolve on daily.dev."}},{"@type":"Question","name":"Why would a manufacturer not want to share a security fix upstream?","acceptedAnswer":{"@type":"Answer","text":"Some manufacturers hold back fixes because they worry it reveals which open source components they use in their products, even though there is a clear preference for upstream-first fixes over private patches. Guidance is needed to show the business benefits of sharing fixes beyond compliance, and why doing so does not necessarily expose trade secrets. Developers weighing upstream contributions against vendor concerns follow this debate on daily.dev."}},{"@type":"Question","name":"Is an OpenSSF Scorecard score enough to assess the security of an open source dependency?","acceptedAnswer":{"@type":"Answer","text":"No, a Scorecard score alone is not enough for due diligence. Manufacturers still need to judge cases such as a project with only one maintainer, or a well-maintained component being used at an outdated version, which a single score does not capture. Anyone vetting open source dependencies can keep up with evolving due diligence guidance on daily.dev."}}]}
```

