Dev.to Security πŸ” Cybersecurity πŸ‘ 0 πŸ“– 5 min read

CRA readiness checklist for app publishers: 12 steps before December 2027

If you publish an app under your own name, the CRA treats you as its manufacturer. Reporting already applies; everything else applies from 11 December 2027. Start with what is already live: Article 14 reporting has a

If you publish an app under your own name, the CRA treats you as its manufacturer. Reporting already applies; everything else applies from 11 December 2027.

  • Start with what is already live: Article 14 reporting has applied since 11 September 2026 and covers apps already on the market (Article 69(3)).
  • The main obligations apply from 11 December 2027 (Article 71(2)), about thirteen months from now.
  • The twelve steps below take you from roles and inventory to the declaration of conformity, each with a link to a detailed guide.

The twelve steps at a glance

Step Main legal basis When
1 to 2: roles and inventory Article 3(13) Now
3 to 4: reporting, contact point, disclosure policy Articles 13 and 14 Now (Article 14 applies since 11 September 2026)
5 to 9: risk assessment, SBOM, Annex I, support period, updates Article 13(1) to (10), Annex I During 2027
10 to 12: documentation, declaration, release checks Articles 13(12) to (13), 31, 69(2), Annexes II and VII Before 11 December 2027

1. Confirm that you are the manufacturer

Under Article 3(13) the manufacturer is whoever develops or manufactures a product with digital elements, or has it designed, developed or manufactured, and markets it under its own name or trademark. If your company publishes the app, that is you, even when an agency wrote the code. Write this down per app, because every other step assumes it.

Read next: Agency or client: who is the manufacturer?

2. List your apps, versions and what is in scope

Make one register of every app you publish, the versions still in use, the stores and the backend each one needs. Check whether each app is covered at all, and whether remote functions you control count as part of the product. The Commission guidance addresses remote data processing solutions in scope questions.

Read next: Does the CRA apply to mobile apps? Β· Companion apps Β· free scope checker

3. Be able to report actively exploited vulnerabilities

Article 14 has applied since 11 September 2026, and Article 69(3) extends it to products placed on the market before 11 December 2027. You owe an early warning within 24 hours, a notification within 72 hours and a final report after a fix is available. Decide now who judges that a vulnerability is actively exploited and who files the report. A summary of the Commission guidance by SCHUTZWERK says the 24-hour clock starts once there is reasonable certainty of exploitation in your own product, not when a CVE appears in a component.

Read next: Vulnerability reporting for app teams Β· deadline calculator

4. Publish a contact point and a disclosure policy

Article 13 requires a single point of contact that lets users reach you directly and quickly, including to report vulnerabilities, and Article 13(8) requires vulnerability disclosure policies. A monitored mailbox and a security.txt file are the usual minimum for an app publisher.

Read next: Writing a disclosure policy Β· security.txt generator

5. Write the cybersecurity risk assessment

Article 13(2) to (4) requires a documented risk assessment per product, updated during the support period. It must consider intended and reasonably foreseeable use, the operating environment, the assets to protect and the expected lifetime, and it becomes part of the technical documentation. Do one per app, not one for the company.

Read next: Risk assessment template

6. Know your dependencies and keep an SBOM

Article 13(5) requires due diligence when you integrate third-party components, including free and open-source ones. If you find a vulnerability in a component, Article 13(6) says to report it to the maintainer and remediate it under Annex I Part II. You cannot do either without a list of what is in each release, so generate an SBOM at every build.

Read next: Flutter Β· React Native Β· iOS Β· Android. Automate it with the open-source Shipmark GitHub Action (uses: shipmark-eu/sbom-action@v1).

7. Check the Annex I security requirements

Article 13(1) requires the app to be designed, developed and produced in line with Annex I Part I. Harmonised standards are still pending, so turn each requirement into a concrete check in your release process and record the result, and justify in the documentation any requirement you consider not applicable (Article 13(4)).

Read next: Annex I as checks for a mobile app Β· Annex I checklist tool

8. Decide and declare the support period

Article 13(8) sets a support period that reflects expected use and lasts at least five years, unless expected use is shorter, and you must document the basis for it. Record it per app version.

Read next: The support period explained Β· support period tool

9. Plan security updates and their retention

Article 13(9) says each security update made available during the support period stays available for at least 10 years after it was issued or for the rest of the support period, whichever is longer. Make sure your store releases, build artefacts and release notes are kept accordingly. Article 13(10) lets you support only the latest version of a substantially modified software product if users can upgrade to it free of charge.

10. Build the technical documentation as you go

Before placing the app on the market you must prepare technical documentation under Article 31 and Annex VII, and Article 13(13) requires it, with the EU declaration of conformity, to be kept for at least 10 years after placing on the market or for the support period if longer. Collecting it per release is far easier than rebuilding it in 2027.

Read next: Technical documentation checklist

11. Prepare user information, conformity assessment and the declaration

Article 13 requires user information and instructions as set out in Annex II. Before placing the app on the market you complete the conformity assessment, issue the EU declaration of conformity and affix the CE marking (Article 13(12)). Check whether your app could fall under an important product class, because that changes the assessment route.

Read next: User information tool Β· Declaration of conformity tool Β· Product class tool

12. Check every release for substantial modification and fix your agency contracts

An app placed on the market before 11 December 2027 is subject to the Regulation only if it undergoes a substantial modification from that date (Article 69(2)), so keep a security delta record per release. If an agency builds or maintains the app for you, put the support period, vulnerability handling, SBOM delivery and who talks to ENISA into the contract, because the duties stay with you as manufacturer.

Read next: Release check tool

Where to start this week

If you only have a day, do steps 1, 2 and 3. They are cheap, they cover the one obligation that is already in force, and they give you the register that every later step depends on. The key dates are in the CRA timeline for app teams.

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

This guide summarises EU law and non-binding Commission guidance for practical use. It is not legal advice. Related: CRA key dates Β· Does the CRA apply to mobile apps? Β· Who is the manufacturer? Β· Vulnerability reporting.

Originally published on shipmark.eu, where the guide is kept up to date. More guides for app teams: shipmark.eu/guides.

πŸ“° Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.