The CRA, the Declaration of Conformity, and CE marking

This page is deliberately narrow and deliberately dull. It describes what the Regulation provides. It does not tell you which route, which marking, or which assessment procedure applies to your product, because that is a determination about your product and this page cannot make it.

The declaration of conformity — Article 28, Annex V

Article 28 provides that the EU declaration of conformity is drawn up by manufacturers in accordance with Article 13(12), and states that the fulfilment of the applicable essential cybersecurity requirements set out in Annex I has been demonstrated.

“The EU declaration of conformity shall have the model structure set out in Annex V and shall contain the elements specified in the relevant conformity assessment procedures set out in Annex VIII. Such a declaration shall be updated as appropriate.”

Regulation (EU) 2024/2847, consolidated text 02024R2847-20241120, Article 28(2).

Annex V is a flat list of eight points: product identification, manufacturer identity, the sole-responsibility statement, the object of the declaration, the conformity statement, standards referenced, notified-body details where applicable, and the signature block. Article 28(2) also notes that a simplified EU declaration of conformity, referred to in Article 13(20), has the model structure set out in Annex VI instead.

The technical documentation — Article 31, Annex VII

“The technical documentation shall contain all relevant data or details of the means used by the manufacturer to ensure that the product with digital elements and the processes put in place by the manufacturer comply with the essential cybersecurity requirements set out in Annex I. It shall at least contain the elements set out in Annex VII.”

Regulation (EU) 2024/2847, consolidated text 02024R2847-20241120, Article 31(1).

Article 31(2) adds that the technical documentation is drawn up before the product is placed on the market and is continuously updated, where appropriate, at least during the support period. The two documents are linked: Annex VII point 7 asks for “a copy of the EU declaration of conformity”, so the declaration sits inside the technical file.

The questions this page will not answer

Each of the following is a determination about a specific product, made by its manufacturer with advice, and nothing here should be read as answering any of them:

  • Whether your product is a product with digital elements made available on the EU market, and therefore in scope at all.
  • How pure software-as-a-service or remote data processing is treated. The conditions are specific, and this is an open question rather than a settled exclusion.
  • Whether an open-source or non-commercial exemption reaches your situation. The exemptions carry conditions; they are not blanket.
  • Whether your product falls into one of the categories singled out as important or critical, and what that means for notified bodies or harmonised standards.
  • Which conformity assessment procedure applies, and whether self-assessment is sufficient.
  • What marking obligations follow, and how they interact with any other Union harmonisation legislation your product is already subject to.

Take all of these to counsel. ceproof produces a draft document from the regulation's own structure and from your answers; it makes no determination about classification, and it never writes one into the output.

A generated Annex V declaration of conformity draft →

Draft yours from your own repository

ceproof lays out all 21 items in the regulation's order, cites each one, derives what your repository can evidence, and lists what is still open. Free to scan and to see the gap checklist. $99, one-time to export the Annex VII pack and the Annex V DoC draft.

Needs a repository with an npm or Python manifest. C or C++ firmware is not supported today.