Your app was built by an agency: what to put in the maintenance contract because of the CRA
If you publish the app under your name, the Cyber Resilience Act duties are yours. The agency can do the work, but only your contract makes sure the work actually happens, on time. You are the manufacturer if you hav
If you publish the app under your name, the Cyber Resilience Act duties are yours. The agency can do the work, but only your contract makes sure the work actually happens, on time.
- You are the manufacturer if you have the app developed and market it under your name or trademark (Article 3(13)). Articles 13 and 14 then apply to you, whoever writes the code.
- Four things need a named owner in the contract: how long the app is maintained, how vulnerabilities are handled, what the agency hands over (SBOM, test results, documentation), and who tells whom within 24 hours when a vulnerability is being exploited.
- A short section at the end is for agencies: what to offer so that publishers can sign.
Why the contract matters more than before
Article 3(13) defines the manufacturer as a person who develops or manufactures products with digital elements, or has them designed, developed or manufactured, and markets them under its name or trademark. If your company ships an app that an agency built, you are the one who "has products designed, developed" and markets them under your name. The obligations in Articles 13 and 14 are addressed to that manufacturer. For the wider question see Agency or client: who is the manufacturer?
The practical gap is this: you carry the duties, but the agency usually holds the repository, the build pipeline and the people who can fix a bug. A contract that only says "maintenance included" leaves every CRA duty without an owner. The sections below turn each duty into something you can ask for in writing. The CRA itself does not prescribe contract clauses; this is our practical reading of what the duties require, not legal advice.
The duties and where the contract has to help
| Your duty | Source | What to ask the agency for |
|---|---|---|
| Handle vulnerabilities for the whole support period | Art. 13(8), Annex I Part II | A maintenance commitment that runs as long as your declared support period, with response times. |
| Due diligence on third-party and open-source components | Art. 13(5) | A list of every component and a check on each before it is added. |
| Report vulnerabilities you find in a component to its maintainer and share your fix | Art. 13(6) | Agreement on who contacts the maintainer and who shares the fix. |
| Document cybersecurity aspects, including vulnerabilities | Art. 13(7) | Written test results, findings and decisions per release. |
| Technical documentation, conformity assessment, declaration of conformity | Art. 13(12) | The technical inputs you need to draw them up. |
| Keep documentation and declaration at least 10 years or the support period | Art. 13(13) | A copy handed over to you, not stored only on the agency's systems. |
| Notify exploited vulnerabilities and severe incidents | Art. 14 | An immediate alert duty towards you and help to prepare each report. |
1. Support period: how long the agency maintains the app
Article 13(8) requires you to handle vulnerabilities effectively during the support period. The support period reflects how long the product is expected to be in use, and it must be at least five years; if the product is expected to be used for a shorter time, the period matches that expected time. The information used to set it goes into the technical documentation. Security updates then have to stay available for at least 10 years or for the remainder of the support period, whichever is longer (Article 13(9)). Our guide on the support period explains how to set it per app version.
For the contract this means:
- Write the support period into the contract per app version, or state clearly that you will agree it in writing before each release.
- Do not accept a maintenance term shorter than your support period without a plan for what happens after it: a renewal option, a hand-over of the code and pipeline, or a named successor.
- Ask for a notice period if the agency stops offering maintenance, long enough to move to another supplier.
2. Vulnerability handling: what "maintenance" has to include
The vulnerability handling requirements are in Annex I Part II. As we read them, they cover keeping an inventory of the components in the app including a machine-readable SBOM (at least the top-level dependencies), fixing vulnerabilities without undue delay and where technically feasible shipping security updates separately from feature updates, regular security testing, publishing information about fixed vulnerabilities, a coordinated vulnerability disclosure policy with a contact address, and secure distribution of updates. See Writing a coordinated vulnerability disclosure policy for the policy and contact address.
Turn that into service terms, not a general promise:
| Term | What to write down |
|---|---|
| Monitoring | How often the agency checks the app's dependencies for known vulnerabilities, and where the results go (for example a ticket in your tracker). |
| Triage time | How fast the agency tells you about a new vulnerability in your app, and how fast it assesses it. Keep this short for actively exploited cases (see section 4). |
| Fix time | Target times to deliver a fix by severity. Article 13 and Annex I use "without delay", not a number, so the numbers are a business decision you make. |
| Security updates | Security releases are separate from feature releases where technically feasible, and are not held back behind a paid change request. |
| Regular testing | What tests run before each release and how the results are shared with you. |
| Incoming reports | Who receives a vulnerability report sent by a researcher, who answers it, and how it reaches you the same day. The contact address should be yours, not the agency's inbox. |
| Component vulnerabilities | Who reports a flaw found in a third-party component to its maintainer and who shares the fix (Article 13(6)). |
Under Article 13(5) you must exercise due diligence when integrating components sourced from third parties, so that they do not compromise the cybersecurity of your app. Add a clause that new dependencies, and especially new third-party SDKs, need your approval before release, with the agency's short assessment attached.
3. SBOM and documentation: what the agency hands over
You can only keep the documentation if you have it. Article 13(12) requires the technical documentation, the conformity assessment and the EU declaration of conformity before you place the product on the market, and Article 13(13) requires you to keep the documentation and the declaration for at least 10 years or the support period, whichever is longer. See the technical documentation checklist.
Ask the agency to deliver, with every release:
- a machine-readable SBOM for that exact version (the iOS, Android, Flutter and React Native guides show how it is produced), kept by version;
- the test and review results for that release;
- a record of vulnerabilities found and fixed, with dates, for the documentation and for any later advisory;
- the information needed to update your cybersecurity risk assessment, if the release changed the app's risk profile (see the risk assessment guide).
Also settle ownership of the things that keep the app maintainable: source code, build scripts, signing keys and store accounts should belong to you or be handed over on request, not sit only in the agency's accounts. If your agency produces the SBOM in a CI pipeline, the free open-source Shipmark SBOM GitHub Action (uses: shipmark-eu/sbom-action@v1) can do it on every build.
4. Reporting: who tells whom, and how fast
Article 14(1) requires the manufacturer to notify any actively exploited vulnerability contained in the product to the CSIRT designated as coordinator and to ENISA, through the single reporting platform. Article 14(2) sets three steps for such vulnerabilities:
| Step | Deadline in Article 14(2) |
|---|---|
| Early warning | Without undue delay and in any event within 24 hours of becoming aware |
| Vulnerability notification | Within 72 hours of the manufacturer becoming aware |
| Final report | No later than 14 days after a corrective or mitigating measure is available |
Severe incidents that affect the security of the app follow a similar path with a final report within one month (Article 14(3) and (4)). Article 14(8) also requires you to inform affected users about the vulnerability or incident and the measures they can take. These duties apply since 11 September 2026; see the key dates and the reporting guide.
The deadlines run from when the manufacturer becomes aware. If your agency monitors the app and knows first, your clock is already running while the news sits in its inbox. So the contract should say:
- the agency alerts you immediately, by a channel that works at night and at weekends, when it learns of a vulnerability that may be actively exploited or an incident in your app, and names a contact person on each side;
- the agency prepares the technical content for each report step (affected versions, nature of the exploit, corrective and mitigating measures) within agreed hours, so that you can submit it;
- the notification itself is made by you, with your account on the reporting platform, unless you have decided otherwise in writing. The legal duty stays with you either way.
Use the free reporting deadlines tool to compute your three dates from the moment of awareness.
5. Other clauses worth having
- Substantial modifications. Agree that changes which could affect compliance with the essential requirements are flagged to you before release, so that you can decide whether the update is a substantial modification (the free release check helps).
- Cost of security fixes. Decide who pays for fixes to vulnerabilities in code the agency wrote, and for urgent work outside office hours. Disputes about cost are the main reason fixes get delayed.
- Audit and evidence. A right to ask for the evidence behind a claim, such as test results and the component list, so that you can show a market surveillance authority what you did.
- Subcontractors. The agency's own freelancers and suppliers are bound by the same terms.
- Exit. On termination, hand-over of code, SBOMs, documentation and access, in a usable form, within a fixed time.
A short section for agencies
When your client publishes the app under its own name, the client is the manufacturer and you are a supplier to it. You do not take on the client's legal role by building the app, and you should not describe yourself as the manufacturer in proposals. What you can do is make the client's duties easy to meet, and that is a service you can sell: a maintenance plan with a stated support period, a monitoring and response service with clear times, an SBOM and test report with every release, and an immediate-alert process for suspected exploitation.
The picture changes if you publish an app under your own name, or supply your own reusable product to several clients; the manufacturer guide explains those cases. Keep the two separate in your contracts.
Try it on your own app: the free Shipmark scanner builds a CycloneDX SBOM from a lockfile in the browser and checks it against OSV.dev. Not sure the CRA applies? Use the six-question CRA check.
Sources
- Regulation (EU) 2024/2847 (Cyber Resilience Act), EUR-Lex: the authentic text.
- Article 3, Definitions: point 13, manufacturer.
- Article 13, Obligations of manufacturers: paragraphs 5, 6, 7, 8, 9, 12 and 13.
- Article 14, Reporting obligations of manufacturers: paragraphs 1 to 4, 7 and 8.
- Annex I, Essential cybersecurity requirements (Prighter copy): Part II, vulnerability handling. We summarise it; check the wording and point numbers against the Official Journal text.
This guide summarises EU law for practical use and suggests contract topics. It is not legal advice; have a lawyer review the contract. Related: Agency or client ยท Support period ยท Readiness checklist ยท Vulnerability reporting.
Originally published on shipmark.eu, where the guide is kept up to date. More guides for app teams: shipmark.eu/guides.
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes โ full credit and traffic to the original publisher.