Shipmark / Free tools / Substantial modification check
Is this app update a substantial modification under the CRA?
For one release of one app, about two minutes. Nothing you answer leaves your browser.
Why it matters: an app first released in the EU before 11 December 2027 only has to meet the CRA requirements if it is substantially modified from that date (Article 69(2)). Reporting exploited vulnerabilities applies to it either way (Article 69(3)). For an app released later, a substantial modification means the new version is assessed again. Apps get updated often, so the question comes back with every release.
Answer for the release you are about to ship. The check follows the four questions of the Commission guidance of July 2026 and writes a short record of your answers to keep with the risk assessment.
What the rules say
| Rule | What it means for an app |
|---|---|
| Dates Article 71(2) | The regulation applies from 11 December 2027. Article 14 (reporting) applies from 11 September 2026, and Chapter IV (notified bodies) from 11 June 2026. |
| Apps already on the market Article 69(2) | Products placed on the market before 11 December 2027 are subject to the requirements of the regulation only if, from that date, they undergo a substantial modification. |
| Reporting for all Article 69(3) | By way of derogation, the reporting obligations of Article 14 apply to all products in scope placed on the market before 11 December 2027. An older app still reports actively exploited vulnerabilities and severe incidents within 24 hours, 72 hours and the final report deadline. |
| Software versions Guidance, points 13 to 15 | As summarised by Schutzwerk and CRA Experts: all copies of a software version are placed on the market when that version is first offered, later downloads are only making it available, and an update that is not a substantial modification does not change that date. |
| The four questions Guidance, points 107, 110 and 111 | As summarised by CVD Portal, Turingpoint and CRA Experts: does the update introduce new threat vectors, enable new attack scenarios, change the likelihood of scenarios already identified, or change their impact? Four negative answers, with the risk assessment's assumptions and mitigations still valid, likely mean the change is not substantial. The scale or complexity of the change does not decide. |
| Security updates Guidance, points 108 and 109 | As summarised by CVD Portal and Turingpoint: a security update is not a substantial modification even with significant technical changes, as long as it does not change the intended purpose or bring new or increased risks, for example a new external dependency. |
| After a substantial modification Guidance, points 116 and 133 | As summarised by CVD Portal, Turingpoint and CRA Experts: the modified product is treated as a new product (point 116), the obligations concern the modified parts unless the change affects the cybersecurity of the product as a whole, and the support period is re-derived rather than automatically reset (point 133). |
How to use this in an agency
- Run the check in release planning, not on release day: a "yes" may mean the release needs the full set of CRA documents first.
- Keep the risk assessment of each client app current. The four questions only work against a list of attack scenarios you already wrote down, and a feature the assessment anticipated is not a new scenario.
- Watch white-label and per-client builds. If they differ in components or features, each one is a variant with its own placing date.
- Who decides is the manufacturer, normally the client that publishes the app (see agency or client: who is the manufacturer?). Save the record the check writes and send it with the release notes so the decision is the client's, on evidence from you.
If the result is that the CRA requirements apply, the next steps are the Annex I checklist, the support period of the new version, the technical documentation and the EU declaration of conformity.
Shipmark keeps an SBOM of every release of every client app, so you can see which components a release added or changed before you answer question 6. Founding agencies use it free until 1 April 2027.
Join the free betaSources
- Regulation (EU) 2024/2847, Article 69: transitional provisions, paragraphs 2 and 3, and Article 71: entry into force and application (SpringLex).
- Regulation (EU) 2024/2847 (Cyber Resilience Act), EUR-Lex: the authentic text.
- European Commission: Commission publishes new guidance to support timely Cyber Resilience Act implementation (27 July 2026, C(2026) 5252, non-binding), with the guidance document.
- CVD Portal: the Commission's CRA guidance, the four-factor test and the support period rules.
- Turingpoint: what C(2026) 5252 settles for manufacturers.
- Schutzwerk: CRA legacy products, does the transition rule cover models or units?
- CRA Experts: are products built before 2027 grandfathered under the CRA?
We read Articles 69 and 71 directly. The guidance point numbers come from the summaries listed above; read the guidance itself before relying on a point. The check runs in your browser and does not send or store your answers. It gives a general orientation and is not legal advice: a substantial modification is decided case by case by the manufacturer. Related: Does the CRA apply? · Risk assessment guide · Support period calculator