Skip to content
Product and evidence

User information under Annex II CRA: what must accompany a product

8 min read

Every product with digital elements must be accompanied by information and instructions to the user. Annex II of the Cyber Resilience Act sets the minimum content, Art. 13 governs language, form and availability. This guide goes through every point in turn – for manufacturers who write this documentation for their software or device.

What it is about

Manufacturers ensure that their products are accompanied by the information and instructions to the user set out in Annex II, in paper or electronic form (Art. 13(18)). Annex II opens with the words “At minimum, the product with digital elements shall be accompanied by”. The nine points are therefore a minimum content.

The user information is also part of the technical documentation: its general description of the product includes the user information and instructions as set out in Annex II (Annex VII point 1(d)).

The obligations under Art. 13 and Annex II apply from 11 December 2027 (Art. 71(2)).

Source: Art. 13(18) CRA · Annex II CRA · Annex VII point 1(d) CRA · Art. 71(2) CRA

Language, form and availability

  • Language: the information and instructions are provided in a language which can be easily understood by users and market surveillance authorities.
  • Form: they must be clear, understandable, intelligible and legible, and allow for the secure installation, operation and use of the product.
  • Duration: the manufacturer keeps them at the disposal of users and market surveillance authorities for at least 10 years after the product has been placed on the market or for the support period, whichever is longer.
  • Online: where they are provided online, they must be accessible, user-friendly and available online for the same duration.

Recital 94 names translation costs for mandatory documentation, including the information and instructions to the user, as a possibly significant cost, in particular for smaller manufacturers. Member States should therefore be able to consider that one of the languages they determine and accept is one which is broadly understood by the largest possible number of users.

Source: Art. 13(18) CRA · Recital 94 CRA

Points 1 and 2: manufacturer and single point of contact

Point 1 requires the name, registered trade name or registered trademark of the manufacturer, and the postal address, the email address or other digital contact as well as, where available, the website at which the manufacturer can be contacted.

Under Art. 13(16), the same details are also indicated on the product, on its packaging or in a document accompanying the product. The contact details must be in a language which can be easily understood by users and market surveillance authorities.

Point 2 requires the single point of contact where information about vulnerabilities of the product can be reported and received, and where the manufacturer’s policy on coordinated vulnerability disclosure can be found. Art. 13(17) specifies this contact point:

  • The manufacturer designates a single point of contact to enable users to communicate directly and rapidly with it, including in order to facilitate reporting on vulnerabilities.
  • It must be easily identifiable by users and is included in the information and instructions to the user set out in Annex II.
  • Users can choose their preferred means of communication; these must not be limited to automated tools.

Recital 63 adds that the availability of the contact point should be clearly indicated and kept up to date. Where manufacturers offer automated tools such as chat boxes, they should also offer a phone number or other digital means of contact, such as an email address or a contact form.

Annex II and Art. 13(17) both use the term “single point of contact”; Annex II and Annex I Part II point (5) both refer to a “policy” on coordinated vulnerability disclosure.

Source: Annex II, points 1, 2 CRA · Art. 13(16), (17) CRA · Recital 63 CRA · Annex I, Part II, point 5 CRA

Points 3 to 5: product, intended purpose and risks

  • Point 3: name and type and any additional information enabling the unique identification of the product.
  • Point 4: the intended purpose, including the security environment provided by the manufacturer, as well as the product’s essential functionalities and information about the security properties.
  • Point 5: any known or foreseeable circumstance, related to use in accordance with the intended purpose or under conditions of reasonably foreseeable misuse, which may lead to significant cybersecurity risks.

Identification also involves Art. 13(15): the product bears a type, batch or serial number or other element allowing its identification; where that is not possible, the information is provided on the packaging or in a document accompanying the product.

“Intended purpose” means the use for which the product is intended by the manufacturer, including the specific context and conditions of use, as specified in the information supplied by the manufacturer, among others in the instructions for use (Art. 3(23)). “Reasonably foreseeable misuse” means use in a way that is not in accordance with the intended purpose, but which may result from reasonably foreseeable human behaviour or interaction with other systems (Art. 3(25)).

Source: Annex II, points 3–5 CRA · Art. 13(15) CRA · Art. 3(23), (25) CRA

Point 6: EU declaration of conformity

Point 6 requires, where applicable, the internet address at which the EU declaration of conformity can be accessed. In addition, the manufacturer provides either a copy of the EU declaration of conformity or a simplified EU declaration of conformity with the product. Where only the simplified declaration is provided, it must contain the exact internet address at which the full declaration can be accessed (Art. 13(20)). The wording of the simplified declaration is set out in Annex VI.

Source: Annex II, point 6 CRA · Art. 13(20) CRA · Annex VI CRA

Point 7: security support and end date

Point 7 requires the type of technical security support offered by the manufacturer and the end-date of the support period during which users can expect vulnerabilities to be handled and to receive security updates.

  • The end date, including at least the month and the year, is clearly and understandably specified at the time of purchase in an easily accessible manner and, where applicable, on the product, its packaging or by digital means (Art. 13(19)).
  • Where technically feasible in light of the nature of the product, the manufacturer displays a notification to users informing them that their product has reached the end of its support period (Art. 13(19)).

How long the support period must be is governed by Art. 13(8) – see the guide on the support period.

Source: Annex II, point 7 CRA · Art. 13(8), (19) CRA

Point 8: detailed instructions

Point 8 requires detailed instructions – or an internet address referring to such detailed instructions and information – on:

  • (a) the necessary measures during initial commissioning and throughout the lifetime of the product to ensure its secure use;
  • (b) how changes to the product can affect the security of data;
  • (c) how security-relevant updates can be installed;
  • (d) the secure decommissioning of the product, including information on how user data can be securely removed;
  • (e) how the default setting enabling the automatic installation of security updates can be turned off;
  • (f) where the product is intended for integration into other products with digital elements, the information necessary for the integrator to comply with the essential cybersecurity requirements set out in Annex I and the documentation requirements set out in Annex VII.

Point (e) refers to Annex I Part I point (2)(c): vulnerabilities must be able to be addressed through security updates, including, where applicable, through automatic security updates enabled as a default setting, with a clear and easy-to-use opt-out mechanism.

Source: Annex II, point 8 CRA · Annex I Part I point (2)(c) CRA

Point 9: software bill of materials

The manufacturer must draw up a software bill of materials in any case – in a commonly used and machine-readable format covering at the very least the top-level dependencies (Annex I Part II(1)). It is only conditionally part of the user information: if the manufacturer decides to make the software bill of materials available to the user, the user information states where it can be accessed (Annex II, point 9).

Source: Annex II, point 9 CRA · Annex I Part II(1) CRA

What importers and distributors check

  • Before placing the product on the market, importers ensure among other things that it is accompanied by the EU declaration of conformity referred to in Art. 13(20) and the information and instructions to the user as set out in Annex II in an easily understood language, and that the manufacturer has complied with Art. 13(15), (16) and (19) (Art. 19(2)(c), (d)). They indicate their own contact details on the product, its packaging or in a document accompanying the product (Art. 19(4)).
  • Before making the product available, distributors verify that the manufacturer and the importer have complied with Art. 13(15), (16), (18), (19) and (20) and Art. 19(4), and have provided all necessary documents to the distributor (Art. 20(2)(b)).

Source: Art. 19(2), (4) CRA · Art. 20(2) CRA

In practice

A structure that follows the numbering of Annex II makes checking easy – for you, for importers and distributors and for market surveillance. A possible outline:

  1. Manufacturer and contact (point 1)
  2. Reporting vulnerabilities: single point of contact, link to the disclosure policy (point 2)
  3. Product and versions, as shown on the type plate or in the about dialog (point 3)
  4. Intended purpose, operating environment, essential functionalities, security properties (point 4)
  5. Known and foreseeable risks, including misuse (point 5)
  6. EU declaration of conformity: internet address (point 6)
  7. Security support and end date with month and year (point 7)
  8. Instructions (a) to (f), each as its own subsection (point 8)
  9. Software bill of materials, if you make it available (point 9)
  • Publish the documents at a permanent address that survives a website redesign, and keep earlier versions per product version.
  • For software, also link the user information inside the program, for example in the about or help menu.
  • For point (f), think of customers who build your library, SDK or module into their own products: what do they need for their own technical documentation?
  • Plan language versions for all target markets and update them together with every change.

Checklist before shipping

  • All nine points of Annex II included, points (a) to (f) each answered or marked as not applicable with a reason?
  • Contact details and single point of contact up to date, not only automated channels?
  • End date of the support period stated with month and year and visible at the time of purchase?
  • Internet address of the EU declaration of conformity reachable?
  • In a language easily understood by users and authorities for every target market?
  • Online version secured for at least 10 years or the longer support period?
  • Version filed in the technical documentation?

Related guides

Terms in the Cyber Resilience Act glossary

Sources

First published 9 Nov 2026, last updated 9 Nov 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.