Key takeaways
- Annex II of the Cyber Resilience Act lists what a manufacturer must tell the people who actually use a product with digital elements, separate from the technical requirements in Annex I.
- Annex II opens with: "At minimum, the product with digital elements shall be accompanied by" the following.
- Paragraph 15 requires the product to "bear a type, batch or serial number or other element allowing their identification," which is the identification data that feeds Annex II point (3).
- Annex II is what goes to the user, in understandable language, not to a market surveillance authority's file.
Annex II of the Cyber Resilience Act lists what a manufacturer must tell the people who actually use a product with digital elements, separate from the technical requirements in Annex I. It covers nine points: who to contact, where to report a vulnerability, how to identify the product, what it is for and what could go wrong, how long security support lasts, and instructions for secure installation, updating and decommissioning. Article 13 of Regulation (EU) 2024/2847 makes this binding and adds rules on language, format, timing and retention.
What is Annex II of the Cyber Resilience Act?
Annex II is titled "Information and instructions to the user." Where Annex I sets the essential cybersecurity requirements a product and its manufacturer's processes must meet, and Annex VII lists the technical documentation a manufacturer keeps on file for market surveillance authorities, Annex II is the user-facing counterpart: the minimum information that must physically or digitally accompany the product so that the person using it — not a regulator — knows who made it, how to reach them, how long it will be supported, and how to use, update and retire it securely.
Article 13(18) is the operative clause that turns Annex II from a list into a legal duty: "Manufacturers shall ensure that products with digital elements are accompanied by the information and instructions to the user set out in Annex II, in paper or electronic form." The same paragraph requires that information to be in a language users and market surveillance authorities can easily understand, and to be "clear, understandable, intelligible and legible," allowing for the secure installation, operation and use of the product.
What exactly must a manufacturer tell the user, point by point?
Annex II opens with: "At minimum, the product with digital elements shall be accompanied by" the following. This table paraphrases each point next to the regulation's own wording.
| Annex II point | What the regulation says | Plain-English meaning |
|---|---|---|
| (1) | "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" | Basic manufacturer contact details |
| (2) | "the single point of contact where information about vulnerabilities of the product with digital elements can be reported and received, and where the manufacturer's policy on coordinated vulnerability disclosure can be found" | Where a researcher or user reports a security issue, and a link to the CVD policy |
| (3) | "name and type and any additional information enabling the unique identification of the product with digital elements" | Model/type/batch/serial identification |
| (4) | "the intended purpose of the product with digital elements, including the security environment provided by the manufacturer, as well as the product's essential functionalities and information about the security properties" | What the product is for, the security environment it assumes, and its security properties |
| (5) | "any known or foreseeable circumstance, related to the use of the product with digital elements in accordance with its intended purpose or under conditions of reasonably foreseeable misuse, which may lead to significant cybersecurity risks" | Known or foreseeable situations, including misuse, that could create significant cybersecurity risk |
| (6) | "where applicable, the internet address at which the EU declaration of conformity can be accessed" | Link to the EU declaration of conformity |
| (7) | "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" | What kind of support is offered, and the date it ends |
| (8) | "detailed instructions or an internet address referring to such detailed instructions" covering (a)-(f) below | Secure-use instructions, which can be a link rather than a printed manual |
| (9) | "If the manufacturer decides to make available the software bill of materials to the user, information on where the software bill of materials can be accessed" | SBOM access info, only if the manufacturer chooses to publish the SBOM to users |
Point (8)'s six sub-points, quoted directly from the regulation, are the detailed instructions (or the link to them):
- (a) "the necessary measures during initial commissioning and throughout the lifetime of the product with digital elements to ensure its secure use"
- (b) "how changes to the product with digital elements can affect the security of data"
- (c) "how security-relevant updates can be installed"
- (d) "the secure decommissioning of the product with digital elements, including information on how user data can be securely removed"
- (e) "how the default setting enabling the automatic installation of security updates, as required by Part I, point (2)(c), of Annex I, can be turned off"
- (f) "where the product with digital elements 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 (8)(e) and (8)(f) are the two places Annex II explicitly cross-references another annex in its own text: (e) points back to the automatic-update default in Annex I Part I point (2)(c), and (f) points to both Annex I (essential requirements) and Annex VII (technical documentation) for the specific case of a component meant to be integrated into someone else's product.
Which article makes this binding, and what does it add on top of the list?
Article 13 — "Obligations of manufacturers" — is where Annex II stops being a list and becomes an enforceable duty, and it layers several requirements on top of the bare annex text:
- Paragraph 16 requires the manufacturer's name, trade name or trademark and contact details to appear on the product, its packaging, or an accompanying document, and in the Annex II information — tying point (1) to physical/packaging labelling, not just a manual.
- Paragraph 17 requires manufacturers to "designate a single point of contact to enable users to communicate directly and rapidly with them, including in order to facilitate reporting on vulnerabilities," that the point of contact be "easily identifiable by the users," included in the Annex II information, and that it "allow users to choose their preferred means of communication" rather than being limited to automated tools only.
- Paragraph 18 sets the format and durability rules: paper or electronic form, understandable language, clear and legible, and — this is a distinct retention duty from the technical-documentation retention in paragraph 13 — the Annex II information itself must be kept available to users and market surveillance authorities for "at least 10 years after the product with digital elements has been placed on the market or for the support period, whichever is longer," with the same minimum period applying to online accessibility if provided that way.
- Paragraph 19 puts a sharper point on Annex II point (7): the support-period end date "including at least the month and the year" must be "clearly and understandably specified at the time of purchase in an easily accessible manner," not just somewhere in the documentation — on the product, its packaging, or by digital means where applicable — and, "where technically feasible," the manufacturer must notify users when the product actually reaches end of support.
- Paragraph 15 requires the product to "bear a type, batch or serial number or other element allowing their identification," which is the identification data that feeds Annex II point (3).
- Paragraph 8 is where the support period itself gets defined — manufacturers determine it based on expected use time, with a floor of five years unless the product's expected use is genuinely shorter — and that determination is what point (7)'s end-date disclosure and paragraph 19's point-of-purchase disclosure both report on.
How does Annex II relate to Annex I and the technical documentation?
They are three different audiences for three different things, and the regulation's own cross-references in point (8)(e) and (8)(f) confirm the link rather than leaving it implicit:
- Annex I sets what the product and the manufacturer's processes must actually be — secure by default, updatable, vulnerabilities handled — and Annex II point (8)(e) directly cross-references Annex I Part I point (2)(c) (the automatic-update default) when describing the instruction for turning that default off.
- Annex VII ("Content of the technical documentation," confirmed from the regulation's own table of contents) is what the manufacturer keeps on file for market surveillance authorities to inspect — the evidence behind the conformity claim. Annex II point (8)(f) cross-references Annex VII specifically for the case of a component meant to be integrated into another product: the integrator needs enough information to meet Annex VII's documentation requirements for the combined product, not just Annex I's technical requirements.
- Annex II is what goes to the user, in understandable language, not to a market surveillance authority's file. A user doesn't need the full technical documentation; they need the contact point, the support end date, and instructions they can act on.
Put together: Annex I is the substance, Annex VII is the regulator's evidence trail, and Annex II is the user's instruction sheet — each one accompanying the product for a different reader. For the Annex I side, see our CRA Annex I explained guide; this guide has deliberately not repeated Annex I's point-by-point content here.
What happens if a manufacturer gets this wrong?
This guide's fetched sources describe Article 13's obligations and Annex II's list itself in detail, but did not surface the specific enforcement or penalty clause text (Chapter VII covers "Confidentiality and penalties," Articles 63-65) in enough verified detail to state a specific fine figure or enforcement mechanism here with confidence. What is clear from Article 13 itself is that Annex II is not optional paperwork: paragraph 18's retention duty, paragraph 19's point-of-purchase disclosure rule, and paragraph 17's single-point-of-contact requirement are all drafted as "shall" obligations sitting alongside the same Article 13 duties (technical documentation, EU declaration of conformity, CE marking) that trigger market surveillance action under Chapter V when a product is found non-compliant. Treat missing or buried Annex II information as a compliance gap of the same kind as a missing declaration of conformity, not a minor documentation nicety — and confirm the actual penalty regime against Articles 63-65 before relying on any specific figure.
What should a device maker check first?
Write down the support period and its end date before anything elseAnnex II point (7) and Article 13(19) both hinge on this one decision — and until the manufacturer has actually determined the support period under Article 13(8) (five-year floor unless expected use is shorter), there is nothing concrete to disclose at the point of purchase. Stand up a real single point of contact, not just an inboxArticle 13(17) requires it to be easily identifiable and to let users choose their communication method — a security.txt file or a dedicated vulnerability-reporting address that nobody monitors will not satisfy "communicate directly and rapidly." Decide what format the Annex II instructions takeA link is allowed for the detailed point (8) instructions, but the core identification, contact and support-period information still needs to reach the user in a form they will actually see — packaging, an insert, or a prominent in-app/web location. Confirm the update-opt-out instruction actually existsPoint (8)(e) requires telling users how to turn off automatic security updates where that default exists under Annex I — this only works if the product genuinely has that default and that off-switch built in first. Decide, separately, whether to publish the SBOM to usersPoint (9) only applies if the manufacturer chooses to make the SBOM available to users; keeping one is mandatory under Annex I regardless, but telling users where to find it is a business decision this annex does not force. Mark 11 December 2027 on the compliance calendarRegulation (EU) 2024/2847 applies in full — including Article 13 and Annex II — from that date (Article 71(2)); only Article 14's reporting duty (11 September 2026) and Chapter IV's notified-body rules (11 June 2026) move earlier, and neither changes the Annex II deadline itself.
A manufacturer's Annex II disclosures are only as accurate as the underlying facts about the firmware they describe — the components it actually contains, the vulnerabilities known against them, and what a realistic update and support commitment looks like given what is actually shippable. SoftWSP's device firmware security service scans a binary firmware image, builds a software bill of materials, matches components against published vulnerabilities, and produces a prioritised fix list and vulnerability report; that evidence is what a manufacturer needs on hand before writing an honest support-period end date or update-mechanism description into their own Annex II documentation. The service does not draft a manufacturer's Annex II user information itself — see device firmware security for what the report does and does not cover.
This guide is built from the verbatim text of Annex II and the relevant paragraphs of Article 13 and Article 71 of Regulation (EU) 2024/2847, fetched directly for this guide (EUR-Lex's own rendering of the regulation did not return readable page content during this research, so the quoted text was cross-verified against a dedicated CRA reference source, StreamLex, which reproduces the Official Journal annex and article text). The enforcement/penalty mechanism in Chapter VII (Articles 63-65) was not independently verified in detail for this guide and is flagged above rather than stated as fact. This guide is general information, not legal advice — confirm any specific clause against the official EUR-Lex text before relying on it in a compliance submission.
Sources
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Annex II and Article 13, Official Journal text, EUR-Lex
- StreamLex: CRA Annex II — Information and Instructions to the User (verbatim annex text)
- StreamLex: CRA Article 13 — Obligations of manufacturers (verbatim article text, paragraphs 15-20 on Annex II)
- StreamLex: CRA Article 71 — Entry into force and application
- European Commission: CRA summary of the legal text
Frequently asked questions
What is Annex II of the Cyber Resilience Act?
Annex II, titled 'Information and instructions to the user,' is the list of information a manufacturer must put in front of users of a product with digital elements: contact details, the single point of contact for reporting vulnerabilities, product identification, intended purpose and known risks, the support-period end date, and detailed secure-use instructions. Article 13(18) of Regulation (EU) 2024/2847 makes this binding.
Does Annex II require publishing the SBOM to users?
No, not automatically. Annex II point (9) only triggers 'if the manufacturer decides to make available the software bill of materials to the user' — in that case, the user information must say where to find it. Keeping an SBOM at all is a separate, mandatory duty under Annex I Part II point (1); publishing it to users is optional.
How long must a manufacturer keep Annex II information available?
Article 13(18) requires manufacturers to keep the Annex II information and instructions available to users and market surveillance authorities for at least 10 years after the product is placed on the market, or for the support period, whichever is longer. If provided online, that same information must stay accessible, user-friendly and online for the same minimum period.
What does a manufacturer have to say about the support period, specifically?
Two separate things. Annex II point (7) requires stating the type of technical security support offered and the end-date of the support period. Article 13(19) adds a stricter rule on top: that end date, including at least the month and year, must be clearly and understandably specified at the time of purchase, not buried in a manual — on the product, its packaging, or by digital means where applicable.
When does the Annex II obligation apply?
Regulation (EU) 2024/2847 applies in full, including Article 13 and Annex II, from 11 December 2027 (Article 71(2)). Two narrower provisions apply earlier: Article 14's vulnerability/incident reporting duty from 11 September 2026, and Chapter IV's notified-body rules from 11 June 2026 — neither of those earlier dates changes when Annex II itself becomes enforceable.
Can the Annex II instructions just be a web link instead of a printed manual?
Yes, for the detailed instructions. Annex II point (8) explicitly allows 'detailed instructions or an internet address referring to such detailed instructions.' Article 13(18) requires the information to be in paper or electronic form, in a language users and market surveillance authorities can easily understand, and clear, understandable, intelligible and legible.
In this cluster


