Shipmark / News

The first CRA standards are published: what EN 40000-1-1 and -1-2 mean for app publishers

· 5 min read · CRA news

A grey steel drawing compass next to a brown leather case on a workbench
Photo: Jeff Sheldon on Unsplash

In short: the first two European standards written for the CRA, EN 40000-1-1 (vocabulary) and EN 40000-1-2 (principles, risk management and lifecycle), are out. They are a framework for organising your cybersecurity work, not yet a legal shortcut.

  • The Commission says the first standard was published on 18 November 2026; CEN-CENELEC announced both on 19 November.
  • Neither source says the standards are cited in the Official Journal or give a presumption of conformity.
  • A secondary tracker reports that no citation is expected for these two; the vulnerability handling part, EN 40000-1-3, is still not published.
  • For an app publisher, the value today is a recognised structure for your risk assessment, lifecycle and technical file.

What was published

On 19 November 2026 the European Commission announced the first European standard supporting the Cyber Resilience Act and said it was published on 18 November. The same day CEN-CENELEC, the standards bodies behind the work, presented two standards as available: EN 40000-1-1, Cybersecurity requirements for products with digital elements, Part 1-1: Vocabulary, and EN 40000-1-2, Part 1-2: Principles, product risk management, and lifecycle activities. Both belong to the standardisation request the Commission gave CEN, CENELEC and ETSI in 2025. We covered their approval on 10 November in our earlier article; this is the next step, publication.

What they cover

EN 40000-1-1 gives the whole series one set of terms and definitions, so you, your auditor and your suppliers read words like "product" and "vulnerability" the same way. EN 40000-1-2 is the substantive one. According to CEN-CENELEC it sets out cybersecurity principles, baseline requirements for managing cybersecurity risk, and activities across the product lifecycle: design, development, production, maintenance, end of support and decommissioning. The Commission describes it as generic, applicable to a wide range of products, and names smartphone-controlled door locks and software such as operating systems, browsers and password managers among the examples. It also says the standard reaches remote data processing that supports a product function, such as cloud-based management of a device. Our reading: for an app, that points to the backend your app depends on, which matches the direction of the Commission guidance we reported on 18 November.

The Commission presents the standard as a way to run cybersecurity processes and lifecycle activities in a more systematic and auditable way, and to demonstrate compliance. Product-category standards with detailed requirements are meant to follow.

What it does not do yet

Neither the Commission page nor the CEN-CENELEC page says these standards are harmonised, cited in the Official Journal, or that they give a presumption of conformity. That matters, because as we explained in our earlier article, a presumption comes only from harmonised standards whose references are published in the Official Journal. We could not read the CRA text on EUR-Lex in this run, so check Article 27 there yourself. The independent guide cyberresilienceact.eu reports that CEN project records mark both standards "no citation expected". We could not verify that against CEN's own records, so treat it as a report.

Two more limits. First, EN 40000-1-3, on secure development and vulnerability handling, is still a draft at formal vote stage according to CEN-CENELEC, which says only that it and the first product-specific standards are coming soon. Cyberresilienceact.eu reports a Commission deadline of 30 November 2026 for it, an amendment we could not check in the decision itself. Second, availability is through national standards catalogues, subject to national publication schedules, so the text may reach your country's catalogue at different times and may cost money.

StandardStatusWhy an app publisher cares
EN 40000-1-1 VocabularyPublishedShared terms for your technical file and supplier contracts.
EN 40000-1-2 Principles, risk, lifecyclePublishedA recognised outline for risk assessment, secure development, maintenance and end of support.
EN 40000-1-3 Vulnerability handlingDraft, not publishedThe part that matches your disclosure and patching process.

What we would do

  1. Obtain EN 40000-1-2 through your national standards body and compare its lifecycle activities with how your team actually builds and ships the app. Do not align to a summary, including ours.
  2. Keep working on the essential requirements. They apply with or without a cited standard; the standard is a method, not a substitute. Our guides on the cybersecurity risk assessment and the technical documentation show what to write down.
  3. Include your backend in the risk assessment and lifecycle plan if it processes data for an app function.
  4. Do not claim conformity to the standard in your declaration or marketing yet. Nothing we read says it gives a legal presumption.
  5. Watch for EN 40000-1-3 and for any Official Journal citation, and keep your disclosure and update process ready in the meantime.

Lifecycle activities include knowing which third-party components are in each release. Build an SBOM and check it against known vulnerabilities in seconds.

Open the free scanner

Sources

This article summarises public announcements for practical use. It is not legal advice. Standards and deadlines may change; verify against the sources. Related: Does the CRA apply to mobile apps? · CRA technical documentation