Guide
Supplier and component oversight under the Act
You answer for the whole product you place on the market, including parts you did not write. Supplier oversight is how you learn about a problem in time to report it.
Last reviewed against European Commission, National Cyber Security Centre Ireland and cyberresilienceact.eu. Sources
What to put in place
Four controls
A component inventory
techUK links vulnerability handling to producing a software bill of materials, and noted there was no consensus on how deep one should go [8]. Start with direct dependencies, then extend.
A flow of advisories
If a flaw stems from a third-party component, the manufacturer must inform the maintainer and share any patch [5]. You also need the reverse: a supplier that tells you quickly about exploitation.
Contract terms
Ask suppliers who the manufacturer is for each part, how they will notify you of exploited flaws and how they support updates.
Evidence for buyers
Importers must check conformity assessment, documentation and CE marking, so they will ask you for evidence [4].
Deciding what to report
Component flaws
A report is needed for a third-party component flaw only if it is actively exploited in your own product [7]. That makes your own telemetry and your supplier's warnings both important.
Test the chain once
Pick one component and walk the path: who finds out, who tells whom, and who decides that you are aware. Fix whatever breaks.

Board view
Reporting upward
Skadden suggests periodic reporting to the board on vulnerability reports and remediation status [5]. For supplier risk, that means a short list of components with no named maintainer.
The open-source guide covers community code, and the gap assessment guide shows how to record what you find.
Keep reading
Read next
What changed
What the EU Cyber Resilience Act reporting start on 11 September 2026 means for UK manufacturers, what is live now and what waits until 2027.
Read the guide
Questions
Sourced answers to what UK organisations ask about the EU Cyber Resilience Act: scope, deadlines, fines, notified bodies, open source and the UK rules.
Read the guide
Who it covers
Work out whether the EU Cyber Resilience Act covers your UK business: manufacturers, importers, distributors, software publishers and what is excluded.
Read the guideHow 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.
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 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
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
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 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
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
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.
