EN 40000-1-2:2026 – Principles, risk management and lifecycle

Since 18 November 2026, EN 40000-1-2 has been available – together with the vocabulary part EN 40000-1-1, one of the first two European standards supporting the Cyber Resilience Act. It sets out cybersecurity principles, baseline requirements for managing cybersecurity risks and activities across the entire product lifecycle. Citation in the Official Journal is not expected; it therefore confers no presumption of conformity. This page puts the standard into context, guides you through risk management and the lifecycle, and offers a readiness check.

آخر تحديث: نوفمبر 2026 · Valeri Milke, Lead Auditor لمعياري ISO 27001 وISO 42001

Available since 18 Nov 2026 · not in the Official Journal
  1. 01Planning
  2. 02Requirements
  3. 03Design
  4. 04Development
  5. 05Verification
  6. 06Production
  7. 07Monitoring
  8. 08Decommissioning
4Principles6Building blocks of risk managementM/606Standardisation request
Orbit around EN 40000-1-2: the standard at the core, principles and risk management inside, the eight lifecycle activities from planning to decommissioning outside.
18 Nov 2026Definitive text available (DAV) – ratified on 2 November 2026
4Principles: risk-based approach, security by design, secure by default, transparency
450+Experts from 28 national standardisation bodies and 17 partner organisations in the responsible working group
0Citations in the Official Journal: none is expected for Part 1-2 – so no presumption of conformity arises

The Cyber Resilience Act requires manufacturers to design, develop and produce products with digital elements on the basis of an assessment of cybersecurity risks – and to keep that assessment up to date throughout the support period. EN 40000-1-2:2026 describes what this looks like methodically; it was developed by the joint working group CEN-CLC/JTC 13/WG 9 under the Commission’s Standardisation request M/606. The standard is product-related, applies to all product categories and forms the framework on which the product-specific standards are meant to build. What matters for putting it in context: citation in the Official Journal of the European Union is not expected for this part. Those who apply the standard gain a methodology agreed at European level and a robust structure for the technical documentation – it does not replace demonstrating that the essential requirements of the Regulation are met.

From the standardisation request to the first CRA standards – and what is still to come

The milestones of EN 40000-1-2 alongside the deadlines of the Cyber Resilience Act. The national dates come from the standard’s CEN project entry.

Nine points manufacturers should know about EN 40000-1-2

Click a card to expand the point – or open them all at once.

Interactive

Classification: What does EN 40000-1-2 mean for your product?

Up to four yes/no questions clarify whether the CRA covers your product, what role Part 1-2 plays for your demonstration of conformity and which additional standards you should follow. Orientation, not legal advice.

Your path
  1. ?

1: Do you manufacture a product with digital elements – or offer one under your own name or trademark on the EU market?

1

Do you manufacture a product with digital elements – or offer one under your own name or trademark on the EU market?

This means products with digital elements: devices with firmware, standalone software, apps and separately offered components that can be connected directly or indirectly to a device or network. Pure online services are not a product in themselves.

Lifecycle navigator

Eight lifecycle activities, one risk management at the core

EN 40000-1-2 links risk management with activities from planning to decommissioning; the handling of third-party components accompanies the whole cycle. For each entry: typical misconceptions, references, measures, a review question and evidence – prepared by VamiSec, not a reproduction of the standard’s text.

Lifecycle · start of every product and every version

Planning cybersecurity across the lifecycle

The standard requires cybersecurity activities to be planned for the whole lifecycle, the plan to be kept up to date and its implementation to be tracked. The plan connects risk management, development, production and operation through to the end of the support period.

ContextEN 40000-1-2 · Lifecycle activity Planning · CRA · Risk assessment in all phases

Typical misconceptions

  • “A security concept at the start of the project is enough.” – The plan covers the whole lifecycle and is updated continuously, including after placing on the market. (high)
  • “Planning is a matter for the security department.” – Without product management, development, production and support, gaps arise at the handovers. (medium)
  • “The support period is a sales topic.” – It determines how long monitoring, updates and risk review must continue. (medium)

References

EN 40000-1-2 · Lifecycle activitiesCRA · Risk assessment in planning, design, development, production, delivery and maintenanceCRA · Support period

What to do

  • Create a cybersecurity plan per product or product family: activities, responsible persons, dates, inputs and expected outputs.
  • Define and justify the support period early – it determines the effort for monitoring and updates.
  • Interlock the plan with the development process: sprint, release or phase gates with cybersecurity criteria.
  • Track progress measurably and feed deviations into the risk review.
Review question for product ownership

Is there a maintained plan for each product that shows which cybersecurity activities are due until the end of the support period – and who is responsible for them?

Evidence you can present

  • Cybersecurity plan with activities, roles and dates
  • Defined and justified support period
  • Gate records with cybersecurity criteria

Planning cybersecurity across the lifecycle

Standards map

EN 40000-1-2 in the standards framework of the Cyber Resilience Act

Where Part 1-2 stands, what comes before and after it and which standards you can already use today. Filter by level and contribution; information as of 22 November 2026.

2CRA standards published: EN 40000-1-1 and EN 40000-1-2
0CRA standards cited in the Official Journal so far
41standards planned under Standardisation request M/606
11 Dec 2027full application of the Cyber Resilience Act
12 of 12 entries
StandardSubjectSignificance for manufacturersStatus
EN 40000-1-1:2026EN 40000-1 (horizontal)TerminologyPart 1-1 · VocabularyCommon terms and definitions for the entire EN 40000 series, without technical requirements of its own. Those who set up risk assessment and documentation according to Part 1-2 use this terminology.Published in November 2026 · not in the Official JournalTerminology
EN 40000-1-2:2026EN 40000-1 (horizontal)Principles, product risk management and lifecycle activitiesPart 1-2 · this pageHorizontal foundation standard for all products with digital elements: four principles, baseline requirements for risk management and activities from planning to decommissioning. Framework for the product-specific standards.Published · available since 18 November 2026 · no citation expectedRisk managementLifecycle
FprEN 40000-1-3EN 40000-1 (horizontal)Vulnerability handlingPart 1-3 · Vulnerability HandlingIs intended to specify the obligations after placing on the market: detecting, documenting and fixing vulnerabilities, coordinated disclosure, secure distribution of updates. Draws on ISO/IEC 29147 and ISO/IEC 30111.Formal vote · no decision yet on citation in the Official JournalVulnerabilities
prEN 40000-1-4EN 40000-1 (horizontal)Generic security requirementsPart 1-4 · Generic Security RequirementsIntended to specify the technical requirement areas of the essential requirements, such as access control, confidentiality, integrity and availability. Until then, manufacturers derive measures themselves from their risk assessment.In preparation · delivery deadline under the standardisation request October 2027Technical requirements
ETSI EN 304 …Product-specificProduct-specific standards for important and critical productsETSI · vertical standardsVertical standards for individual product categories, such as browsers, password managers, VPN products or operating systems. They are meant to build on the horizontal framework and – once cited in the Official Journal – can give rise to a presumption of conformity for their category.Drafts in the voting stageProduct categoryTechnical requirements
EN IEC 62443-4-1 · -4-2InternationalSecure development process and technical requirements for componentsIEC 62443 · Industry and OTRecognized state of the art for industrial components. The process requirements of Part 4-1 overlap strongly with the lifecycle activities of EN 40000-1-2; an adaptation to the CRA is in progress.Published · CRA adaptation in progressLifecycleTechnical requirements
ISO/IEC 29147 · ISO/IEC 30111InternationalVulnerability disclosure and processes for vulnerability handlingISO/IEC · internationalInternational basis for coordinated disclosure and internal handling of vulnerabilities – the bridge from the monitoring activity in Part 1-2 to vulnerability handling in Part 1-3.Published · internationalVulnerabilities
ISO/IEC 27005 · ISO 31000InternationalInformation security risk management and general risk managementISO/IEC · internationalWell-known methodology from the ISMS environment. The logic of context, assessment and treatment is compatible; however, EN 40000-1-2 requires the product focus and the communication of residual risks to users.Published · internationalRisk management
ETSI EN 303 645Other frameworksCybersecurity of connected consumer devicesETSI · Consumer IoTWidely used baseline requirements for connected consumer devices, such as no universal default passwords, update capability and a point for reporting vulnerabilities. A good template for technical measures, but not a CRA standard.Published · not cited for the CRATechnical requirements
EN 18031-1 · -2 · -3Other frameworksCybersecurity of radio equipmentRadio Equipment Directive · delegated regulationHarmonised standards for connected radio equipment, whose cybersecurity requirements have applied since 1 August 2025. For many radio products a predecessor in substance – not a substitute for the evidence under the CRA.Cited in the Official Journal, with restrictions · for the Radio Equipment DirectiveTechnical requirements
ISO/SAE 21434 · IEC 81001-5-1Other frameworksEngineering standards for vehicles and health softwareSector legislation · outside the CRAAuthoritative for type-approved vehicles (UN R155) and medical devices (MDR/IVDR), which are excluded from the CRA. Methodologically closely related – manufacturers with products in both worlds can set up their processes jointly.Published · sector legislationRisk managementLifecycle
C/2026/6013Other frameworksCommission guidance on the application of the CRACommission · not bindingInterpretation of scope, substantial modification, support period, open source and remote data processing – the guardrails within which you apply the methodology of Part 1-2.Official Journal C of 17 November 2026Risk management

Status information based on the CEN project entry for EN 40000-1-2, the announcement by CEN and CENELEC of 19 November 2026 and public project information; citations change only with publication in the Official Journal. Compilation and assessment: VamiSec, not legal advice.

Deep dive

EN 40000-1-2 in detail

Ten chapters from classification through principles, risk management and lifecycle to the implementation roadmap – for product owners, development leads and compliance.

01Chapter 1

What EN 40000-1-2 is – and what it is not

The first horizontal standard with requirements supporting the Cyber Resilience Act gives manufacturers a common methodology for cybersecurity risks across the entire product lifecycle. It is not proof of conformity.

EN 40000-1-2:2026 is titled “Cybersecurity requirements for products with digital elements – Part 1-2: Principles, product risk management, and lifecycle activities”. The standard sets out general cybersecurity principles, baseline requirements for the management of cybersecurity risks and activities with which these risks can be reduced. Its aim: to establish and maintain an appropriate, risk-based level of cybersecurity across the entire lifecycle – from design to the end of support and decommissioning.

2 Nov 2026Ratification by CEN and CENELEC
18 Nov 2026Definitive text available
31 May 2027Latest date for the national versions
35.030ICS classification IT security

Who developed it

The joint working group CEN-CLC/JTC 13/WG 9 is responsible; it develops horizontal cybersecurity standards for products with digital elements, and the secretariat is held by the Dutch standardisation institute NEN. According to CEN and CENELEC, more than 450 experts from 28 national standardisation bodies and 17 partner organisations contributed; the work received financial support from the EU executive agency EISMEA under the STAN4CR grant. The basis is Standardisation request M/606, with which the Commission mandated CEN, CENELEC and ETSI to develop standards in support of the CRA.

What the standard delivers

  • Common language: together with the terminology part EN 40000-1-1, a uniform vocabulary for manufacturers, assessment bodies and authorities.
  • Methodology: a product-related risk management process with fixed building blocks.
  • Lifecycle: activities that anchor cybersecurity from planning to decommissioning.
  • Framework: baseline requirements on which coherent product-specific standards are meant to build.

What it does not deliver

EN 40000-1-2 contains no concrete technical requirements for individual product categories – it expressly leaves those to the vertical standards. And according to the CEN project entry, no citation in the Official Journal of the European Union is expected. It therefore lacks the effect that harmonised standards have in European product law: the presumption that a product complying with the standard meets the legal requirements.

02Chapter 2

Status: published, but without a presumption of conformity

In European product law, it is not the publication of a standard that determines its legal effect, but its citation in the Official Journal. For Part 1-2, none is expected.

The Cyber Resilience Act follows the New Legislative Framework: the Regulation sets essential requirements, and harmonised standards describe how they can be met. Only when the Commission publishes the reference of a standard in the Official Journal does the presumption of conformity with the covered requirements apply to products that comply with it.

CharacteristicStatus for EN 40000-⁠1-⁠2
Status at CENPublished
Ratification (DOR)2 November 2026
Availability (DAV)18 November 2026
National announcement by (DOA)28 February 2027
National publication by (DOP)31 May 2027
Withdrawal of conflicting national standards (DOW)31 May 2027
Legal referenceCyber Resilience Act, Standardisation request M/606
Citation in the Official JournalNot expected
Presumption of conformityNone

Source: CEN project entry JT013089, retrieved on 22 November 2026.

What this means in practice

  • Default category: internal control by the manufacturer is possible anyway. EN 40000-1-2 structures your evidence but does not replace it.
  • Important products of Class I: self-assessment is open only with fully applied harmonised standards, common specifications or a suitable European certification scheme – or for free and open-source software with public technical documentation. Part 1-2 does not meet this condition; until suitable cited standards or common specifications exist, the route is via a notified body.
  • Class II and critical products: third-party assessment or certification is required – for Class II, the only exception is free and open-source software with public technical documentation; the standard provides the methodology for preparation.
  • Technical documentation: manufacturers list the cited harmonised standards, common specifications or certification schemes applied; where none were applied, they describe the chosen solutions together with a list of other relevant technical specifications applied. EN 40000-1-2 can be named there – the link to the individual essential requirements remains your justification.
03Chapter 3

The standards framework: horizontal, vertical and what follows

EN 40000-1-2 is the starting point of a standards family. Those who understand its logic can place the following parts in context before they appear.

Standardisation request M/606 of 3 February 2025 foresees 41 standards: horizontal standards that apply to all products and vertical standards for specific categories of important and critical products. CEN and CENELEC are developing the horizontal parts EN 40000-1-x and some of the product-specific standards – some of them also with an EN 40000 number, such as EN 40000-10 for identity and access management –, ETSI vertical standards of the EN 304 series. In November 2026, the Commission slightly postponed the delivery deadlines planned for 2026: to 30 November 2026 for the horizontal standards on risk-based design, development and production and on vulnerability handling, and to 31 January 2027 for the vertical standards.

PartSubjectRole in the frameworkStatus 22 November 2026
EN 40000-⁠1-⁠1TerminologyCommon vocabulary of the seriespublished, not cited in the Official Journal
EN 40000-⁠1-⁠2Principles, risk management, lifecycleMethodological framework for all products and for the vertical standardspublished, no citation expected
FprEN 40000-⁠1-⁠3Vulnerability handlingRequirements after placing on the marketformal vote
prEN 40000-⁠1-⁠4Generic security requirementsTechnical requirement areas of the essential requirementsin preparation
Vertical standardsCategories of important and critical productsConcrete requirements per categorydrafts in the voting stage

Status according to CEN and CENELEC and public project information.

Why the framework matters

The product-specific standards are meant to build on the baseline requirements of Part 1-2. For manufacturers, this means: those who structure their risk management process according to Part 1-2 today do not have to rebuild it when the standard for their own product category appears – they supplement it with its concrete requirements.

04Chapter 4

The four principles: risk-based, secure by design, secure by default, transparent

The principles describe the stance from which risk management and lifecycle activities are carried out. They coincide with the guiding ideas of the CRA’s essential requirements.

Risk-based approach

The appropriate level of cybersecurity results from the risks of the specific product in its context – not from a blanket checklist. Measures are selected with justification, residual risks deliberately accepted.

Security by design

Security is designed in from the start: small attack surface, least privilege, defense in depth and secure coding. Later corrections are more expensive and rarely complete.

Secure by default

The delivery state is secure: unneeded services are disabled, secure default values are set, and resetting to the original state is easily possible.

Transparency

Users learn what they need to know for security: whether updates are available, what the current security status is, which risks remain and what to do in the event of security incidents.

How the principles feed into the CRA

PrincipleLink to the CRA’s essential requirements (in essence)
Risk-based approachDesign, development and production with an appropriate level of cybersecurity based on the risks
Security by designLimit attack surfaces, reduce the impact of incidents, control access, protect confidentiality and integrity
Secure by defaultMaking available with a secure by default configuration and the possibility to reset the product to its original state
TransparencyInformation and instructions for users, indication of the support period, notes on security updates

Mapping: VamiSec. The standard places the principles up front as orientation for risk management and lifecycle.

05Chapter 5

Product context and risk acceptance: the foundation of every assessment

Before a single risk is assessed, the standard clarifies what is being talked about: the product in its context – and the yardsticks by which risks are measured.

The product context describes the intended purpose, the reasonably foreseeable use, the functions, the operating environment, an overview of the architecture and the users. If remote data processing forms part of the product – such as a cloud backend developed in-house or on the manufacturer’s behalf without which a function does not work – it is part of this context.

  • Intended purpose: what the manufacturer intends the product for, including the information in the instructions for use, advertising and technical documentation.
  • Reasonably foreseeable use: how the product is realistically also used – for example in the home network instead of the isolated industrial network.
  • Operating environment: networks, connected systems, physical access, environmental conditions.
  • Architecture overview: components, interfaces, data flows and trust boundaries.
  • Users: roles, knowledge and responsibilities – from the end customer to administration.

Criteria for risk acceptance

Acceptance criteria define which risk a manufacturer is willing to bear and which not. The standard requires them before the assessment; in our view, regulatory requirements and the state of the art, among other things, should feed into them. Without them, every treatment decision remains arbitrary – and not comparable between products.

  1. Capture the context

    Document purpose, use, environment, architecture and users per product.

  2. Define the criteria

    Company-wide scales for likelihood and impact, thresholds for acceptance and authorities for acceptance decisions.

  3. Maintain the context

    Update the context on new functions, markets or user groups and trigger a reassessment.

06Chapter 6

Assess, treat, communicate, review

The standard’s risk management cycle does not end with the list of measures: residual risks are communicated to users, and the assessment continues until the end of the support period.

  1. Building block 1Product context

    Describe purpose, foreseeable use, operating environment, architecture and users.

  2. Building block 2Risk acceptance criteria

    Define yardsticks for tolerable and intolerable risks.

  3. Building block 3Risk assessment

    Identify assets and their protection goals, derive threats, estimate likelihood and impact and assess against the criteria.

  4. Building block 4Risk treatment

    Avoid or reduce risks, document measures, reassess residual risks and accept them with justification.

  5. Building block 5Risk communication

    Pass on remaining risks, countermeasures and conditions for secure use to users in an understandable way.

  6. Building block 6Review

    Reassess at planned intervals and on occasions such as product changes, a new threat landscape or new vulnerabilities.

How to recognize good assessments

  • Traceable: every rating can be traced back to context, threat and criteria.
  • Complete: all assets, interfaces and lifecycle phases are considered – including production, updates and decommissioning.
  • Linked: risks give rise to requirements, requirements to tests, test results to new assessments.
  • Current: date, version and occasion of the last review are documented.

From risk to essential requirement

The risk assessment under the CRA must show whether and how the individual security requirements of the Regulation apply to the product and how they are implemented. The cycle of EN 40000-1-2 provides the justifications for this: a requirement applies because a threat is relevant; it is adequately implemented when the chosen measures reflect the state of the art and traceably bring the risk below the acceptance threshold.

Example: router for consumersRiskTreatmentResidual risk and communication
Remote maintenance interfaceTakeover via weak credentialsIndividual credentials per device, remote maintenance disabled in the delivery stateNote on secure activation in the instructions
Update channelTampered firmwareSigned updates, verification in the deviceInformation on available updates and the end of support
Remote data processing (app backend)Leakage of user dataEncryption, access control, loggingSecurity and data protection notices for users

Simplified example by VamiSec for illustration – not a reproduction of the standard.

07Chapter 7

Lifecycle activities: from planning to decommissioning

The second core of the standard describes what must happen during the product’s life for risk management to take effect. Every activity follows the same pattern.

EN 40000-1-2 describes activities, not a process model. For each activity, it defines which inputs it needs, which requirement applies, which output results and by which criteria fulfilment can be assessed. This makes the standard suitable as a framework for process descriptions, audits and the technical documentation.

Activity or cross-cutting topicCore of the requirement (in essence)Typical output
PlanningPlan, maintain and track activities for the entire lifecycleCybersecurity plan
RequirementsDerive from context and risk assessment and keep up to dateRequirements catalog with traceability
DesignDefine architecture and protective measures, consider integrationThreat model, architecture
DevelopmentDevelop in a secure environment, maintain component list and documentationCode, SBOM, documentation
Verification and validationAnalyze, scan and test – recurringTest reports
Production and deliveryProtect integrity and authenticity up to placing on the marketSigned artifacts, manufacturing records
Monitoring and issue managementObserve sources, handle issues without undue delayMonitoring and triage records
DecommissioningPrepare secure resetting and retirementDeletion and retirement procedures
Third-party componentsDue diligence before integration, monitoring afterwardsComponent review, SBOM matching

Summary by VamiSec based on publicly available descriptions of the standard; the text of the standard is authoritative.

Agile, DevSecOps or V-model

Because the standard describes activities rather than phases, they can, in our assessment, also be carried out in parallel and iteratively. In agile teams, requirements, threat modeling and tests move into every iteration; planning lives in the backlog and release gates. What matters is that inputs, outputs and assessment criteria are documented traceably.

08Chapter 8

Third-party components, open source and SBOM

Hardly any product consists only of its own code. The standard treats third-party components as a topic of their own that accompanies the entire lifecycle.

Before integration comes due diligence, afterwards verification and ongoing monitoring. This corresponds to the CRA’s due diligence obligation: when integrating third-party components, manufacturers must exercise due diligence so that these do not compromise the cybersecurity of the product – expressly also for free and open-source software that has not been made available on the market in the course of a commercial activity.

  • Selection: assess maintenance status, security history, response times of the maintainers, origin and license.
  • Recording: components with their version in the SBOM – at least the top-level (direct) dependencies are required; the entire chain is better.
  • Monitoring: match the SBOM continuously against new vulnerabilities, triage with deadlines.
  • Feedback: report vulnerabilities found to maintainers or suppliers and share fixes.
  • End of maintenance: plan replacement or your own maintenance before a component drops out of support.
09Chapter 9

Evidence: technical documentation and conformity assessment

The results of the lifecycle activities are the building blocks of your technical documentation. Who reviews them depends on the product class.

The technical documentation under the CRA contains, among other things, a description of design, development and production, the assessment of cybersecurity risks, information on vulnerability handling including the SBOM, test reports and the list of cited harmonised standards applied – or, where none were applied, the description of the chosen solutions with a list of other technical specifications applied. EN 40000-1-2 provides a structure for most of these building blocks.

Building block of the technical documentationWhat EN 40000-⁠1-⁠2 contributes
Description of design, development and productionResults of the activities from planning to production
Assessment of cybersecurity risksProduct context, acceptance criteria, assessment, treatment, residual risks
Information on the support periodPlanning and decommissioning as inputs
Vulnerability handling and SBOMMonitoring, issue management and third-party components – deepened by Part 1-⁠3
Test reportsVerification and validation
Standards applied or solutions describedNaming EN 40000-⁠1-⁠2 among the other technical specifications applied – the justification per essential requirement remains yours

Mapping: VamiSec.

Conformity assessment by product class

Product classPossible proceduresRole of EN 40000-⁠1-⁠2
Default categoryInternal control (module A)Methodology and structure of the evidence
Important, Class IModule A only with fully applied harmonised standards, common specifications or European certification (at least assurance level “substantial”) or as free and open-source software with public technical documentation; otherwise module B+C or module HDoes not open module A, but eases the assessment by the notified body
Important, Class IIModule B+C, module H or European certification (at least assurance level “substantial”); for free and open-source software with public technical documentation also module APreparation of the third-party assessment
CriticalEuropean certification where required; otherwise as for Class IIPreparation of the certification

Procedures under the Cyber Resilience Act, presented in simplified form.

10Chapter 10

Implementation roadmap: anchoring EN 40000-1-2 in 180 days

There is time until the CRA applies in full on 11 December 2027 – but not much, if processes, tools and documentation have to be adapted for several products.

  1. Days 1–30Inventory

    Product inventory with CRA classification, support periods and responsible persons; gap analysis of the existing development and risk process against EN 40000-1-2, for example with the readiness check on this page.

  2. Days 31–90Define the methodology

    Company-wide risk acceptance criteria, templates for product context and risk assessment, mapping of existing processes such as IEC 62443-4-1 to the lifecycle activities; pilot on a representative product.

  3. Days 91–180Roll out and evidence

    Risk assessments for all products, release gates with cybersecurity criteria, automated SBOM and automated monitoring, technical documentation structured according to the standard.

  4. OngoingTrack the standards landscape

    Observe Part 1-3, Part 1-4 and the product-specific standards of your category, check citations in the Official Journal and supplement processes.

Roles and responsibility

  • Management: approve risk acceptance criteria and resources – residual risks are business decisions.
  • Product management: own product context, support period and user information.
  • Development and architecture: threat modeling, secure development and tests.
  • Production and procurement: integrity through to delivery and diligence for third-party components.
  • Product security and PSIRT: monitoring, vulnerability handling and reporting.
Readiness check

EN 40000-1-2 readiness check: How far along are risk management and lifecycle?

In about ten minutes, work through up to 29 questions in eight action areas – with live evaluation, a maturity level per area, your biggest gaps, a 30/90/180-day roadmap and the evidence you should prepare. Your answers stay in your browser.

0 / 29 questions answered

00 / 08Your product profile

Three inputs control the check. Whether at least one of your products is important or critical determines the target level. Product type and existing products show or hide matching questions – the core questions on product context, risk assessment, lifecycle and third-party components apply to every manufacturer.

  1. Is at least one of your products an important (Class I or II) or critical product?

    What counts is the core functionality: exactly one per product, determined objectively. Important and critical products generally undergo third-party assessment – which is why we apply the highest target level to them.

  2. Which types of products with digital elements do you place on the market?

    Multiple selection possible. Devices/hardware includes firmware; remote data processing means backend services that you develop yourself or that are developed on your behalf and without which a product function does not work. Some questions apply only to certain product types.

  3. After 11 December 2027, will you place on the market products that are already in development or on the market today?

    Typical for series products and maintained software: every unit or version placed on the market from 11 December 2027 must comply with the Regulation. “Yes” shows a question on retroactive risk assessment.

Target level3 — Effective & verifiable

For important and critical products, we assume Level 3 (“Effective & verifiable”): your evidence is generally reviewed by a notified body or as part of a certification and must withstand third-party scrutiny. The target level is a classification by VamiSec.

Foundation

First the Regulation, then the standard: the CRA deep dive

EN 40000-1-2 presupposes the Regulation: which products are covered, which classes apply and which deadlines run is governed by the Cyber Resilience Act. Our CRA deep dive explains the obligations, the page on the CRA guidance the Commission’s interpretation – and this page the methodology for risk and lifecycle.

RegulationObligations, product classes, deadlines
GuidanceThe Commission’s interpretation, not binding
EN 40000-1-2Methodology for risk management and lifecycle
  • Reporting obligations since 11 September 2026, full application from 11 December 2027.
  • The guidance of 17 November 2026 clarifies, among other things, scope, substantial modification, support period and remote data processing.
  • Part 1-3 on vulnerability handling follows as the next part of the series.

The wording of the Regulation and the text of the standard are authoritative. This page summarizes and puts into context; it does not replace legal advice.

VamiGRC

هكذا تطبّقون ذلك مع VamiGRC

يمرّر VamiGRC منتجاتكم عبر بوابات إصدار محددة، ويربط متطلبات CRA بالمرحلة المناسبة، ويصل بين SBOM والموردين والأدلة – وصولًا إلى البلاغ المُعدّ مسبقًا إلى BSI وENISA.

Glossary

Glossary: the terms around EN 40000-1-2

27 terms from the standard and the Regulation – each with the German term.

EN 40000-1-2Grundsätze, Produktrisikomanagement und Lebenszyklusaktivitäten
Horizontal European standard on the Cyber Resilience Act with cybersecurity principles, baseline requirements for risk management and lifecycle activities for products with digital elements. Available since 18 November 2026; citation in the Official Journal is not expected.
EN 40000-1-1Begriffe
Terminology part of the series with common terms and definitions, published together with Part 1-2; it contains no technical requirements of its own.
FprEN 40000-1-3Schwachstellenbehandlung
Part on vulnerability handling after placing on the market. The abbreviation FprEN denotes the draft standard in the formal vote.
Cyber Resilience Act (CRA)Cyberresilienzverordnung
EU regulation on horizontal cybersecurity requirements for products with digital elements. In force since 10 December 2024; the rules for conformity assessment bodies have applied since 11 June 2026, the reporting obligations since 11 September 2026, all other obligations from 11 December 2027.
Product with digital elementsProdukt mit digitalen Elementen
Software or hardware product and its remote data processing solutions, including components placed on the market separately. The CRA covers it where its intended purpose or reasonably foreseeable use includes a direct or indirect logical or physical data connection to a device or network.
Harmonised standardHarmonisierte Norm
European standard developed at the request of the Commission. It gives rise to a presumption of conformity only once its reference has been published in the Official Journal of the European Union.
Presumption of conformityKonformitätsvermutung
Legal consequence whereby a product that complies with a harmonised standard cited in the Official Journal, a common specification or a European cybersecurity certification scheme designated for this purpose is presumed to meet the requirements covered by it; the presumption is rebuttable. EN 40000-1-2 does not give rise to it.
Standardisation request M/606Normungsauftrag M/606
Request of the Commission to CEN, CENELEC and ETSI of 3 February 2025 to develop 41 standards in support of the CRA; individual delivery deadlines were adjusted in November 2026.
Horizontal standardHorizontale Norm
Standard that applies to all products with digital elements, regardless of product category – like parts EN 40000-1-1 to EN 40000-1-4.
Vertical (product-specific) standardVertikale Norm
Product-specific standard for a category of important or critical products, for example from the ETSI EN 304 series. It is meant to build on the framework of EN 40000-1-2.
Product contextProduktkontext
Description of the intended purpose, foreseeable use, functions, operating environment, architecture and users of a product – the starting point of the risk assessment.
Intended purposeBestimmungsgemäßer Zweck
Use for which the manufacturer intends the product, including the context and conditions of use as specified in the instructions for use, promotional or sales material and technical documentation.
Reasonably foreseeable useVernünftigerweise vorhersehbare Verwendung
Use that does not necessarily correspond to the intended purpose stated by the manufacturer but which is likely to result from reasonably foreseeable human behavior or technical operations or interactions.
Risk acceptance criteriaRisikoakzeptanzkriterien
Yardsticks defined in advance by which a risk is considered tolerable or intolerable; the basis of every treatment decision.
Residual riskRestrisiko
Risk that remains after risk treatment. It is assessed, accepted with justification and communicated to users.
Risk communicationRisikokommunikation
Passing on remaining risks, countermeasures and conditions for secure use to users in an understandable form.
Security by designSicherheit durch Gestaltung
Principle of anchoring security in architecture and implementation from the start – with a small attack surface, least privilege and defense in depth.
Secure by defaultSichere Voreinstellungen
Principle of making products available in a secure delivery state: secure default values, unneeded services disabled, simple reset to the original state.
Support periodUnterstützungszeitraum
Period during which the manufacturer must handle vulnerabilities effectively. It reflects the expected use time and is at least five years; if the product is expected to be in use for a shorter time, it corresponds to that use time.
Software bill of materials (SBOM)Software-Stückliste (SBOM)
Machine-readable inventory of a product’s components. The CRA requires it in a commonly used format and at least covering the top-level dependencies.
Remote data processingDatenfernverarbeitung
Data processing at a distance for which the software is designed and developed by, or under the responsibility of, the manufacturer, and the absence of which would prevent the product from performing one of its functions.
Third-party componentDrittkomponente
Software or hardware component obtained from third parties, including free and open-source software. The manufacturer’s due diligence obligation applies to it.
Notified bodyBenannte Stelle
Notified conformity assessment body that carries out procedures such as EU-type examination or the assessment of full quality assurance.
Internal control (module A)Interne Kontrolle (Modul A)
Conformity assessment by the manufacturer itself. Always possible for the default category; for Class I only with fully applied harmonised standards, common specifications or a suitable European certification scheme. For free and open-source software in Classes I and II, it is sufficient to make the technical documentation public when placing the product on the market.
Technical documentationTechnische Dokumentation
Documents with which the manufacturer demonstrates fulfilment of the essential requirements – including the risk assessment, test reports and the standards applied or solutions described.
DOR, DAV, DOA, DOP, DOWCEN-Umsetzungstermine
Ratification, availability of the definitive text to the national standardisation bodies, latest date for national announcement, latest date for national publication and latest date for withdrawal of conflicting national standards. For EN 40000-1-2: 2 November 2026, 18 November 2026, 28 February 2027, 31 May 2027, 31 May 2027.
CEN-CLC/JTC 13/WG 9Gemeinsame Arbeitsgruppe von CEN und CENELEC
Joint working group of CEN and CENELEC for horizontal cybersecurity standards for products with digital elements; the secretariat is held by the Dutch standardisation institute NEN.
FAQ

Frequently asked questions about EN 40000-1-2

Short answers to questions that product management, development and compliance ask about EN 40000-1-2.

The standard sets out general cybersecurity principles, baseline requirements for the management of cybersecurity risks and activities across the entire lifecycle of products with digital elements – from design to the end of support and decommissioning. It applies horizontally to all product categories and forms the framework for the product-specific standards on the Cyber Resilience Act.

It was developed under the standardisation request for the CRA but, according to the CEN project entry, will not be cited in the Official Journal of the European Union. It therefore does not give rise to a presumption of conformity. It is a published European standard that manufacturers apply voluntarily as a methodology.

CEN and CENELEC ratified it on 2 November 2026; the definitive text has been available since 18 November 2026, and on 19 November 2026 the organizations announced the publication. Nationally, the standard must be adopted by 31 May 2027 at the latest, in Germany as DIN EN 40000-1-2.

No. The standard structures risk assessment, development process and documentation, but contains no product-specific technical requirements. You continue to provide the evidence that your product meets the essential requirements of the Regulation yourself – in the technical documentation, with a description of the chosen solutions.

No. For internal control in Class I, harmonised standards, common specifications or a European cybersecurity certification scheme of at least assurance level “substantial” must be fully applied. Since Part 1-2 is not cited, the route until then is via a notified body. Independently of the standard, there is an exception for free and open-source software whose technical documentation is public when it is placed on the market.

Part 1-1 contains the terminology, Part 1-2 principles, risk management and lifecycle activities, Part 1-3 vulnerability handling and the planned Part 1-4 generic technical security requirements. So far, Parts 1-1 and 1-2 have been published; Part 1-3 is in the formal vote, Part 1-4 in preparation.

Six building blocks: establish the product context, define risk acceptance criteria, assess risks, treat risks, communicate residual risks to users and review the assessment regularly and on specific occasions – for example on product changes or new vulnerabilities.

For software placed on the market as a product with digital elements – such as installable applications, apps or firmware – yes. Pure online services are not in themselves a product within the meaning of the CRA. They form part of a product’s remote data processing if the product manufacturer designed and developed their software itself or under its responsibility and the product could not perform one of its functions without them; they then belong in the product context and risk assessment.

No. The development process under IEC 62443-4-1 overlaps strongly with the lifecycle activities of EN 40000-1-2. A mapping makes sense: which practices cover which activity, and where are building blocks missing? Frequently this concerns risk acceptance criteria, communication of residual risks to users, decommissioning and the ongoing monitoring of third-party components.

No. An ISMS manages the organization’s information security risks. EN 40000-1-2 requires risk management per product that includes the users and the entire product lifecycle. Methodology, roles and tools from the ISMS can, however, be readily reused.

The reporting obligations for actively exploited vulnerabilities and severe security incidents apply independently of the standard. EN 40000-1-2 supports them through the Monitoring and issue management activity: those who systematically observe sources and handle issues without undue delay recognize reportable cases in good time. Vulnerability handling in detail is to be governed by Part 1-3.

European standards are distributed by the national standardisation bodies, in Germany by DIN through DIN Media. When the national version appears depends on the respective publication schedule – by 31 May 2027 at the latest. The draft has been available since March 2026 as E DIN EN 40000-1-2 in German and English versions.

المعايير والمصادر

يستند محتوى هذه الصفحة إلى الأدلة والدراسات التالية المتاحة للعموم.

CEN-CENELEC · 2026

CRA Milestone Unlocked: First European standards supporting CRA are now available!

Announcement of 19 November 2026 on the publication of EN 40000-1-1 and EN 40000-1-2 – working group, contributors and next parts

CEN-CENELEC · 2026

EN 40000-1-2:2026 – Project entry JT013089 (CEN/CLC/JTC 13)

Primary source for title, scope, status, implementation dates and citation status; retrieved on 22 November 2026

European Parliament and Council of the EU · 2024

Regulation (EU) 2024/2847 on horizontal cybersecurity requirements for products with digital elements (Cyber Resilience Act)

Legal basis – essential requirements, risk assessment, technical documentation, conformity assessment, reporting obligations

European Commission · 2025

Commission Implementing Decision C(2025) 618 – Standardisation request M/606 in support of the Cyber Resilience Act

Request of 3 February 2025 to CEN, CENELEC and ETSI for 41 horizontal and product-specific standards

European Commission · 2026

Commission Implementing Decision C(2026) 7861 amending Implementing Decision C(2025) 618

Decision of 10 November 2026; replaces the annex with the delivery deadlines of the standardisation request

European Commission · 2026

Annex to Commission Implementing Decision C(2026) 7861 – list of requested standards and deadlines

New deadlines: 30 November 2026 for risk-based design, development and production and for vulnerability handling, 30 October 2027 for the remaining horizontal standards, 31 January 2027 for the vertical standards

European Commission · 2026

Commission guidance on the application of Regulation (EU) 2024/2847, C/2026/6013

Interpretation of scope, substantial modification, support period, open source and remote data processing; OJ C of 17 November 2026

European Commission · 2022

Commission Notice – The ‘Blue Guide’ on the implementation of EU product rules 2022 (2022/C 247/01)

Fundamentals on harmonised standards, citation in the Official Journal and presumption of conformity in the New Legislative Framework

DIN · 2026

E DIN EN 40000-1-2:2026-03 – Draft, German and English version prEN 40000-1-2:2025

German draft standard (123 pages, German and English), at the time under the title “Principles for cyber resilience” (German: “Grundsätze für die Cyberresilienz”)

European Commission · 2026

Cyber Resilience Act – Commission policy page

Overview, implementation status, standardisation and reporting platform

IEC · 2018

IEC 62443-4-1:2018 – Secure product development lifecycle requirements

Requirements for the secure development process for industrial automation components; closely related to the lifecycle activities of EN 40000-1-2

ISO/IEC · 2018

ISO/IEC 29147:2018 – Vulnerability disclosure

Coordinated vulnerability disclosure; reference standard for vulnerability handling

ISO/IEC · 2019

ISO/IEC 30111:2019 – Vulnerability handling processes

Internal processes for handling vulnerabilities; reference standard for vulnerability handling

ETSI · 2024

ETSI EN 303 645 – Cyber Security for Consumer Internet of Things: Baseline Requirements

Widely used baseline requirements for connected consumer devices; not a CRA standard

Bringing EN 40000-1-2 into your product development?

In an initial consultation, we examine how your risk assessment, your development process and your technical documentation fit EN 40000-1-2 and the requirements of the Cyber Resilience Act – and where the biggest gaps are.