When a Firmware Update Needs New CE Evidence or Retesting
Assess firmware changes against existing CE evidence, notified body notification duties and the CRA substantial modification rules with a change impact record.
By CenitiaUpdated
Fact-checked against the law as of Reviewed by Vladimír Vician on How we check
A firmware update needs a documented impact review when it can change the assumptions behind your CE evidence. Some updates leave those assumptions intact; others change radio operation, power behaviour, safety functions or cybersecurity boundaries and need additional assessment.
Use the firmware change review for each release. It connects engineering changes to existing evidence without automatically treating every update as a complete retest.
Compare configurations, not release names
Record the old and new firmware hashes, affected hardware, enabled features and distribution scope. Read the actual diff and configuration changes. A release called “maintenance update” can still change radio settings or a safety relevant state machine.
For radio equipment, Article 10(5) of the Radio Equipment Directive (Directive 2014/53/EU) requires manufacturers to have procedures in place so that series production remains in conformity. Changes in the equipment's design or characteristics, and changes in the harmonised standards or other technical specifications used to declare conformity, must be adequately taken into account. Directive 2014/53/EU is the legal basis; your review explains how the new release remains covered.
The relevant question is not simply whether the PCB changed. Software can alter how the same hardware operates.
Map changes to evidence assumptions
| Change | Potential impact to review | Candidate evidence |
|---|---|---|
| Different transmit power or channel availability | Radio and exposure assessment conditions | Configuration comparison and relevant radio review |
| New high activity background task | Power, thermal or EMC operating conditions | Mode comparison and targeted measurements where needed |
| Revised charging control | Safety relevant behaviour | Safety analysis and appropriate functional testing |
| New remote command function | Intended use and cybersecurity risk | Threat model, authorisation and product classification review |
| Security patch with unchanged operating envelope | Whether existing assumptions remain valid | Patch scope, regression evidence and written rationale |
These are prompts, not mandatory test lists. The competent reviewer should decide what applies to the actual change and product.
A fictional update with two distinct questions
A fictional gateway update fixes a library vulnerability and also adds a remote relay control feature. The patch alone may preserve the existing operating envelope. The new control feature can change intended use, attack surface and consequences of misuse.
The team reviews those changes separately. It checks whether the relay activity changes electrical or thermal conditions, whether instructions need revision and whether the cybersecurity assessment covers remote control. It does not let the security patch label hide the new functionality.
Any decision to reuse previous test evidence records the relevant report, its assumptions and why they remain valid. If assumptions change, identify the uncovered condition and the action to close it.
Tell the notified body when a certificate is involved
If a notified body took part in the conformity assessment, a firmware change can trigger a duty to inform it. Check this before release.
- Radio Equipment Directive, Annex III, Module B, point 7. The manufacturer must inform the notified body that holds the technical documentation for the EU-type examination certificate of all modifications to the approved type that may affect conformity with the essential requirements or the conditions for validity of the certificate. Such modifications need additional approval, issued as an addition to the original certificate.
- Radio Equipment Directive, Annex IV, Module H, point 3.5. A manufacturer with an approved full quality assurance system must keep the notified body informed of any intended change to that system.
- Cyber Resilience Act (Regulation (EU) 2024/2847), Annex VIII, Part II (Module B), point 7. For products assessed under that module from 11 December 2027, the manufacturer must inform the notified body of all modifications to the approved type and to the vulnerability handling processes that may affect conformity or the conditions for validity of the certificate.
A product assessed only under internal production control has no notified body to inform. The manufacturer's own duty to keep the product in conformity is the same.
Keep the Cyber Resilience Act modification analysis distinct
Article 3(30) of the Cyber Resilience Act defines a substantial modification as a change made after the product is placed on the market that affects its compliance with the essential cybersecurity requirements in Part I of Annex I, or that modifies the intended purpose for which the product was assessed. Section 4 of the Commission guidance on the application of the Cyber Resilience Act (C/2026/6013) explains how to apply the definition to software updates:
- The assessment is case by case. Ask whether the update introduces new or increased cybersecurity risks that the risk assessment did not already address (paragraph 104).
- A new function that changes the product's intended purpose as a whole is generally a substantial modification (paragraph 105). A function that was already foreseen and assessed in the risk assessment is not (paragraph 106).
- Size is not the test. A small feature can be a substantial modification if it adds significant risk (paragraph 107).
- Security updates are generally not substantial modifications. They can be where they change the intended purpose or introduce new or increased risks, for example by adding externally reachable interfaces (paragraphs 108 and 109).
- Whatever the conclusion, the risk assessment and the technical documentation must be kept up to date (paragraph 113).
A substantially modified product that is made available on the market is treated as newly placed on the market. Existing documentation and tests can be reused for the parts that did not change (paragraphs 116, 122 and 123).
This legal analysis is distinct from deciding whether an existing radio report covers a changed transmit mode. A conclusion that a modification is not substantial under the Cyber Resilience Act does not prove that every CE evidence assumption is unchanged.
Timing and the responsible entity also matter. Under Article 69(2) of the Cyber Resilience Act, a product placed on the market before 11 December 2027 becomes subject to the Regulation's requirements only if it is substantially modified from that date. Under Article 22, a person other than the manufacturer, importer or distributor who substantially modifies a product and makes it available is treated as a manufacturer: for the affected part of the product or, where the modification affects the cybersecurity of the product as a whole, for the entire product. Have the reviewer identify the applicable rules instead of applying one slogan to old units, new production and third party modifications alike.
Decide proportionate verification before release
Define expected results, impacted requirements, tests and acceptance criteria. Retain both passing and failing results. If a fix requires a hardware or firmware configuration change during testing, record which final version was accepted.
Update declarations, technical documentation, instructions or labels where the assessment concludes that this is necessary. Under the Cyber Resilience Act, the technical documentation is continuously updated, where appropriate, at least during the support period (Article 31(2)), and the EU declaration of conformity is updated as appropriate (Article 28(2)). Do not change a declaration's date merely to create the appearance of recent testing.
Make reassessment part of the release process
Assign a conformity owner alongside the software release owner. Record unresolved questions and prevent the approval field from being populated solely by a build succeeding. Software regression tests and conformity evidence answer overlapping but different questions.
This article does not decide whether any particular firmware release needs retesting. That depends on the review described above.
CRA applicability and timing
Most Cyber Resilience Act obligations apply to products placed on the market from 11 December 2027; a product placed on the market earlier becomes subject to them only if it is substantially modified from that date (Article 69(2)). Article 14 reporting is already a current duty: it has applied since 11 September 2026 to every in-scope product, including products placed on the market before 11 December 2027 (Article 69(3)), and it continues after the support period ends. Check the product’s scope, your role and the transitional provisions. See the Commission page for manufacturers, the Commission page on reporting and the Commission guidance on the application of the Cyber Resilience Act (C/2026/6013).
Continue reading
Related guides
tutorial
Secure OTA Firmware Updates and the Evidence to Keep
Plan secure OTA test evidence for signatures, interrupted updates, recovery and downgrade controls against the CRA update requirements, with a small host demo.
6 min read
guide
CRA Scope for Connected Devices and Their Cloud Backends
Apply the CRA remote data processing tests to connected device architectures and record external cloud dependencies separately.
5 min read
tutorial
CycloneDX VEX for Embedded Firmware: a Worked Synthetic Example
Write a scoped CycloneDX VEX decision for embedded firmware: an unresolved in_triage record, a synthetic not_affected record with justification, and reassessment triggers.
5 min read
tutorial
CRA Cybersecurity Risk Assessment for an IoT Gateway
Create an IoT gateway risk register that connects product boundaries, abuse cases, security controls and verifiable release evidence.
4 min read
Put this into practice
Free tools & references
- CRA Readiness CheckerScore your product against the Cyber Resilience Act essential requirements.Open tool →
- EU Directive SelectorDescribe your product and find which EU directives and regulations apply.Open tool →
New to the terminology? Browse the compliance glossary — plain-English, citation-backed definitions of every term above.