Article 27

Presumption of Conformity, Harmonised Standards, and Common Specifications

Article 27 governs how harmonised European standards and common specifications create a legal presumption of conformity with the CRA's essential cybersecurity requirements. When a manufacturer applies a harmonised standard published in the EU Official Journal, their product is presumed to meet the essential requirements that standard covers. Article 27 also covers common specifications and European cybersecurity certification schemes. Formal objections to harmonised standards follow Article 11 of Regulation (EU) No 1025/2012.

Effective: December 2027Applies to: Manufacturers seeking to use harmonised standards as compliance evidenceLast reviewed: 26 October 2026Verified against: the final text of Regulation (EU) 2024/2847
Source: Regulation (EU) 2024/2847, Article 27, official text on EUR-Lex

What Harmonised Standards Are

Harmonised standards are European standards (EN standards) developed by European standardisation organisations - CEN, CENELEC, or ETSI - following a mandate from the European Commission. Unlike general ISO or IEC standards, harmonised standards are specifically aligned with the essential requirements of EU legislation and, once published in the EU Official Journal, carry the legal presumption of conformity benefit.

For the CRA, the Commission issued standardisation request M/606 by Commission Implementing Decision C(2025) 618 final of 3 February 2025, and CEN, CENELEC and ETSI accepted it on 3 April 2025. The request covers 41 standards for the essential requirements in Annex I. Horizontal standards, the EN 40000 series, apply to every product with digital elements. Vertical standards cover specific product categories.

Prior to harmonised standards becoming available, manufacturers may use existing technical specifications such as ETSI EN 303 645 (consumer IoT), IEC 62443 (industrial automation), or ENISA guidelines as supporting evidence, though these do not provide the formal presumption of conformity.

CRA reference:Article 27(1)

How to Identify Applicable Harmonised Standards

Harmonised standards applicable to the CRA will be published in the EU Official Journal with references indicating which essential requirements they cover. Manufacturers should monitor the Official Journal regularly to identify newly published standards relevant to their product categories.

The European Commission's standardisation database also provides searchable access to published harmonised standards by regulation. ETSI's portal and CEN/CENELEC's standards catalogue list standards under development, giving manufacturers advance notice of upcoming standards they may wish to follow.

For product categories where no harmonised standard yet exists, manufacturers must use alternative means to demonstrate compliance - typically through technical documentation, third-party testing, or reference to relevant ISO/IEC standards - while accepting that no formal presumption of conformity applies.

CRA reference:Article 27(1)

Partial Application of Harmonised Standards

Manufacturers are not required to apply harmonised standards in their entirety. Where a standard covers requirements that are not applicable to a specific product, or where a manufacturer has achieved compliance through different technical means, partial application is permissible. However, the presumption of conformity only applies to the requirements actually covered by the portions of the standard that are applied.

Where a manufacturer deviates from a harmonised standard - for example, by using a different cryptographic algorithm than specified - they must document the deviation and provide alternative evidence that the essential requirement is met. This documentation forms part of the technical file that must be maintained under Annex VII.

Audit trails and version control of standard references are important: where a harmonised standard is revised, manufacturers should assess whether the updated version affects their compliance position.

CRA reference:Article 27(2)

Common Specifications as an Alternative

Where harmonised standards are not yet available or are considered inadequate, Article 27 allows the Commission to adopt 'common specifications' - implementing acts that set out the technical requirements manufacturers may use as an alternative compliance pathway. Common specifications also provide a presumption of conformity for the requirements they cover.

Common specifications are typically used as a transitional measure while the standardisation process catches up with new regulatory requirements, or in areas where the standardisation bodies have not produced suitable standards within a reasonable timeframe. They have the same legal status as harmonised standards for the purposes of the presumption of conformity but are issued by the Commission rather than developed through the European standardisation process.

CRA reference:Article 27(2), Article 27(5)

Scope and Limits of the Presumption

The presumption of conformity is not unlimited. It applies only to:

  1. The specific harmonised standard actually applied (not merely referenced)
  2. The essential requirements that the standard covers
  3. The version of the standard that is currently referenced in the Official Journal

A manufacturer who applies an outdated version of a harmonised standard, or who applies only parts of the standard, benefits from the presumption only to the extent of their actual compliance. Where a product deviates from the standard's requirements - even in minor ways - the presumption may be weakened or lost for the affected requirements.

The presumption also operates at the product level, not the batch level. If a manufacturer discovers a defect in a specific production batch that results in products not meeting the standard, the presumption does not protect those units even if the product design meets the standard.

CRA reference:Article 27(1)

Common Specifications as an Equivalent Pathway

Article 27 extends the presumption of conformity to products conforming to common specifications adopted under Article 7(4). Common specifications are Commission implementing acts that provide technical requirements as an alternative to harmonised standards, typically used where harmonised standards are not yet available or are considered insufficient.

From the manufacturer's perspective, common specifications and harmonised standards are functionally equivalent for presumption purposes - both create the same legal presumption when applied. The procedural differences are on the standards development side: harmonised standards are developed by European standardisation organisations through consultation processes, while common specifications are adopted directly by the Commission.

Manufacturers monitoring the compliance landscape should track both the Official Journal harmonised standards references and any Commission implementing acts adopting common specifications.

CRA reference:Article 27(2)

Interaction with Third-Party Conformity Assessment

For a default-class product, Module A internal control is open (Article 32(1)). A manufacturer that applies a harmonised standard gets the presumption of conformity in Article 27(1) for the requirements the standard covers. That presumption supports the EU declaration of conformity.

For an Annex III Class I product, Module A is open only when the manufacturer fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level at least substantial (Article 32(2)). Otherwise the product goes to EU-type examination (Module B plus Module C) or full quality assurance (Module H). No CRA harmonised standard is cited in the Official Journal yet, so today a Class I product needs a notified body. A standard applied in part still makes the third-party assessment easier, because the assessor can check conformity to the standard instead of each essential requirement separately.

For an Annex III Class II product, Module A is never open. The routes are Module B plus Module C, Module H, or a European cybersecurity certification scheme specified under Article 27(9) at assurance level at least substantial, for the requirements it covers (Article 32(3)). Harmonised standards still reduce the assessment workload, because they give a structured framework for the evaluation.

CRA reference:Article 27(1), Article 32

Maintaining the Presumption Over Time

The presumption of conformity is based on the product's compliance with the harmonised standard at the time of assessment. Manufacturers must maintain their compliance over time - particularly as standards are updated and as new vulnerabilities are discovered.

When a harmonised standard is revised and the new version is published in the Official Journal, manufacturers typically have a transition period to update their products and documentation to the new standard. During the transition period, compliance with the old version continues to create the presumption. After the transition period expires, only the new version maintains the presumption.

Manufacturers should establish a process for monitoring standard updates and assessing whether product updates are required to maintain compliance with current versions.

CRA reference:Article 27, Article 7(1)

Formal Objections to Harmonised Standards

Article 27 contains no procedure to object to a harmonised standard. Formal objections follow Article 11 of Regulation (EU) No 1025/2012. A Member State or the European Parliament that considers that a harmonised standard does not entirely satisfy the requirements it aims to cover informs the Commission with a detailed explanation. After consultation, the Commission decides to publish, not to publish, or to publish with restriction the reference to the standard in the Official Journal. For a reference that is already published, it decides to maintain it, to maintain it with restriction, or to withdraw it.

A restriction or a withdrawal removes the presumption of conformity under Article 27(1) for the requirements concerned. A manufacturer that relies on that standard must then show conformity with those requirements by other means.

Common specifications have a separate route. A Member State that considers that a common specification does not entirely satisfy the essential cybersecurity requirements informs the Commission, and the Commission may amend the implementing act (Article 27(7)).

CRA reference:Article 27(1), Article 27(7)

Process for Raising Objections

The Commission decides on a formal objection after it consults the committee set up by the relevant Union harmonisation legislation, where one exists, or sectoral experts (Regulation (EU) No 1025/2012, Article 11(1)). A decision to publish, not to publish or to publish with restriction follows the advisory procedure. A decision to maintain, to maintain with restriction or to withdraw a published reference follows the examination procedure (Regulation (EU) No 1025/2012, Article 11(4) and (5)).

The Commission publishes information on its website about the standards subject to such a decision. It informs the European standardisation organisation concerned and, if necessary, requests a revision of the standard (Regulation (EU) No 1025/2012, Article 11(2) and (3)). A revised standard can then be proposed for a new reference in the Official Journal. Publication of that reference restores the presumption of conformity for the requirements the standard covers.

CRA reference:Article 27(6)

Implications for Manufacturers

The presumption of conformity in Article 27(1) depends on the published reference. A harmonised standard on which a manufacturer bases its CE marking and technical documentation can be restricted or withdrawn after a formal objection. The manufacturer must then reassess compliance and possibly update products or documentation.

Manufacturers should monitor the Official Journal and the Commission's information on formal objection decisions. Good practice is to keep technical documentation that shows compliance with each essential requirement directly, in addition to the reference to the harmonised standard. This gives resilience against a withdrawn or restricted reference.

Where a standard is subject to an objection, assess whether the decision affects the product. A restriction of one requirement does not affect a product that meets that requirement through other documented means.

CRA reference:Article 27(1)

Distinguishing Formal Objections from Standard Revisions

It is important to distinguish formal objections from the routine process of harmonised standard revision. Standards are regularly updated by standardisation bodies to reflect new technical developments, emerging threats, and improved understanding of security requirements. These routine revisions do not involve the Commission's formal objection process.

When a harmonised standard is revised through normal standardisation processes, the new version is published in the Official Journal, the old version's reference is typically withdrawn after a transition period, and manufacturers migrate to the new version during the transition period. This is a normal part of the compliance lifecycle and should be planned for.

A formal objection decision is exceptional and records a finding that the standard is substantively deficient. They are expected to be relatively rare events rather than routine occurrences.

CRA reference:Article 27(1)

Work through Article 27 for each product in one CRA workspace.

Classify the product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Is it mandatory to follow harmonised standards to comply with the CRA?+

No. Using harmonised standards is voluntary - manufacturers can demonstrate compliance with essential requirements by other means. However, harmonised standards provide the most straightforward route to compliance and the formal presumption of conformity. Using other approaches requires more extensive technical documentation and may face greater scrutiny from conformity assessment bodies and market surveillance authorities.

Which harmonised standards currently apply to the CRA?+

None yet. No CRA harmonised standard is cited in the Official Journal of the European Union, so no standard gives a presumption of conformity today. CEN ratified EN 40000-1-1 and EN 40000-1-2 on 2 November 2026, and gives 18 November 2026 as the date their text becomes available. The CEN project records for EN 40000-1-1 and EN 40000-1-2 mark both “no citation expected” under the CRA, so their publication is not expected to bring a presumption. CEN marks prEN 40000-1-3 on vulnerability handling “citation expected”. Presumption of conformity starts only when the Commission cites a standard in the Official Journal. Until then, ETSI and IEC standards such as ETSI EN 303 645 and IEC 62443 are supporting evidence only. The CRA applies from 11 December 2027, and the Article 14 reporting obligations apply from 11 September 2026.

Does ETSI EN 303 645 provide a presumption of conformity under the CRA?+

ETSI EN 303 645 (Cyber Security for Consumer Internet of Things) aligns well with the CRA's requirements for consumer IoT products, but it only provides the formal presumption of conformity if it has been formally designated as a CRA harmonised standard through the Official Journal publication process. Until that designation occurs, it remains valuable evidence of compliance but without the formal presumption.

Can I use IEC 62443 to demonstrate CRA compliance for industrial products?+

IEC 62443 is highly relevant for industrial automation and control systems and covers many of the essential requirements applicable to such products. As with other non-harmonised standards, it provides strong supporting evidence but does not create a formal presumption of conformity unless designated as a CRA harmonised standard. Monitor the Official Journal for designation updates.

What happens if no harmonised standard covers my product category?+

Where no harmonised standard is available for your product category, you must demonstrate compliance by other means - typically through technical documentation, testing results, expert assessments, or reference to relevant but non-harmonised standards such as ISO/IEC publications or ETSI specifications. The absence of a harmonised standard does not exempt you from meeting the essential requirements; it only means you cannot benefit from the formal presumption of conformity.

Can I use multiple harmonised standards to cover all essential requirements?+

Yes. It is common practice to apply multiple harmonised standards to cover different aspects of a product's requirements. For example, one standard might address network security requirements while another addresses cryptographic algorithm requirements. As long as the combined standards cover all applicable essential requirements, the presumption of conformity applies across all those requirements.

Is the presumption of conformity the same as market approval?+

No. The presumption of conformity means authorities cannot challenge your compliance without evidence of non-compliance - but it is not a market approval granted by a public authority. There is no central EU approval process for CRA compliance. The CE marking and conformity declaration are manufacturer self-declarations (with possible third-party involvement) that are subject to post-market surveillance.

If my product uses a harmonised standard but still has a security vulnerability, does the presumption protect me?+

Not necessarily. If a specific vulnerability demonstrates that the product does not in fact meet the essential requirements - for example, it has an exploitable default credential issue that Annex I Part I(2) prohibits - then the product may not actually conform to the essential requirements, regardless of which standard was applied. The presumption is a procedural tool, not an immunity from substantive requirements.

Has the Commission raised any formal objections against CRA harmonised standards?+

No. No CRA harmonised standard is cited in the Official Journal yet, so there is no reference to object to. Formal objections to harmonised standards follow Article 11 of Regulation (EU) No 1025/2012. Formal objections are an established route under other product legislation. Member States raised them against machinery standards under Article 10 of the Machinery Directive 2006/42/EC. The Machinery Regulation (EU) 2023/1230 that replaces that directive applies only from 20 January 2027.

What should I do if a standard I use is subject to a formal objection?+

First, read the Commission's objection decision carefully to understand which essential requirements are affected. If the objection concerns requirements that your product meets through other documented means, your compliance position may not be materially affected. If the objection covers requirements where your product relies solely on the standard, you should supplement your technical documentation with additional evidence of compliance while the standardisation body revises the standard.

Can manufacturers challenge a formal objection?+

Manufacturers can submit comments during the consultation that precedes the Commission's decision on a formal objection. Once the Commission adopts its implementing decision, it can be challenged through EU administrative and judicial review procedures. However, such challenges are uncommon given the complex technical nature of standardisation disputes and the Commission's broad discretion in this area.

Is there a period where I can continue to use a standard after it has been objected to?+

The Commission's implementing decision typically specifies whether there is a transitional period. In some cases, the standard's reference is immediately withdrawn; in others, a period of several months is allowed for manufacturers to adjust. The implementing decision should be checked carefully for transition provisions.

Need a CVD policy for Article 27?

Annex I Part II(5) asks for a coordinated vulnerability disclosure policy. Download a free template.

Browse templates →