Getting ready

How to prepare for the EU Cyber Resilience Act

Begin with decisions rather than engineering: what you sell in the EU, and who acts if it is attacked. Design and documentation work can follow in sequence.

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

A brick wall with a flame burning through the middle

Principle

People before process

Because reporting is already live, the first steps concern ownership. Skadden's checklist starts with product mapping, then plans and governance, then decision-making, then named staff and escalation [5].

Sequence

Five steps

Take the steps below one after another, and keep a note of every decision.

  1. 1

    Map every product and supporting back-end service on the EU market, and identify the regulated manufacturer for each [5].
  2. 2

    Update incident response and vulnerability management plans, and define when a CRA notification also triggers another regulatory notice [5].
  3. 3

    Set procedures that can meet the 24-hour and 72-hour windows, then rehearse them [5].
  4. 4

    Name responsible staff, backups and an escalation path [5].
  5. 5

    Measure the gap to the essential requirements, product by product, using the gap assessment guide.

The action cards below set out who owns each step.

Easy to miss

Common weak spots

A hooded figure at a laptop surrounded by alerts, a bug and bank cards

Reporting overlaps with other regimes

CRA reporting is additional to UK and EU GDPR breach reporting, so one incident can start several clocks [6]. Write the sequence down in advance.

Two server racks in front of a cloud with a padlock and a shield

Older products

Reporting applies to products placed on the market before 11 September 2026 [5]. Old lines are the easiest to leave off the list.

A hooded figure holding up several masks

Third-party components

If a flaw sits in a component such as an open-source library, you must tell its maintainer and share any patch [5]. The supplier guide covers the contractual side.

Also check

Items for the programme plan

Questions from other teams are answered on the questions page.

Add these to the plan so they are not lost:

  • Whether any product needs a notified body, covered in the conformity routes guide [4]
  • The support period you will declare for each product [4]
  • Whether the UK product security regime also applies to the same products [10]
  • Periodic board reporting on vulnerability reports and remediation [5]

What to do

Seven steps, in order

  1. Step 1

    List every product you place on the EU market[5]

    Include older lines and the back-end services a product needs to work, and note which legal entity is the manufacturer for each. Reporting applies to products already on sale.

    Who: Product, engineering and legal leads

  2. Step 2

    Name an owner and a deputy for the 24-hour clock[5]

    Decide who judges that you are aware of an exploited vulnerability or severe incident, who approves the filing and who covers absence. Test the decision path with a tabletop exercise.

    Who: Security and product leadership

  3. Step 3

    Run a gap assessment against the essential requirements[4]

    Compare your secure development, vulnerability handling and update processes with the Annex I requirements, and record the gaps against each product.

    Who: Engineering and security teams

  4. Step 4

    Map suppliers and software components[8]

    Know which third-party and open-source components sit in each product, and who tells you when one is exploited. Start the component inventory that a software bill of materials needs.

    Who: Engineering and procurement

  5. Step 5

    Choose the conformity route for each product[4]

    Work out whether each product can use internal control or needs a notified body, based on whether it falls in an important or critical category.

    Who: Compliance and product teams

  6. Step 6

    Check the UK regime for consumer connectable products[10]

    UK product security rules have applied since 29 April 2024 and are separate from the EU Act, so meeting one does not settle the other.

    Who: Compliance leads

  7. Step 7

    Brief the board[5]

    Agree periodic reporting to the board on vulnerability reports and remediation status, so reporting decisions have clear sponsorship.

    Who: Directors and security leads

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.