Guide

Open-source software and the Act

Contributing code does not make you a manufacturer. Responsibility depends on who publishes and controls a project, and on whether it is supplied commercially.

Last reviewed against European Commission, National Cyber Security Centre Ireland and cyberresilienceact.eu. Sources

A person holding two ends of a broken chain together

The basics

Stewards and manufacturers

Reporting duties extend to open-source software stewards from 11 December 2027 [2]. Fines do not apply to infringements by stewards, under Article 64(10) [4]. A commercial publisher that ships open-source code inside its product is a different case: the product, and its manufacturer, are in scope.

Commercial lines

What the guidance says

The Commission's final guidance, as summarised by Hogan Lovells Cadwalader, makes three points [7].

A tangled green cable between a start point and an arrow

Contributors

Contributing code does not by itself make someone a manufacturer or a steward. It depends on who publishes and controls the project [7].

A lifebuoy held out to a hand rising from a pile of paperwork

Community and paid editions

A community edition can remain outside commercial scope even if a paid edition exists [7].

A desk monitor showing a plant control screen with a padlock beside it

Services

Separately sold consulting or training does not by itself make the software commercial [7].

For your products

Using community code

If you build on open-source libraries, you carry the product duties for what you ship. If a vulnerability stems from a third-party component, you must inform its maintainer and share any patch [5]. A report to the authorities is needed only where the flaw is actively exploited in your own product [7].

Keep a trail to the maintainer

Record who maintains each component and how you reach them. The duty to pass on a patch is hard to meet if you cannot identify the project.

A padlock with a tick on a hexagonal platform

Practical steps

Before December 2027

Compile an inventory of components, because techUK links vulnerability handling to producing a software bill of materials [8]. Then decide, per component, who watches for advisories and who contacts the maintainer. Where the same library appears in several products, assign one owner so that a single advisory does not trigger several uncoordinated responses.

The supplier oversight guide covers contractual controls, and the software guide covers scope.

How CyPro can help

Need a hand getting ready?

Reading the rules is one job. Mapping them to your organisation, closing the gaps and showing the evidence are several more. CyPro's consultants can take any of them off your plate.

Security lead advising a board

Fractional CISO for the board

A senior security lead who advises the board on what to fix first, what to accept and what to tell customers, and owns the decision record.

More on cypro.co.uk
Penetration tester probing an application for weaknesses

Penetration testing

A focused test of your systems and the controls around them, so you know they hold before an attacker finds out for you.

More on cypro.co.uk
Cyber security consultants planning hardening work

Hardening and segmentation

Our consultants put the controls in place that limit the damage when something is missed: firewall rules, network isolation and tighter admin access.

More on cypro.co.uk
Security analysts monitoring systems around the clock

24/7 security monitoring

Our SOC analysts watch your systems day and night for the signs of an attack in progress: unexpected processes, new outbound connections, logins that do not fit.

More on cypro.co.uk
Incident responders containing an attack

Incident response

If you may already be compromised, our responders contain it, preserve the evidence, find out what was touched and get you running again safely.

More on cypro.co.uk
Scanner checking internet-facing systems for weaknesses

Vulnerability scanning

Find every internet-facing system you run, including the forgotten ones, and see which are still on a vulnerable build.

See the scanning service
Rocket launching from a cloud

Get ready

Need to know what this means for you?

Meeting the Act takes a named owner for product security, a decision path for reporting and a plan to 2027. A virtual CISO can take that role, assess which products are in scope and report progress to your board.