CRA requirements for manufacturers: Article 13 obligations and Annex I

The Cyber Resilience Act's manufacturer requirements sit in Article 13 and Annex I: design to Annex I Part I based on a documented risk assessment, run the Part II vulnerability-handling processes for a support period, report under Article 14, document, assess conformity and CE-mark.

By the Vellaci teamPublished Updated 8 min readOperational guidance, not legal advice

Share:LinkedInXE-mail

Key facts

Core article
Article 13 — 25 paragraphs of manufacturer obligations
Product requirements
Annex I Part I — an appropriate level of cybersecurity based on the risks, plus 13 properties (a)–(m) applied according to the risk assessment
Process requirements
Annex I Part II — eight vulnerability-handling requirements, including an SBOM covering at least top-level dependencies
Reporting
Article 14 — actively exploited vulnerabilities and severe incidents, since 11 September 2026
Applies in full
11 December 2027 (Art. 71(2)); earlier products only if substantially modified (Art. 69(2))
Fines
Up to €15 million or 2.5 % of worldwide annual turnover for breaches of Annex I, Article 13 or Article 14 (Art. 64(2))

How the requirements are organised

Article 13 is the manufacturer's checklist. Its first paragraphs tie product design to Annex I Part I through a risk assessment; the middle paragraphs establish vulnerability handling and the support period by reference to Annex I Part II; the later paragraphs cover documentation, conformity assessment, identification, user information, corrective action and cooperation with authorities. Article 14 adds reporting, Article 31 and Annex VII the technical documentation, Article 32 the conformity procedures, and Articles 28 to 30 the declaration and CE marking. Nothing in the list is optional; how each item is met depends on the product and its risks.

Article 13 obligations, grouped

Art. 13ObligationWhat it means in practice
(1)–(4)Design, develop and produce to Annex I Part I on the basis of a documented cybersecurity risk assessment, updated during the support period and included in the technical documentationA per-product risk assessment that states how each Annex I point applies, with justifications for anything not applicable
(5)Exercise due diligence when integrating third-party components, including open sourceSBOM, provenance and maintenance signals per component; a policy for abandoned dependencies
(6)Report vulnerabilities found in an integrated component to its maintainer and share fixesAn upstream-reporting rule in the disclosure process
(7)Systematically document relevant cybersecurity aspects, including known vulnerabilities and third-party informationA decision record per finding; risk assessment updates
(8)Handle vulnerabilities per Annex I Part II for a support period of at least five years unless expected use is shorter; have CVD policiesSupport period with rationale; a working vulnerability-handling workflow
(9)Keep each security update available for at least ten years or the rest of the support period, whichever is longerAn archive of security updates with retention
(10)–(11)For successive substantially modified software versions, remediation may be limited to the latest version if users can move to it free of charge; public archives must warn about unsupported versionsA version policy and archive notices
(12)–(14)Technical documentation, conformity assessment, EU declaration of conformity and CE marking; keep them for ten years or the support period; keep series production in conformityAnnex VII file per product; chosen procedure; retention
(15)–(17)Identification of the product, manufacturer contact details and a single point of contact for users, including for vulnerability reportsProduct labelling and a published, human-reachable contact
(18)–(20)User information per Annex II, the support period end date (at least month and year) at the time of purchase, and the declaration or a simplified declarationProduct pages and documentation that show the support end date
(21)–(23)Corrective action, withdrawal or recall on non-conformity; cooperation with market surveillance; notice before ceasing operationsA non-conformity procedure and an authority-request playbook
(24)–(25)The Commission may specify the SBOM format; ADCO may request SBOMs for Union-wide dependency assessmentsSBOMs kept in a format you can hand over on request

Annex I Part I: product properties

Point (1) requires an appropriate level of cybersecurity based on the risks. Point (2) lists the properties that apply 'on the basis of the cybersecurity risk assessment and where applicable' — which is why the risk assessment must say, for each one, whether and how it applies.

PointRequirementTypical evidence
(2)(a)No known exploitable vulnerabilities when made availableRelease gate on vulnerability matching; triage records
(2)(b)Secure by default configuration, with a reset to the original stateDefault configuration specification; test results
(2)(c)Vulnerabilities addressable through security updates, automatic by default where applicable, with opt-out and postponementUpdate mechanism description
(2)(d)Protection from unauthorised access, and reporting of possible unauthorised accessAuthentication and access-control design; logs
(2)(e)–(f)Confidentiality and integrity of stored, transmitted and processed data, commands, programs and configurationEncryption and signing design; integrity checks
(2)(g)Data minimisationData inventory per function
(2)(h)–(i)Availability of essential functions, including against denial of service, and limited impact on other devices and networksResilience tests; rate limiting
(2)(j)–(k)Limited attack surface and exploitation mitigationInterface inventory; hardening and compiler or runtime mitigations
(2)(l)Security-relevant logging and monitoring, with a user opt-outLogging specification
(2)(m)Secure, permanent removal of all data and settings, and secure transfer where supportedReset and wipe procedure; test

Annex I Part II: vulnerability handling

Part II applies to the manufacturer's processes for the support period: identify and document components and vulnerabilities, including an SBOM; remediate without delay, with security updates separate from feature updates where technically feasible; test and review regularly; disclose fixed vulnerabilities once an update is available; put in place and enforce a coordinated vulnerability disclosure policy; provide a contact address for reports; distribute updates securely and, where applicable, automatically; and disseminate security updates without delay and free of charge with advisory messages. The vulnerability-handling guide treats each of the eight in detail.

Article 14: reporting

Manufacturers notify actively exploited vulnerabilities and severe incidents having an impact on the security of the product, simultaneously to the CSIRT designated as coordinator and to ENISA through the single reporting platform: an early warning within 24 hours of awareness, a notification within 72 hours and a final report — 14 days after a corrective measure for vulnerabilities, one month after the notification for incidents. They also inform impacted users. Of all the CRA's requirements, this is the one already in force for every product on the market.

What applies now, and what applies from December 2027

RequirementApplies fromProducts placed on the market before 11 December 2027
Article 14 reporting11 September 2026Yes — all in-scope products (Art. 69(3))
Notified-body framework (Chapter IV)11 June 2026Not a product obligation
Annex I, Article 13, documentation, conformity assessment, CE marking11 December 2027Only if substantially modified from that date (Art. 69(2))
Importer and distributor obligations11 December 2027For products they place or make available from that date

Other economic operators

The manufacturer carries most of the load, but the CRA assigns duties along the supply chain — and turns some operators into manufacturers.

RoleMain dutiesArticle
Authorised representativeActs under a written mandate: keeps the declaration and documentation available for ten years, provides them on request, cooperates with authorities. The design, vulnerability-handling and documentation obligations of Art. 13(1)–(11), (12) first subparagraph and (14) cannot be delegated to itArt. 18
ImporterPlaces only conforming products on the market; checks conformity assessment, technical documentation, CE marking, declaration and user information before doing soArt. 19
DistributorActs with due care; checks CE marking and that manufacturer and importer obligations on identification and information are metArt. 20
Importer or distributor under its own brand, or after a substantial modificationBecomes a manufacturer, subject to Articles 13 and 14Art. 21
Any other person who substantially modifies a product and makes it availableBecomes a manufacturer for the modified part, or the whole product if security as a whole is affectedArt. 22
Open-source software stewardDocumented cybersecurity policy, cooperation with authorities and Article 14 reporting to the extent involved in development; no CE markingArt. 24

Turning the requirements into a plan

  1. Inventory the products you place on the EU market and confirm scope per product, including remote data processing.
  2. Classify each product and choose the conformity route.
  3. Write the risk assessment per product, mapping every Annex I Part I point to controls or a justification.
  4. Stand up the Part II processes: SBOM per release, continuous matching, triage with reasons, disclosure policy, update distribution and advisories.
  5. Keep the Article 14 runbook live and rehearsed.
  6. Assemble the Annex VII documentation as the work happens, and fix the support period and its public end date.

Frequently asked questions

What are the main requirements of the Cyber Resilience Act?
For manufacturers: secure design to Annex I Part I based on a documented risk assessment; vulnerability handling under Annex I Part II for a support period of at least five years (unless expected use is shorter), including an SBOM; reporting of actively exploited vulnerabilities and severe incidents under Article 14; technical documentation; conformity assessment, EU declaration of conformity and CE marking; and user information including the support end date.
Which CRA requirements apply today?
Article 14 reporting has applied since 11 September 2026 to all in-scope products, and the notified-body framework since 11 June 2026. The other requirements apply from 11 December 2027 to products placed on the market from that date, and to earlier products only if they are substantially modified.
Does every Annex I requirement apply to every product?
Point (1) of Part I and all of Part II apply to every product. The properties in Part I point (2) apply on the basis of the risk assessment and where applicable; where one does not apply, the technical documentation must contain a clear justification (Art. 13(3)–(4)).
Do SaaS products have CRA requirements?
A service delivered purely as software-as-a-service is not in itself a product with digital elements. Cloud software comes into scope as remote data processing when a product depends on it to perform one of its functions; it is then assessed together with that product. Downloadable or installable software is a product in its own right.
What are the penalties for not meeting CRA requirements?
Member States set the penalties within Article 64: up to €15 million or 2.5 % of worldwide annual turnover for breaches of Annex I, Article 13 or Article 14; up to €10 million or 2 % for many other obligations; and up to €5 million or 1 % for supplying incorrect, incomplete or misleading information to authorities or notified bodies — whichever amount is higher.

From requirement to evidence

What the obligations in this guide mean for an engineering, security or compliance team, the Vellaci workflow that supports each one, and the records it leaves. The full map for every CRA obligation is on the CRA compliance software page.

How to read this. Official requirement summarises the text of Regulation (EU) 2024/2847 with its reference. What your team does is Vellaci’s operational interpretation, not legal advice. Vellaci workflow and Evidence describe what the product does today. Methodology · reviewed 2026-10-05.

  1. Due diligence on third-party components

    Article 13(5)Applies from 11 Dec 2027
    Official requirement
    Exercise due diligence when integrating components sourced from third parties, including free and open-source software, so that they do not compromise the product's cybersecurity.
    What your team does (interpretation)
    Know which third-party and open-source components each version ships, watch them for new vulnerabilities over the support period, and record why a risky component was accepted.
    Vellaci workflow
    Component catalogue across all SBOMs with product usage, continuously matched against OSV and GitHub advisories, enriched with CISA KEV and EPSS. How it works
    Evidence produced
    • Which products and versions ship a component
    • Match history with source and fetch time
    • Recorded risk acceptance with reason
  2. Coordinated vulnerability disclosure and contact address

    Annex I, Part II(5)–(6)Applies from 11 Dec 2027
    Official requirement
    Put in place and enforce a policy on coordinated vulnerability disclosure, and facilitate the sharing of information about potential vulnerabilities, including by providing a contact address for reporting them.
    What your team does (interpretation)
    Publish a reachable intake channel (for example security.txt), a disclosure policy with response targets, and keep a record of reports received and how they were handled.
    Vellaci workflow
    CVD settings per organisation: vulnerability contact, reporting URL, security.txt status, published policy URL, intake instructions and acknowledge / triage / fix targets; policy template aligned with ISO/IEC 29147. How it works
    Evidence produced
    • Recorded contact point, security.txt and policy URL
    • Response targets (acknowledge, triage, fix)
    • Changes to the settings in the audit log
  3. Support period

    Article 13(8)Applies from 11 Dec 2027
    Official requirement
    Handle vulnerabilities effectively for the support period, and determine that period so it reflects the time the product is expected to be in use; it is at least five years unless the product is expected to be in use for less.
    What your team does (interpretation)
    Record a support end date and its rationale per product, keep handling vulnerabilities for every version still inside it, and plan what happens at end of support.
    Vellaci workflow
    Support period with rationale per product, end-of-support alerts, vulnerability handling per supported version. How it works
    Evidence produced
    • Support period and rationale on the product record
    • Version list showing which versions are still supported
  4. Cybersecurity risk assessment

    Article 13(2)–(3)Applies from 11 Dec 2027
    Official requirement
    Undertake an assessment of the cybersecurity risks of the product, take its outcome into account during planning, design, development, production, delivery and maintenance, document it and update it as appropriate during the support period.
    What your team does (interpretation)
    Write the risk assessment per product, link it to the Annex I controls it justifies, and revisit it when vulnerabilities or incidents change the picture.
    Vellaci workflow
    Risk assessment section in the per-product technical documentation workspace, with version history; per-product obligations view. How it works
    Evidence produced
    • Versioned risk assessment section with author and status
    • Link between findings and the assessment they updated
  5. Technical documentation

    Article 13(12)–(13); Article 31; Annex VIIApplies from 11 Dec 2027
    Official requirement
    Draw up the technical documentation before placing the product on the market, containing at least the elements in Annex VII, and keep it, with the EU declaration of conformity, at the disposal of market surveillance authorities for at least ten years after placing on the market or for the support period, whichever is longer.
    What your team does (interpretation)
    Assemble the Annex VII file progressively from records you already keep — SBOMs, vulnerability handling, risk assessment, support period, test reports — instead of writing it once before an audit.
    Vellaci workflow
    Fourteen Annex VII-oriented sections per product with status, version history and evidence links, exported as a ZIP technical package. How it works
    Evidence produced
    • Section versions with author and approval status
    • ZIP technical package (product record, SBOMs, sections, evidence index)

See every obligation mapped to a workflow.

The requirement map links each CRA obligation to the Vellaci workflow that operates it and the evidence it leaves.