Before signing a Cyber Resilience Act addendum, check which products it covers and whether your company can deliver each promise for as long as the buyer needs it.
A distributor might ask for seven years of security updates. If the supplier of a critical component stops issuing fixes after four, who will maintain the last units you ship?
Put the buyer’s addendum beside your supplier’s terms. Four clauses deserve particular attention: the compliance warranty, the support period, notice of vulnerabilities and the cost of a recall.
Discuss a CRA addendum
What to check against your supplier agreement
| What the buyer asks for | What to check before agreeing |
|---|---|
| A warranty covering the product | Which versions were tested, who controls changes and which evidence can be passed to the buyer and the authorities. |
| Seven years of updates | The end date for the last units sold and who can produce, sign and distribute fixes after the component vendor exits. |
| Notice within 24 hours | Which events count, whose knowledge starts the clock and whether the contract provides an out-of-hours contact. |
| Reimbursement of recall costs | Which party controls the decision, what losses the cap covers and what you could recover if a component caused the defect. |
Consider a UK supplier selling a connected device to a Polish importer. The importer plans to put the next batch on the EU market under its own brand in 2028. It asks the supplier to sign a CRA addendum before accepting the order. The examples below follow that negotiation.
For an overview of the regulation, including products in scope and the application dates, see our guide to the EU Cyber Resilience Act.
How far should a CRA compliance warranty extend?
Buyer’s draft“Supplier warrants full compliance with the Cyber Resilience Act.”
A firmware supplier can stand behind the release it delivered. It may have no control over the app the buyer adds, the configuration used in the field or a later change to the update mechanism. Start with a schedule that identifies the device, firmware version, intended use and agreed configuration.
For the rebranded batch, Article 21 of the Cyber Resilience Act treats the Polish importer as the manufacturer when it places the devices on the market under its own name or trademark. The importer can commission tests and negotiate access to evidence. It remains responsible for the manufacturer’s duties, including conformity assessment and the EU declaration of conformity.
A narrower warranty and an evidence schedule
Supplier’s counterproposal“Supplier warrants that the device and firmware identified in Schedule 1, as delivered in the agreed configuration, meet the applicable product requirements in Annex I, Part I of the CRA. Supplier is responsible for a failure caused by a subsequent change to the extent that it made or approved that change.”
Record separately how the supplier will support the manufacturer’s vulnerability-handling processes under Part II. Specify delivery of version-specific test reports, component information and the record of unresolved issues. Give the buyer the right to use that material for its assessment and disclose it to a competent authority. Agree how third-party confidential information can be supplied securely.
A ten-business-day response may be reasonable for a routine evidence request. It is useless if an authority expects a response on Friday. Agree an urgent contact, immediate acknowledgement and staged delivery in time for the applicable deadline. Where access to underlying records matters, agree when the buyer can request a targeted review and who pays for it.

Who covers the final years of security updates?
Suppose the supplier delivers units from February 2028 to January 2029. The module vendor guarantees fixes only until January 2032. Seven years from the first delivery ends in February 2035. Seven years from the last delivery ends in January 2036. The final units therefore face four years without vendor support.
Delivery is the assumed contractual trigger in this example. Check separately when each unit is placed on the EU market. Under Article 13(8), the manufacturer determines a support period reflecting expected use. The minimum is generally five years, unless the product is expected to be used for less. Article 13(19) requires the support end date, at least the month and year, to be clear and accessible at purchase.
A support commitment the supplier can deliver
Before the order is released, choose how the gap will be covered. The supplier could secure extended module support through January 2036. Alternatively, it could obtain the rights, tools and technical capability to maintain the module itself, or qualify a replacement and agree the cost of any redesign, testing and deployment. Buying extra stock alone does not secure another four years of fixes.
Supplier’s counterproposal“Supplier will provide security fixes for each unit for seven years from delivery, including through January 2036 for the final scheduled delivery. Before release of the first batch, Supplier will provide evidence of extended module support or demonstrate the agreed alternative maintenance route. Any later delivery requires a revised end date and corresponding support arrangements.”
This wording assumes the UK supplier accepts the full commitment. If it cannot secure either route, the Polish company must arrange the remaining support itself or revisit the product and delivery plan before launch. A shorter supplier contract leaves the manufacturer responsible for meeting its own support obligations.
Keep issued updates available as well. Article 13(9) requires availability for at least ten years after issue or for the remainder of the support period, whichever is longer. Specify who hosts the files and who takes over after termination.
The same issue in a software licence
A Polish reseller supplies an on-premises application under its own brand. Customers install it locally, but only the UK licensor can sign an update. Source-code escrow alone leaves the reseller unable to issue a trusted release. Agree release conditions, maintenance rights, access to build instructions and dependencies, and a tested, secure way for an authorised successor to sign releases. Allocate delivery to the reseller and installation to the customer if that is how the service operates.
Check any promise to patch only the latest version. Article 13(10) provides a limited route for subsequent substantially modified versions, for the requirement in Annex I, Part II, point 2. Earlier users must be able to obtain the latest version free of charge without extra costs to adapt their hardware or software environment. A paid database migration can defeat that assumption.

When does a 24-hour notice clause start?
Buyer’s draft“Supplier shall notify Distributor of any vulnerability within 24 hours of discovery.”
Define discovery, the affected products and the recipient. An internal alert to a distributor and a manufacturer’s statutory report serve different purposes. Article 14 covers actively exploited vulnerabilities and severe incidents affecting product security. Early warning is due without undue delay and within 24 hours of the manufacturer becoming aware. The coordinating CSIRT and ENISA receive it through the single reporting platform.
A Friday advisory and a Tuesday escalation
At 17:00 on Friday the UK supplier’s security team receives an advisory, confirms its module version is affected and knows of no exploitation or severe incident. If those facts trigger the contractual notice, it must alert the importer by 17:00 on Saturday. On the facts given, the advisory alone does not trigger Article 14 reporting.
At 09:30 on Tuesday the Polish manufacturer receives credible evidence of active exploitation affecting its product. Assuming it had no such evidence earlier, Wednesday at 09:30 is the outer limit for early warning. A new bulletin does not restart a clock that is already running. Record who received what and when.
One workable offer is immediate escalation of credible exploitation or a suspected severe incident, with a contractual outer limit of 12 hours from supplier awareness. Identify affected versions, known impact, available mitigation and a contact reachable overnight. Set a separate deadline for other high-severity issues and a regular advisory channel for lower-risk findings. Allow disclosure to authorities, users and component maintainers when required. A confidentiality clause must leave room to meet those obligations.
For statutory reports, the 72-hour notification also runs from awareness. The final-report deadline differs: for an actively exploited vulnerability it is 14 days after a corrective or mitigating measure becomes available. For a severe incident it is one month after the incident notification. Agree who supplies follow-up information while the investigation continues.
Information may also have to go back to the component vendor. Under Article 13(6), a manufacturer identifying a vulnerability in an integrated component must report it to the component’s manufacturer or maintainer. If it develops a modification to address that vulnerability, it must share the relevant code or documentation with that party. Check that the licence, NDA and reporting channels accommodate that exchange.
Who pays if products must be withdrawn or recalled?
Buyer’s draft“Supplier shall reimburse Distributor for all costs of any recall or withdrawal.”
This wording leaves the supplier exposed even if the distributor’s own modification caused the problem. Conversely, requiring a written order from an authority can leave the distributor paying for urgent action it was legally obliged to take itself. Article 13(21) requires a manufacturer to take immediate corrective measures, including withdrawal or recall where appropriate. That can arise before an authority intervenes.
Agree which decisions trigger reimbursement, which costs qualify and how to allocate responsibility if causes overlap. Distinguish withdrawal of stock in the distribution chain from recovery of products already with end users. The logistics and likely costs differ.
An alternative recall clause
Supplier’s counterproposal“Supplier will reimburse reasonable, documented direct costs of a withdrawal or recall to the extent caused by non-conformity of the Product as supplied. This applies where the action is ordered by a competent authority, is reasonably necessary to discharge a legal duty, or is agreed by both parties in writing. Distributor will consult Supplier in advance where time permits. If delay would prevent timely action, Distributor may proceed and will promptly explain its decision and provide supporting records.”
Define direct costs, for example customer notices, transport and replacement labour. State how any recall sub-limit interacts with the overall liability cap, which contract year applies to a multi-year incident and whether insurance covers the agreed costs. A contractual allocation between the parties does not limit the authority’s powers. Have the cap reviewed under the agreement’s governing law.

Getting a CRA addendum reviewed
Send the proposed addendum, the agreement it amends and the relevant component or software support terms. With those documents, CGO Legal can review the CRA clauses, propose changes to the buyer’s wording and identify the commitments your product team or component vendor needs to confirm before signature.
Frequently asked questions
Does the CRA prescribe a particular B2B warranty or indemnity?
The CRA assigns statutory duties according to each party’s role. It does not prescribe a standard B2B warranty or recall indemnity. The contract can specify the evidence, practical assistance and financial protection each party will provide.
Can a buyer charge a business customer for security updates?
The general rule is that manufacturers make security updates available to users free of charge. Annex I, Part II, point 8 allows a different agreement between a manufacturer and a business user for a tailor-made product. A B2B label alone does not establish that exception. Price upstream maintenance services separately from any promise about charges to users.
What if the supplier’s support ends before the last customer’s support period?
Identify who has the rights and capability to maintain the affected versions for the remaining period. Agree a funded takeover, extend supplier support or qualify a replacement before committing to the delivery schedule. Check the date customers will see at purchase against the solution actually secured.
Can notice to the distributor satisfy the manufacturer’s reporting duty?
An email to a distributor does not itself fulfil Article 14. For a reportable event the manufacturer must ensure that the statutory notification reaches the coordinating CSIRT and ENISA through the single reporting platform. A contractual alert can give the manufacturer the information it needs to meet its deadline.

