Shipmark / Free tools

CRA readiness tracker for app publishers

The twelve steps before 11 December 2027 for one app you publish: status, owner and target date per step, and a plan you can export.

If your company publishes the app under its own name, the Cyber Resilience Act makes you its manufacturer (Article 3(13)). Reporting of actively exploited vulnerabilities has applied since 11 September 2026; the rest of the regulation applies from 11 December 2027 (Article 71(2)). The steps follow our CRA readiness checklist: mark where you stand, give each open step an owner and a date, and keep the plan.

11 December 2027 is when the main obligations apply.

Everything stays in your browser: nothing you enter is sent or stored. Closing the page clears it, so download the JSON file to continue later.

The app

The twelve steps

Start with steps 1 to 3 if you only have a day: they cover the one obligation already in force and give you the register every later step depends on.

1 Confirm that you are the manufacturer

Start now Article 3(13)

If your company markets the app under its own name or trademark, paid or free, you are its manufacturer, even when an agency wrote the code.

What to do
  • Write down, per app, which legal entity publishes it in the stores.
  • Check developer accounts: the store listing should show that entity.
  • Note any app another company publishes for you, or you for another company.

Help: Who is the manufacturer?

2 List your apps, versions and what is in scope

Start now Article 3(13), scope

One register of every app you publish, the versions still in use, the stores and the backend each one needs.

What to do
  • List apps, platforms and the oldest version still in use.
  • Note the backend services each app needs to work.
  • Run the scope check for every app and keep the answer.

Help: Does the CRA apply? · CRA and mobile apps

3 Be able to report actively exploited vulnerabilities

In force since 11 Sep 2026 Article 14, Article 69(3)

Applies since 11 September 2026, also to apps placed on the market earlier: early warning within 24 hours, notification within 72 hours, final report no later than 14 days after a fix or mitigation is available.

What to do
  • Name who decides that a vulnerability is actively exploited.
  • Name who files on ENISA's single reporting platform, and a backup.
  • Run one practice report with the deadline calculator.

Help: Vulnerability reporting · Deadline calculator

4 Publish a contact point and a disclosure policy

Start now Article 13(17), Annex I Part II (5) and (6)

A single point of contact so users can reach you directly and rapidly, a coordinated vulnerability disclosure policy and a contact address for reporting vulnerabilities.

What to do
  • Set up a monitored security mailbox.
  • Publish security.txt on your website.
  • Publish the disclosure policy and link it from the app and the store listing.

Help: security.txt generator · Disclosure policy guide

5 Write the cybersecurity risk assessment

Before 11 Dec 2027 Article 13(2) to (4)

A documented assessment of the cybersecurity risks, per app, that goes into the technical documentation and explains any Annex I requirement you treat as not applicable.

What to do
  • One assessment per app, not one for the company.
  • Cover the app, its backend and the data it handles.
  • Plan when you review it during the support period.

Help: Risk assessment template

6 Know your dependencies and keep an SBOM

Before 11 Dec 2027 Article 13(5) and (6), Annex I Part II (1)

Due diligence on third-party components, including open source, and a report to the maintainer when you find a vulnerability in one. An SBOM per release is the starting point.

What to do
  • Generate an SBOM on every release build.
  • Check it for known vulnerabilities before release.
  • Keep the SBOM with that version's documentation.

Help: SBOM scanner · SBOM checker

7 Check the Annex I security requirements

Before 11 Dec 2027 Article 13(1) and (4), Annex I Part I

The app must be designed, developed and produced in line with the essential requirements. Justify any requirement you consider not applicable.

What to do
  • Go through the 13 Part I requirements for the current version.
  • Turn every gap into a ticket with an owner.
  • Add the checks to your release process.

Help: Annex I checklist · Annex I for apps

8 Decide and declare the support period

Before 11 Dec 2027 Article 13(8)

A support period that reflects how long the app is expected to be in use, documented with the reasons for it, during which vulnerabilities are handled.

What to do
  • Decide the period per app and write down why.
  • Plan how you will tell users when support ends.
  • Record the dates per version.

Help: Support period calculator · Support period guide

9 Plan security updates and their retention

Before 11 Dec 2027 Article 13(9) and (10), Annex I Part II (8)

Security updates stay available for at least 10 years after they are issued, or for the rest of the support period if longer, and reach users without delay and free of charge.

What to do
  • Decide how a fix reaches users: store release, forced update or backend fix.
  • Keep build artefacts and release notes for every security update.
  • Prepare the advisory template you will publish with a fix.

Help: Security advisory generator

10 Build the technical documentation as you go

Before 11 Dec 2027 Article 13(12) and (13), Annex VII

Draw up the technical documentation before placing the app on the market and keep it, with the declaration, for at least 10 years or the support period if longer.

What to do
  • Create one folder per app version.
  • File the risk assessment, SBOM, Annex I record and test results in it.
  • Decide who keeps it and for how long.

Help: Technical documentation checklist

11 User information, conformity assessment and declaration

Before 11 Dec 2027 Article 13(12), Annexes II and V

Before placing the app on the market: the user information of Annex II, the conformity assessment, the EU declaration of conformity and the CE marking.

What to do
  • Check the product class: it decides the assessment route.
  • Draft the Annex II user information page.
  • Draft the declaration of conformity.

Help: Product class check · User information · Declaration of conformity

12 Check releases and fix your agency contracts

Before 11 Dec 2027 Article 69(2)

An app placed on the market before 11 December 2027 falls under the main obligations only after a substantial modification from that date. If an agency builds or maintains the app, the duties still stay with you.

What to do
  • Record a security delta for every release.
  • Put SBOM delivery, vulnerability handling and support in agency contracts.
  • Agree who prepares reports on time for you.

Help: Release check · Agency or client

0 of 12 done

0 of 12

How to use the plan

Share the Markdown plan with whoever owns each step, and save the JSON file to update it next week. Most steps are per app: run the tracker once for each app you publish. A target date after 11 December 2027 is flagged, because the obligations behind steps 4 to 12 apply from that day for apps placed on the market from then on, and for older apps after a substantial modification (Article 69(2)).

The tracker is a planning aid. The detail behind each step is in the linked guides and tools, and in the CRA timeline for app teams.

Steps 3, 6 and 9 start with knowing what is inside each release. Shipmark keeps an SBOM and daily vulnerability checks for every app you publish. Founding members use it free until 1 April 2027.

Join the free beta

Sources

The tracker summarises the regulation in short; the regulation's text is what counts. It is a planning aid, not legal advice. Related: CRA readiness checklist · Annex I checklist · Does the CRA apply? · CRA key dates.