Open Source Regulators Move From Guidance to Audit Requests

Archi4 min read

regulationsoftwaresecurityeurope

Contents
  1. The First Enforcement Wave Looks Like Procurement
  2. What the questionnaires ask
  3. The guidance gap
  4. The incident clock starts before the patch
  5. Penalties are late-stage risk
  6. What regulators will test first

The First Enforcement Wave Looks Like Procurement#

European market surveillance authorities are moving open source from the policy footnote to the audit file. The Cyber Resilience Act sets the timetable: vulnerability reporting duties apply from September 2026, and the main product obligations apply from December 2027. Regulators will not clone every repository. They will follow products into the market, then ask manufacturers to show the components inside.

That shift changes the first contact. A maintainer is more likely to see a supplier questionnaire than a formal inspection notice. A foundation is more likely to get a request for its security policy than a subpoena. The work will look like procurement, because procurement is where regulators and large buyers already test claims.

What the questionnaires ask#

The first requests will be familiar to anyone who has sold into a regulated market: technical documentation, a software bill of materials, a vulnerability handling process, an update policy and a named security contact. Regulators will ask which versions shipped, which versions remain supported, and how a patch reaches a device after the sale.

For open source components, the weak point is often the handoff. A manufacturer may know the library name but not the version. It may know the version but not the maintainer. It may know the maintainer but not the support window. A spreadsheet with a commit hash and no owner fails the first review.

The Cyber Resilience Act also creates a category for open source stewards. A foundation that provides support and coordination can carry duties that an individual contributor does not. Regulators will draw the line around commercial activity: paid support, hosted builds, custom features, warranty terms. A hobby project can sit outside the product rules, but the manufacturer that ships it cannot outsource its own due diligence.

The guidance gap#

Regulators are writing guidance faster than harmonised standards arrive. Market surveillance authorities will lean on existing frameworks: coordinated vulnerability disclosure, secure development life cycle, SBOM formats. They will also ask for evidence that a component's support window matches the product's expected life. A five-year warranty on a device with a two-year library support commitment invites questions. Open source foundations are asking for clear safe harbours for non-commercial work. Regulators have not finished that map. Until they do, the practical answer is documentation that separates the community project from the commercial distributor.

The incident clock starts before the patch#

Reporting duties will force maintainers and manufacturers to keep better timestamps. Regulators will want an early warning within 24 hours of becoming aware of an actively exploited vulnerability, a fuller notification within 72 hours, and a final report later. The exact forms will vary by authority, but the sequence is clear. A public advisory posted a week after the fix will be easy to compare against the clock.

That is where volunteer projects feel the strain. Many maintainers handle security reports in personal email and publish fixes when a release train allows. Regulators will not accept that as a process if the component sits in a regulated product. They will ask who received the report, when the maintainer confirmed it, and what the manufacturer did next.

Penalties are late-stage risk#

Fines and market restrictions give the rules teeth, but they arrive after the requests and the corrective action plans. The nearer risk is a stalled shipment. A missing SBOM can hold up a conformity assessment. A vague vulnerability policy can turn a routine buyer review into a six-week exchange. Regulators can order a product withdrawn or recalled, and they can publish enough of the case to affect the next tender.

Small vendors will feel this first. They often assemble products from open source parts and have no staff to trace every license and patch. Large vendors have legal teams and supplier portals. The gap between them will show up in the paperwork, not in the code.

What regulators will test first#

Three tests are likely. First, can the manufacturer name the open source components in a shipped product and their versions? Second, can it show a route for vulnerability reports and a record of fixes? Third, can it explain who is responsible when a component is maintained by a volunteer, a foundation or a commercial steward?

The answers will be dull: a maintained inventory, a security contact that works, a release log, a support statement. Regulators will not reward a manifesto. They will check whether the evidence survives a request from an authority that has a product, a deadline and a lawyer.

Maintainers can prepare without pretending to be manufacturers. Publish a security policy. Keep a machine-readable dependency list. State the supported versions. Record how reports arrive. Foundations can run legal clinics and template notices. Manufacturers can stop treating open source as a free input with no paperwork. The first audit letter will find the projects that wrote down their process and the ones that trusted memory.

More articles