/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

An analysis of the EU Cyber Resilience Act, which covers every connected device and almost all software, causing open-source developers to worry about its scope

Bert Hubert's writings Bert Hubert

Context & Ripple Effects

When EU lawmakers proposed the Cyber Resilience Act in September 2022, it was framed as a rulebook for IoT and smart-device makers facing fines for weak security. Bert Hubert's analysis widens that frame dramatically: the Act as drafted covers every connected device and almost all software, which is why open-source developers — not just gadget vendors — are suddenly worried about its scope.

The breadth is consistent with how Brussels has been extending digital regulation: the 2015 rules already forced critical providers to harden infrastructure and report major security incidents, and separate EU plans would require companies to scan for CSAM, alarming privacy experts. The Cyber Resilience Act reads as the next step in that expansion — this time reaching into the code supply chain itself.

First-order effects

  • Open-source developers and maintainers fall within the Act's potential scope, since it covers almost all software, not just commercial IoT products — a compliance burden falling on volunteers who never asked to be regulated vendors.
  • Connected-device makers selling into the EU now face security requirements backed by fines under the Act's original design, extending obligations well beyond the smart-device categories named at proposal time.

Second-order effects

  • Commercial vendors may respond by reducing reliance on open-source components they cannot get warranty or support commitments for, shifting procurement toward commercially maintained code and pressuring foundations to formalize stewardship.
  • The open-source community's alarm becomes a lobbying position: developers and foundations have an immediate stake in pushing Brussels to carve out non-commercial or hobbyist software before the rules harden.

Third-order effects

  • If the pattern holds, EU regulation evolves from policing finished devices toward governing the entire software supply chain — who maintains code, how vulnerabilities are handled, and who carries liability when volunteer-built components ship inside commercial products.
  • The Act joins a broader Brussels arc — CSAM scanning mandates, collective risk assessments on chips and AI, and a tech-sovereignty agenda — suggesting the EU is positioning itself as the de facto global regulator of digital infrastructure, with compliance costs rippling far beyond European borders.

The trend: EU digital regulation is expanding from sector-specific rules toward blanket coverage of connected products and the software supply chain, forcing open-source governance into the compliance conversation.

Discussion

  • @danyork@mastodon.social Dan York on mastodon
    READ THIS if you work with open source and live in the EU!  (And even if you aren't in the EU, you should read it, too!)  —  @bert_hubert explains why the EU's proposed Cyber Resilience Act (CRA) may have started with good intentions, but now may seriously harm open source. …
  • @lukolejnik Lukasz Olejnik on x
    New EU proposal for a regulation may mean the immediate prohibition of shipping and using products or apps if a security vulnerability is found. This is extreme and sounds like censorship. Huge control delegated to untransparent and unelected bodies. https://berthub.eu/...
  • @alecmuffett Alec Muffett on x
    Buggy or not, code is *speech* and state-imposed obligations tread upon prior restraint & chilled speech. Sure, emplace quality standards on industries like medical or aerospace hardware; but across-the-board this approach is illiberal and misconceived. https://berthub.eu/... htt…
  • @kaliszad Adam Kalisz on x
    Great article by @bert_hu_bert illuminating the recent EU Cyber Resilience Act (CRA) proposal https://berthub.eu/... From what I know about most audits and certifications, it would almost certainly make selling or just writing software with occasional donations complete hell.
  • @cartron @cartron on x
    As usual, Bert does an excellent analysis of the CRA and his thoughts on what's good and what could go wrong/be improved. Worth reading! https://twitter.com/...
  • @rafbuff Rafael Laguna de la Vera on x
    If you didn't find the time to dig in to the Cyber Resilience Act but are afraid that it might do something not so clever - as always my friend @bert_hu_bert / @bert_hubert has a very readable explainer about what's going on and what's at stake #OpenSource https://twitter.com/...
  • @kaepora Nadim Kobeissi on x
    If you work in security auditing in the EU, this is an extremely important read. Make sure you read this and pass it on: https://berthub.eu/...
  • @bert_hu_bert Bert Hubert on x
    New post: The EU's new Cyber Resilience Act is about to tell us how to code, and fine us hugely if we don't. https://berthub.eu/...