FAQEUCyber Resilience Act

EU Cyber Resilience Act FAQ Manufacturer Obligations

Use this CRA FAQ to understand what Article 13 requires from manufacturers before launch, during the support period, and when vulnerabilities, incidents, or authority requests arise.

Built for product security, engineering, legal, certification, and compliance teams responsible for CRA manufacturer duties.

Author
Sorena AI
Published
Mar 10, 2026
Updated
Mar 10, 2026
Sections
41

Structured answer sets in this page tree.

Primary sources
4

Cited legal and guidance references.

Publication metadata
Sorena AI
Published Mar 10, 2026
Updated Mar 10, 2026
Overview

CRA manufacturer obligations span the full product lifecycle. This FAQ focuses on Article 13 duties, risk assessment, support-period decisions, vulnerability handling, documentation, declarations, user information, reporting, and corrective action obligations that remain with the manufacturer even when work is outsourced.

Search this module

Find a question or answer quickly

41 of 41 sections
Section 1

Who is the manufacturer under the CRA?

Under the CRA, the manufacturer is the natural or legal person who develops or manufactures a product with digital elements, or has it designed, developed, or manufactured, and markets it under its own name or trademark, whether for payment, monetisation, or free of charge.

Citations
Recommended next step

Use EU Cyber Resilience Act FAQ Manufacturer Obligations as a cited research workflow

Research Copilot can turn EU Cyber Resilience Act FAQ Manufacturer Obligations into a reusable cited workflow for teams implementing EU Cyber Resilience Act FAQ.

Section 2

What are the manufacturer's core duties under the CRA?

The manufacturer has two central duties.

First, when placing a product with digital elements on the market, it must ensure that the product has been designed, developed, and produced in accordance with the essential cybersecurity requirements in Annex I Part I. Second, when placing the product on the market and for the support period, it must ensure that vulnerabilities of the product, including its components, are handled effectively in accordance with Annex I Part II.

Citations
Section 3

Do the manufacturer's CRA duties stop once the product is launched?

No.

Article 13 requires the manufacturer to take the cybersecurity risk assessment into account during planning, design, development, production, delivery, and maintenance. The CRA therefore covers both pre-market design and post-market vulnerability handling.

Citations
Section 4

Must the manufacturer carry out a cybersecurity risk assessment?

Yes.

The manufacturer must undertake a cybersecurity risk assessment for the product and use it to minimise cybersecurity risks, prevent incidents, and minimise their impact, including in relation to users' health and safety.

Section 5

Does the CRA prescribe one mandatory risk-assessment methodology?

No.

The CRA does not mandate a single methodology. The manufacturer may choose its approach, but it still has to identify the relevant risks, document how those risks were treated, and be able to demonstrate compliance to market surveillance authorities.

Section 6

What must the manufacturer's risk assessment cover?

At minimum, it must analyse cybersecurity risks based on the intended purpose, reasonably foreseeable use, the conditions of use such as the operational environment or assets to be protected, and the length of time the product is expected to be in use.

It must also indicate whether and how Annex I Part I point (2) applies, how those requirements are implemented, and how the manufacturer applies Annex I Part I point (1) and Annex I Part II. The Commission FAQ also states that the risk assessment needs to cover the entire product with digital elements, including remote data processing when in scope and supporting functions that form part of the product.

Section 7

Does the manufacturer need to update the risk assessment after launch?

Yes.

The CRA says the risk assessment must be documented and updated as appropriate during the support period. The manufacturer must also systematically document relevant cybersecurity aspects, including vulnerabilities it becomes aware of and relevant information provided by third parties, and update the risk assessment where applicable.

Citations
Section 8

Must the manufacturer implement every essential cybersecurity requirement in Annex I Part I in the same way for every product?

No.

The manufacturer must determine, on the basis of the cybersecurity risk assessment, which Annex I Part I requirements are relevant to the product. Where certain essential cybersecurity requirements are not applicable, the manufacturer must include a clear justification in the technical documentation. By contrast, the vulnerability-handling requirements in Annex I Part II apply throughout the support period.

Citations
Section 9

If interoperability needs or other constraints make an Annex I Part I requirement not fully applicable, can the manufacturer just ignore it?

No.

Article 13(4) allows justified non-applicability, but recital 55 and the Commission FAQ make clear that the manufacturer still has to assess the resulting risks and address them by other means where needed, for example through limits on intended use or user information.

Citations
Section 10

Does the manufacturer have to exercise due diligence on third-party components?

Yes.

The manufacturer must exercise due diligence when integrating third-party components so those components do not compromise the cybersecurity of the product. This expressly includes free and open-source software components that were not made available on the market in the course of a commercial activity.

Citations
Section 11

Does due diligence mean the manufacturer can only use CE-marked components?

No.

The Commission FAQ says manufacturers can integrate components that do not bear the CE marking, but they still have to exercise due diligence to ensure those components do not compromise the cybersecurity of the finished product.

Citations
Section 12

What must the manufacturer do if it finds a vulnerability in an integrated component?

The manufacturer must report the vulnerability to the person or entity manufacturing or maintaining that component and must address and remediate the vulnerability in accordance with Annex I Part II. If the manufacturer developed a software or hardware modification to address the vulnerability, it must share the relevant code or documentation with the component manufacturer or maintainer where appropriate.

Citations
Section 13

How does the manufacturer determine the support period?

The support period must reflect the length of time during which the product is expected to be in use.

Article 13(8) says the manufacturer must take into account, in particular, reasonable user expectations, the nature of the product including its intended purpose, and relevant Union law determining product lifetime. It may also take into account the support periods of similar products, the availability of the operating environment, the support periods of core third-party components, and relevant ADCO or Commission guidance.

Section 14

Is there a minimum support period?

Yes, in most cases.

Article 13(8) says the support period must be at least five years, unless the product is expected to be in use for less than five years, in which case the support period corresponds to that expected use time. Where the product is reasonably expected to be in use for longer than five years, the support period should be longer.

Citations
Section 15

What does the manufacturer have to do during the CRA support period?

It must ensure effective vulnerability handling for the product, including its components, in line with Annex I Part II.

That includes addressing and remediating vulnerabilities without delay in relation to the risks posed, applying regular tests and reviews, maintaining coordinated vulnerability disclosure arrangements, facilitating vulnerability reporting, and securely distributing updates.

Citations
Section 16

Must the manufacturer patch every vulnerability it discovers?

No.

The Commission FAQ says the CRA does not require a dedicated patch for every vulnerability. The manufacturer must assess the relevance and risk of the vulnerability and ensure that an appropriate remedy is put in place without delay. Depending on the risk, that remedy might be a patch, a mitigation, updated instructions, or another corrective measure.

Citations
Section 17

Is the manufacturer responsible if users do not install security updates?

Not in that sense.

The Commission FAQ says the manufacturer's duty is to make security updates available and to provide the mechanisms required by the CRA, including automatic installation where applicable, user notification, and secure distribution. But the CRA does not make the manufacturer responsible where a user does not install available updates, for example after opting out.

Citations
Section 18

Must the manufacturer keep security updates available after release?

Yes.

Each security update made available during the support period must remain available for at least 10 years after issuance or for the remainder of the support period, whichever is longer.

Citations
Section 19

Can the manufacturer support only the latest substantially modified software version?

In some cases, yes.

Where the manufacturer has placed subsequent substantially modified versions of a software product on the market, it may ensure compliance with Annex I Part II point (2) only for the latest version it placed on the market, provided that users of earlier versions have access to that latest version free of charge and without additional hardware or software adjustment costs.

Citations
Section 20

Can the manufacturer keep a public CRA software archive of old versions?

Yes.

The CRA allows public software archives that improve access to historical versions. If the manufacturer does this, users must be clearly informed in an easily accessible manner about the risks associated with using unsupported software.

Citations
Section 21

What must the manufacturer do before placing the product on the market?

Before placing the product on the market, the manufacturer must draw up the technical documentation, carry out the applicable conformity assessment procedure or have it carried out, draw up the EU declaration of conformity once conformity is demonstrated, and affix the CE marking.

Citations
Section 22

How long must the manufacturer keep the technical documentation and EU declaration of conformity?

For at least 10 years after placing the product on the market or for the support period, whichever is longer.

Citations
Section 23

Does the manufacturer have to keep series production in conformity?

Yes.

The manufacturer must ensure that procedures are in place so products that are part of a series of production remain in conformity. It must adequately take into account changes in development, production, design, product characteristics, and relevant harmonised standards, certification schemes, or common specifications.

Citations
Section 24

What product identification and contact information must the manufacturer provide?

The manufacturer must ensure that the product bears a type, batch, serial number, or other identifying element. It must also indicate its name, trade name or trademark, and postal address and email address or other digital contact details and, where applicable, website, on the product, packaging, or accompanying document.

That same contact information must also be included in the information and instructions to the user.

Citations
Section 25

Must the manufacturer provide a single point of contact for vulnerability reporting?

Yes.

The manufacturer must designate a single point of contact so users can communicate directly and rapidly with it, including for vulnerability reporting. The single point of contact must be easily identifiable, must let users choose their preferred means of communication, and must not limit communication to automated tools.

Citations
Section 26

Must the manufacturer provide information and instructions to users?

Yes.

The manufacturer must ensure that the product is accompanied by the Annex II information and instructions, in paper or electronic form, in a language easily understood by users and market surveillance authorities. They must be clear, understandable, intelligible, and legible and must allow secure installation, operation, and use.

Citations
Section 27

Must the manufacturer disclose the support-period end date to buyers?

Yes.

The manufacturer must clearly and understandably specify the end date of the support period, at least month and year, at the time of purchase in an easily accessible manner and, where applicable, on the product, packaging, or by digital means. Where technically feasible, it must also notify users when the product has reached the end of its support period.

Citations
Section 28

Must the manufacturer include the EU declaration of conformity with the product?

Yes, either in full or in simplified form.

The manufacturer must provide either a copy of the full EU declaration of conformity or a simplified EU declaration of conformity with the product. If the simplified version is used, it must contain the exact internet address where the full declaration can be accessed.

Section 29

Must the manufacturer report actively exploited vulnerabilities and severe incidents?

Yes.

Under Article 14, the manufacturer must notify actively exploited vulnerabilities and severe incidents having an impact on the security of the product. The key CRA deadlines are an early warning within 24 hours of becoming aware and a fuller notification within 72 hours. After that, the final report deadline differs: for an actively exploited vulnerability it is no later than 14 days after a corrective or mitigating measure is available, while for a severe incident it is within one month after the incident notification.

Citations
Section 30

After becoming aware of an actively exploited vulnerability or severe incident, must the manufacturer also inform users?

Yes.

Article 14(8) requires the manufacturer to inform impacted users, and where appropriate all users, of the vulnerability or incident and any risk-mitigation or corrective measures users can deploy. If the manufacturer does not inform users in a timely manner, the notified CSIRTs may do so where necessary and proportionate.

Section 31

Can the manufacturer shift its core Article 13 duties to an authorised representative?

No.

Article 18(2) says the obligations in Article 13(1) to (11), Article 13(12) first subparagraph, and Article 13(14) cannot form part of the authorised representative's mandate. Those remain the manufacturer's own responsibilities.

Citations
Section 32

What must the manufacturer do if it knows or has reason to believe the product is not in conformity?

From placing on the market and for the support period, the manufacturer must immediately take the corrective measures necessary to bring the product or the manufacturer's processes into conformity, or withdraw or recall the product as appropriate.

Section 33

What must the manufacturer do if a market surveillance authority asks for evidence?

The manufacturer must provide, in paper or electronic form and in a language easily understood by the authority, all information and documentation necessary to demonstrate conformity. It must also cooperate with the authority on measures taken to eliminate cybersecurity risks posed by the product.

Citations
Section 34

What happens under the CRA if the manufacturer is going to cease operations?

Before the cessation takes effect, the manufacturer must inform the relevant market surveillance authorities and, by any means available and to the extent possible, the users of the relevant products placed on the market.

Citations
Section 35

Can the manufacturer use one risk assessment for the CRA and other applicable EU product laws?

Yes.

The Commission FAQ says the manufacturer may carry out a single risk assessment covering different applicable legislation or separate assessments for each instrument. What matters is that the manufacturer remains able to demonstrate compliance with each individual act. For CRA purposes, the assessment still has to cover the entire product with digital elements, including any in-scope remote data processing and supporting functions that form part of the product.

Section 36

If the manufacturer outsources design, development, assembly, or similar work, can it shift its CRA responsibility to the subcontractor?

No.

Under the CRA definition, a manufacturer can still be the manufacturer where it has the product designed, developed, or manufactured and places it on the market under its own name or trademark. The Blue Guide adds that where subcontracting takes place, the manufacturer must retain overall control and cannot discharge its responsibilities to an authorised representative, distributor, user, or subcontractor.

Citations
Section 37

Must the manufacturer have procedures to process vulnerability reports coming from internal and external sources?

Yes.

Article 13(8) expressly requires appropriate policies and procedures, including coordinated vulnerability disclosure policies, to process and remediate potential vulnerabilities reported from internal or external sources. The March 2026 draft guidance repeats that requirement when explaining how manufacturers are expected to organise their handling of potential vulnerabilities.

Section 38

If the manufacturer provides the user information and instructions online, what extra obligation applies?

They must stay accessible, user-friendly, and available online for at least 10 years after the product is placed on the market or for the support period, whichever is longer.

So the CRA does not only require the manufacturer to provide Annex II information once. If those materials are hosted online, the manufacturer has an ongoing availability obligation for the same long-term period that applies to keeping them at the disposal of users and market surveillance authorities.

Citations
Section 39

Must the manufacturer document how it determined the support period?

Yes.

Article 13(8) requires the manufacturer to include in the technical documentation the information taken into account to determine the support period. Annex VII repeats that requirement, so the support-period decision has to be documented, not just decided internally.

Citations
Section 40

Can products already placed on the market continue to be made available after their support period has expired?

Yes.

The Commission FAQ says products already placed on the market can continue to be made available after the support period expires. But if the manufacturer later places additional units of that product on the market, it still has to determine the support period for those newly placed units in accordance with Article 13(8).

Section 41

If a product was designed before the CRA applied, must the manufacturer redesign it or recreate historical design and test files before placing it on the market?

Not necessarily.

The March 2026 draft guidance says a product designed before the CRA applies may still be placed on the market without redesign if the manufacturer carries out a current cybersecurity risk assessment and can show through the technical documentation that the existing design already addresses the relevant risks. Where the manufacturer cannot show how the original design phase took the risk assessment into account, the guidance says it is not required to recreate historical design or test documentation that would not improve the product's cybersecurity. But the manufacturer still has to complete the CRA's current obligations before placement on the market, including the conformity assessment, declaration of conformity, and CE marking steps.

Citations
Primary sources

References and citations

data.europa.eu41 citations
Referenced sections
  • Article 3(13)
  • Article 13(1); Article 13(8)
  • Article 13(2); Article 13(8)
Show 32 more
  • Article 13(2)-(4)
  • Article 13(3)
  • Article 13(3); Article 13(7)
  • Article 13(3)-(4); Article 13(8)
  • Article 13(4); recital 55
  • Article 13(5); recital 34
  • Article 13(5); recital 34; recital 35
  • Article 13(6); Article 13(8)
  • Article 13(8)
  • Article 13(8); recital 60
  • Article 13(8); Annex I Part II
  • Annex I Part II point (2)
  • Article 6; Annex I Part I point (2)(c); Annex I Part II points (7) and (8); recital 56
  • Article 13(9)
  • Article 13(10); recital 40
  • Article 13(11)
  • Article 13(12); Article 28; Article 30; Article 32
  • Article 13(13)
  • Article 13(14)
  • Article 13(15)-(16); Annex II point (1)
  • Article 13(17); Annex II point (2); recital 63
  • Article 13(18); Annex II
  • Article 13(19); Annex II point (7); recital 56
  • Article 13(20)
  • Article 14(1)-(4)
  • Article 14(8)
  • Article 18(2)
  • Article 13(21)
  • Article 13(22)
  • Article 13(23)
  • Article 13(8); Annex VII point (4)
  • Article 13(2); Article 13(12)
ec.europa.eu23 citations
Referenced sections
  • section 4.1.1
  • section 4.1.2
  • section 4.1.8
Show 14 more
  • section 4.1.3
  • sections 4.4.1 and 4.4.3
  • section 4.3.6
  • section 4.5.1
  • section 4.5.2
  • section 4.3.1
  • section 4.3.3
  • section 4.3.2
  • sections 6.6 and 6.8
  • section 6.8
  • sections 5.2 and 5.3
  • section 5.3
  • section 4.3.4
  • section 4.5.3
Related guides

Explore more topics

Applicability Test | EU Cyber Resilience Act, CRA Product Security and CE Marking
Use this CRA applicability test to confirm product scope, exclusions, remote data processing boundaries, operator role, product classification.
Checklist | EU Cyber Resilience Act, CRA Product Security and CE Marking
Use this Cyber Resilience Act checklist to assign owners, deadlines, evidence, and release gates for scope, Annex I controls, support period operations.
Compliance Program | EU Cyber Resilience Act, CRA Product Security and CE Marking
Build a CRA compliance program that covers product scope, governance, engineering controls, support period operations, Article 14 reporting.
Conformity Assessment and CE Marking | EU Cyber Resilience Act, CRA Product Security and CE Marking
Choose the right CRA conformity route, prepare the declaration of conformity, structure the technical file.
CRA Blue Guide Concepts FAQ | Placing on the Market, Making Available, Distance Sales
CRA FAQ on Blue Guide concepts used in Cyber Resilience Act interpretation: placing on the market, making available, putting into service, online sales.
CRA CE Marking FAQ | Meaning, Placement Rules, Software Labeling, Notified Bodies
CRA CE marking FAQ covering what the mark means, when it is mandatory, software and website placement rules, packaging fallback, notified body numbers.
CRA Component Due Diligence FAQ | Third-Party Components, FOSS, SBOM, Vulnerabilities
CRA component due diligence FAQ covering third-party components, FOSS, CE-marked components, SBOM review, risk-based checks, upstream vulnerability reporting.
CRA Conformity Assessment Routes FAQ | Module A, Module B+C, Module H, Critical and Important Products
CRA FAQ on conformity assessment routes covering module A, module B+C, module H, important and critical products, harmonised standards, certification schemes.
CRA Core Functionality FAQ | Important Products, Critical Products, Classification
CRA FAQ on core functionality covering classification of important and critical products, ancillary functions, integrated components.
CRA Cybersecurity Risk Assessment FAQ | Article 13, Threat Modelling, Variants, Constraints
CRA FAQ on cybersecurity risk assessment covering Article 13, threat modelling, intended purpose, foreseeable misuse, external dependencies, documentation.
CRA Declaration of Conformity FAQ | Full vs Simplified, Languages, Updates, Duties
CRA FAQ on the EU declaration of conformity covering full and simplified formats, required contents, languages, updates, single declarations across EU laws.
CRA Economic Operators FAQ | Manufacturers, Importers, Distributors, Authorised Representatives
CRA FAQ on economic operators covering manufacturer, authorised representative, importer, distributor, responsible operator rules, checks, traceability.
CRA Essential Cybersecurity Requirements FAQ | Annex I Part I and Part II
CRA FAQ on the essential cybersecurity requirements covering Annex I Part I and Part II, applicability, evidence, interoperability constraints.
CRA FAQ Hub | Blue Guide Concepts, CE Marking, Component Due Diligence
Browse the CRA FAQ hub for Blue Guide market-access concepts, CE marking, and component due diligence.
CRA Hardware and Software Boundaries FAQ | Product Scope, Combined Products, Source Code
CRA FAQ on hardware and software boundaries covering combined products, standalone software, source code, companion apps, remote data processing.
CRA Harmonised Standards and Common Specifications FAQ | Presumption of Conformity, OJ Publication
CRA FAQ on harmonised standards, common specifications, and certification schemes covering presumption of conformity, Official Journal publication.
CRA Important and Critical Products FAQ | Annex III, Annex IV, Core Functionality
CRA FAQ on important and critical products covering Annex III and Annex IV classification, core functionality, conformity routes, FOSS rule limits.
CRA Integrated Components and Dependencies FAQ | Due Diligence, RDPS, Third-Party Components
CRA FAQ on integrated components and dependencies covering due diligence, third-party components, RDPS, cloud dependencies, upstream fixes, FOSS dependencies.
CRA Interplay With Other EU Laws FAQ | RED, AI Act, GDPR, Data Act, EHDS, Machinery
CRA FAQ on interplay with other EU laws covering exclusions, overlap with RED, AI Act, GDPR, Data Act, EHDS, Machinery, GPSR, NIS2, aviation, marine.
CRA Known Exploitable Vulnerabilities at Launch FAQ | Placement on the Market, CVEs, Late Discoveries
CRA FAQ on known exploitable vulnerabilities at launch covering the launch-time rule, exploitability, known vulnerabilities, CVEs, compensating controls.
CRA Legacy Products FAQ | Pre-2027 Products, Reporting, Grandfathering, Substantial Modification
CRA FAQ on legacy products covering pre-11 December 2027 products, Article 14 reporting, continued sale, substantial modification, spare parts, old designs.
CRA Market Surveillance and Enforcement FAQ | Authorities, Safeguards, Sweeps, Formal Non-Compliance
CRA FAQ on market surveillance and enforcement covering authorities, investigations, safeguard procedures, formal non-compliance, sweeps, joint activities.
CRA Module A FAQ | Internal Control, Self-Assessment, Eligibility, Documentation
CRA FAQ on module A covering internal control, eligible products, class I limits, FOSS exception, technical documentation, testing, CE marking.
CRA Module B+C FAQ | EU-Type Examination, Conformity to Type, Notified Bodies
CRA FAQ on module B+C covering EU-type examination, conformity to type, notified-body role, certificate changes, production control, CE marking.
CRA Module H FAQ | Full Quality Assurance, Notified Body Surveillance, CE Marking
CRA FAQ on module H covering full quality assurance, quality-system approval, notified-body surveillance, scope changes, CE marking, language rules, records.
CRA Notified Bodies FAQ | Notification, Scope, NANDO, Independence, Competence
CRA FAQ on notified bodies covering notification, competence, independence, NANDO scope, accreditation, cross-border choice, subcontracting.
CRA Open-Source Software FAQ | FOSS, Commercial Activity, Stewards, Donations, Paid Editions
CRA FAQ on open-source software covering FOSS qualification, commercial activity, donations, paid support, stewards, contributors, repositories.
CRA Over-the-Air Updates FAQ | OTA, Automatic Updates, Secure Distribution, Offline Paths
CRA FAQ on over-the-air updates covering OTA versus automatic updates, secure distribution, screenless products, gateways, offline update paths.
CRA Penalties and Fines FAQ | Fine Tiers, Turnover Caps, SME Carve-Outs, Stewards
CRA FAQ on penalties and fines covering Article 64 fine tiers, turnover caps, SME carve-outs, steward exemptions, cumulative fines, criminal sanctions.
CRA Product Families FAQ | Variants, Shared Assessments, Family Reuse, Conformity Scope
CRA FAQ on product families covering shared risk assessments, family-wide documentation reuse, cybersecurity-relevant variant differences.
CRA Remote Data Processing Solutions FAQ | RDPS Scope, Cloud Services, SaaS Boundaries, Documentation
CRA FAQ on remote data processing solutions covering Article 3(2) RDPS tests, cloud-service boundaries, websites and portals, third-party SaaS, backend scope.
CRA Repairs and Spare Parts FAQ | Repairs, Refurbishment, Spare-Part Exemption, Compatibility
CRA FAQ on repairs and spare parts covering substantial modification, Article 2(6) identical spare parts, non-identical replacements.
CRA Reporting Obligations FAQ | Article 14 Deadlines, CSIRT Filing, User Notices, Legacy Products
CRA FAQ on reporting obligations covering Article 14 deadlines, actively exploited vulnerabilities, severe incidents, CSIRT routing, user notifications.
CRA Scope FAQ | Products with Digital Elements, Connections, Software, Exclusions
CRA FAQ on scope and products with digital elements covering software, firmware, components, direct and indirect connections, offline products, exclusions.
CRA Secure-by-Default FAQ | Default Configuration, Auto Updates, Tailor-Made Limits
CRA FAQ on secure by default covering Annex I default configuration, automatic security updates, opt-outs, components, inapplicability.
CRA Security Updates vs Functionality Updates FAQ | Separation, Free Updates, Article 13(10)
CRA FAQ on security updates versus functionality updates covering separation where technically feasible, free security updates, automatic updates.
CRA Substantial Modification FAQ | Post-Market Changes, New Manufacturer, Legacy Products
CRA FAQ on substantial modification covering Article 3(30), software updates, repairs, new manufacturer status, conformity reassessment.
CRA Support Period FAQ | Placement on the Market, Unit-Level Timing, Update Availability
CRA FAQ on support periods covering Article 13(8), placement on the market timing, unit-level support periods, standalone software, update availability.
CRA Tailor-Made Products FAQ | Business-User Exception, Paid Updates, Evidence
CRA FAQ on tailor-made products covering the narrow business-user carve-out, secure-by-default and paid-update deviations, required evidence.
CRA Technical Documentation FAQ | Annex VII, Languages, Authority Access, Updates
CRA FAQ on technical documentation covering Annex VII content, timing, languages, versioning, authority access, reused documentation, simplified formats.
CRA Transition Period FAQ | Key Dates, Legacy Products, Pre-CRA Stock, RED Interplay
CRA FAQ on the transition period covering entry into force, phased application dates, legacy products, stock and customs timing, standalone software.
CRA Update Availability and Archives FAQ | Article 13(9), Archives, Historical Versions
CRA FAQ on update availability and software archives covering Article 13(9), Article 13(10), Article 13(11), retention of issued security updates.
CRA User Information and Transparency FAQ | Annex II, Support Disclosure, User Notices
CRA FAQ on user information and transparency covering Annex II instructions, support-period disclosure, end-of-support notices, vulnerability notices.
CRA vs RED Cybersecurity Delegated Act | EU Cyber Resilience Act, CRA Product Security and CE Marking
Compare the Cyber Resilience Act with the RED cybersecurity delegated act so you can decide which products fall under which rule, what dates apply.
CRA vs UK PSTI Act | EU Cyber Resilience Act, CRA Product Security and CE Marking
Compare the EU Cyber Resilience Act with the UK PSTI product security regime so your team can plan dual market compliance without mixing two different rule.
CRA Vulnerability Handling FAQ | Lifecycle Duties, Components, Disclosure, Fix Sharing
CRA FAQ on vulnerability handling covering Annex I Part II duties, component vulnerabilities, upstream reporting and fix sharing.
Deadlines and Compliance Calendar | EU Cyber Resilience Act, CRA Product Security and CE Marking
Track the CRA entry into force date, the notified body date, the reporting start date, and the main application date.
Essential Cybersecurity Requirements | EU Cyber Resilience Act, CRA Product Security and CE Marking
Understand the CRA essential cybersecurity requirements in Annex I.
Penalties and Fines | EU Cyber Resilience Act, CRA Product Security and CE Marking
Understand the CRA administrative fine tiers in Article 64, the conduct that attracts the highest penalties, and the evidence that reduces enforcement exposure.
Products with Digital Elements Scope | EU Cyber Resilience Act, CRA Product Security and CE Marking
Understand what counts as a product with digital elements under the CRA, how remote data processing fits, and where the scope boundary usually causes mistakes.
Reporting Obligations | EU Cyber Resilience Act, CRA Product Security and CE Marking
Prepare for CRA Article 14 reporting, including the twenty four hour early warning, the seventy two hour notification, final reports, CSIRT routing.
Requirements | EU Cyber Resilience Act, CRA Product Security and CE Marking
Review the full CRA requirement set, including manufacturer duties, operator duties, support period rules, user information, corrective action, reporting.
SBOM and Vulnerability Management Template | EU Cyber Resilience Act, CRA Product Security and CE Marking
Use this CRA SBOM and vulnerability management template to structure dependency records, triage, remediation, advisory publication, and support period evidence.
Technical Documentation and Audit File | EU Cyber Resilience Act, CRA Product Security and CE Marking
Build a CRA technical documentation file that covers product definition, risk assessment, support period, Annex I mapping, standards use, test evidence.
Vulnerability Handling and Disclosure | EU Cyber Resilience Act, CRA Product Security and CE Marking
Build a CRA vulnerability handling system that covers SBOM, intake, triage, remediation, coordinated vulnerability disclosure, secure updates.