FAQEUCyber Resilience Act

EU Cyber Resilience Act FAQ Interplay With Other EU Laws

Use this CRA FAQ to understand where the CRA overlaps with other EU regimes, where products are excluded, and how declarations, assessments, and certificates interact across frameworks.

Built for legal, compliance, certification, and product teams navigating multi-framework EU obligations.

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

Structured answer sets in this page tree.

Primary sources
3

Cited legal and guidance references.

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

The CRA is a horizontal cybersecurity regime, but many products also fall under other EU laws. This FAQ focuses on when the CRA applies alongside those frameworks, when products are excluded instead, and how declarations, assessments, certificates, and notified-body roles interact across overlapping regimes.

Search this module

Find a question or answer quickly

25 of 25 sections
Section 1

Does the CRA replace other EU laws that may apply to the same product?

No.

The CRA is a horizontal product-cybersecurity regime. It adds mandatory cybersecurity rules for products with digital elements, but it does not generally replace other Union acts that regulate the same product from another angle, such as product safety, machinery, data protection, health-data systems, or AI. Depending on the product, the CRA may apply alongside those other acts, unless the CRA itself excludes the product or a later delegated act limits the CRA for a specific product framework.

Citations
Recommended next step

Use EU Cyber Resilience Act FAQ Interplay With Other EU Laws as a cited research workflow

Research Copilot can turn EU Cyber Resilience Act FAQ Interplay With Other EU Laws into a reusable cited workflow for teams implementing EU Cyber Resilience Act FAQ.

Section 2

Can one product be subject to the CRA and another EU law at the same time?

Yes.

That is a normal CRA scenario. The Commission FAQ gives machinery, radio equipment, EHR systems, and connected products that are also subject to the Data Act as examples of products that may have to comply with more than one Union framework at once.

Citations
Section 3

When is a product excluded from the CRA rather than merely overlapping with another EU law?

The starting point is the CRA's express exclusions and any delegated acts adopted under Article 2(5).

Some products are excluded directly by Article 2, including products to which the medical-device and in vitro-diagnostic frameworks apply, products to which Regulation (EU) 2019/2144 applies, products certified under the civil-aviation framework, and marine equipment in scope of Directive 2014/90/EU. In addition, Delegated Regulation (EU) 2025/1535 excludes products falling within the scope of Regulation (EU) No 168/2013, except L1e category vehicles designed to pedal. More generally, Article 2(5) allows the Commission to limit or exclude the CRA for products covered by other Union rules that address the same risks, but only where that is consistent with the overall framework and delivers the same or a higher level of protection.

Citations
Section 4

How does the CRA relate to NIS2 and the Cybersecurity Act?

The CRA complements them; it does not duplicate them.

Recital 3 says existing Union cybersecurity law, including Regulation (EU) 2019/881 and Directive (EU) 2022/2555, does not directly cover mandatory security requirements for products with digital elements. Recital 24 adds that the CRA is intended to facilitate compliance by digital infrastructure providers with NIS2 supply-chain requirements by making the products they use more secure and better supported. The CRA also operates without prejudice to Union-level NIS2 supply-chain risk assessments.

Citations
Section 5

How does the CRA interact with the eIDAS framework for European Digital Identity Wallets?

Where a wallet product falls within the CRA's scope, both frameworks apply.

Recital 33 says providers of European Digital Identity Wallets should comply with both the CRA's horizontal essential cybersecurity requirements and the specific security requirements in Article 5a of Regulation (EU) No 910/2014. The same recital also says that, where the Commission has specified a presumption of conformity, a European cybersecurity certification scheme under Regulation (EU) 2019/881 may be used to help demonstrate compliance with both frameworks for the covered requirements.

Citations
Section 6

What is the CRA's relationship with the EU Product Liability Directive?

They are complementary, but they do not serve the same function.

The Product Liability Directive deals with compensation for damage caused by defective products. The CRA sets ex ante cybersecurity obligations for products placed on the market. The Commission FAQ explains that CRA duties such as security-update obligations can become relevant when defectiveness and damage are assessed under the Product Liability Directive.

Section 7

How does the CRA interact with the Machinery Regulation?

A product can fall under both.

The CRA covers essential cybersecurity requirements for products with digital elements. The Machinery Regulation covers essential health and safety requirements for machinery and related products, including some cybersecurity-related safety issues. Recital 53 and the Commission FAQ both say manufacturers of products in scope of both regimes need to comply with both sets of requirements.

Section 8

If the CRA and the Machinery Regulation both apply, is compliance with one enough?

No.

The Commission FAQ says compliance with only one regime cannot automatically be treated as full compliance with the other. There may be synergies where the same technical work addresses similar cybersecurity risks, but the manufacturer still has to demonstrate that on the basis of a risk assessment and the applicable standards or technical specifications. The applicable conformity assessment procedures under both frameworks also remain relevant.

Section 9

How does the CRA interact with the General Product Safety Regulation?

They cover different kinds of risks.

The CRA addresses cybersecurity risks for products with digital elements. The GPSR addresses product safety for consumer products. Article 11 of the CRA says the GPSR continues to apply to aspects and risks not covered by the CRA, unless those risks are already governed by another specific Union harmonisation law.

Citations
Section 10

Does a CRA product sometimes still have to comply with the GPSR?

Yes.

If the product also presents safety risks that are not covered by the CRA, and those risks are not already addressed by a more specific Union product regime, the GPSR may still apply to those safety aspects.

Section 11

How does the CRA interact with the Radio Equipment Directive and Delegated Regulation (EU) 2022/30?

The key issue is timing.

The Commission FAQ says that, for the categories of radio equipment covered by Delegated Regulation (EU) 2022/30, the RED cybersecurity requirements apply to products placed on the market from 1 August 2025 until 10 December 2027. For those same products placed on the market on or after 11 December 2027, the CRA applies instead for the relevant cybersecurity requirements. The FAQ also says a repeal of the RED delegated act from 11 December 2027 would not undo RED market-surveillance treatment for products already placed on the market during the RED period.

Section 12

How does the CRA interact with the AI Act for high-risk AI systems?

Article 12 sets a specific coordination rule.

Where a product is both a CRA product and a high-risk AI system, compliance with the CRA can satisfy the AI Act's cybersecurity requirement in Article 15 to the extent covered by the CRA declaration of conformity. As a rule, the AI Act conformity assessment procedure applies for those cybersecurity requirements. But Article 12(3) preserves the CRA's stricter conformity assessment routes for important and critical CRA products where the AI Act would otherwise rely on internal control.

Citations
Section 13

How does the CRA interact with the European Health Data Space Regulation?

A product may need to comply with both.

The Commission FAQ says a product may be both a product with digital elements under the CRA and an EHR system under the EHDS Regulation. In that case, both sets of requirements can apply. The same FAQ also says the CRA cybersecurity risk assessment may form part of the EHDS risk assessment, and that, for the covered EHR-system scenario, the EHDS conformity assessment route applies instead of the CRA route because the EHDS introduced Article 32(5a) into the CRA.

Citations
Section 14

How does the CRA interact with the GDPR?

They are different legal regimes.

The CRA regulates products placed on the market. The GDPR regulates the processing of personal data by controllers and processors. They can support similar security outcomes, but the CRA does not replace the GDPR and the GDPR does not replace the CRA.

Section 15

Does CRA compliance prove GDPR compliance?

No.

The Commission FAQ says CRA compliance has no formal effect on the separate GDPR tools used to demonstrate compliance with data-protection law. The two frameworks may reinforce each other in practice, but they are not interchangeable.

Section 16

How does the CRA interact with the Data Act?

The two regimes address different issues, but one product may fall under both.

The CRA is about the making available of products with digital elements and their cybersecurity. The Data Act is about access to and sharing of product data and related service data. The Commission FAQ says manufacturers should take relevant Data Act data-access obligations into account in the CRA risk assessment where those obligations apply to the same product.

Citations
Section 17

Does the Data Act by itself force a redesign of all legacy CRA products?

No, not as a general rule in the CRA materials.

The Commission FAQ says the Data Act does not create a standalone rule that all already marketed products must be redesigned solely because of the Data Act. It also explains that CRA cybersecurity requirements apply fully from 11 December 2027, while products already placed on the market before that date are generally brought into those requirements only if they are substantially modified after that date. The same FAQ adds that CRA reporting obligations apply more broadly.

Citations
Section 18

Are medical devices, IVDs, vehicles, certified aviation products, and marine equipment still covered by the CRA?

Not in the same way, and sometimes not at all.

Article 2 excludes products to which the medical-device and in vitro-diagnostic frameworks apply, products to which Regulation (EU) 2019/2144 applies, products certified under the civil-aviation framework, and marine equipment within Directive 2014/90/EU. Separately, Delegated Regulation (EU) 2025/1535 excludes products falling within the scope of Regulation (EU) No 168/2013, except L1e category vehicles designed to pedal. The Commission FAQ adds an important aviation nuance: products that fall within the aviation framework but are not certified under Regulation (EU) 2018/1139 may still be covered by the CRA, and separately marketed components intended for certified aviation products may also remain in scope if those components are not themselves certified under that framework.

Citations
Section 19

Are dual-use products excluded from the CRA?

No, not merely because they can also be used for defence or national-security purposes.

The CRA excludes products developed or modified exclusively for national security or defence purposes and products specifically designed to process classified information. The Commission FAQ adds that dual-use products with both civilian and defence applications remain subject to the CRA unless they are modified exclusively for national security or defence purposes.

Citations
Section 20

If more than one EU product law applies, can the manufacturer issue one EU declaration of conformity?

Yes.

Article 28(3) requires a single EU declaration of conformity where more than one Union act requiring such a declaration applies to the product. The Commission FAQ confirms the same logic for overlapping CRA and EHDS scenarios.

Section 21

Can one technical-documentation set or one risk-assessment workflow support the CRA and more than one other EU law?

Often yes, but the manufacturer still has to prove compliance with each law separately.

For CRA Article 12 products that are also subject to other Union acts with technical-documentation requirements, Article 31(3) requires a single technical-documentation set. Article 13(4) also allows the CRA cybersecurity risk assessment to form part of the risk assessment required by those other Union acts. The Commission FAQ adds that manufacturers may use one combined risk assessment or separate risk assessments, but they must be able to demonstrate compliance with each applicable regime.

Citations
Section 22

Does the mere existence of another Union product law with some cybersecurity rules automatically displace the CRA?

No.

Outside the CRA's express exclusions and specific delegated acts adopted under Article 2(5), the existence of sector-specific cybersecurity requirements does not by itself switch the CRA off. Recital 28 makes clear that limitation or exclusion for other Union rules requires an additional Commission act and depends on the overall framework addressing the same risks at the same or a higher level of protection.

Citations
Section 23

If a component is intended for use in aviation, marine, or vehicle products that are excluded or partially excluded, is that component automatically outside the CRA?

No.

The Commission FAQ says components intended for certified aviation products may still be covered where the component itself is not certified under Regulation (EU) 2018/1139, and the same logic applies to components intended for marine equipment where the component itself is not within Directive 2014/90/EU. The draft guidance adds a more specific rule for vehicle frameworks: components designed and constructed exclusively for integration into vehicles covered by Regulation (EU) 2019/2144 or Regulation (EU) No 168/2013 can stay outside the CRA, but generic components that can also be used elsewhere remain in scope. It also says distribution facts matter: if a non-exclusive component is offered through channels open beyond the automotive supply chain, such as general retail or public online sales, it falls within the CRA regardless of intended-use statements.

Section 24

Can a manufacturer rely on existing EU type-examination certificates or approval decisions issued under other Union product laws once the CRA starts applying?

Partly, for a limited time and only for the risks those certificates actually cover.

Article 69(1) says EU type-examination certificates and approval decisions issued regarding cybersecurity requirements under other Union harmonisation legislation remain valid until 11 June 2028, unless they expire earlier or that other legislation provides otherwise. The draft guidance explains that this does not amount to full CRA compliance. It only means the manufacturer does not need to reassess or re-demonstrate compliance for the already covered cybersecurity risks during that period. The manufacturer must still perform the CRA cybersecurity risk assessment and address any additional risks not covered by the earlier certificate, including where the prior certificate was issued under the RED cybersecurity regime or the Machinery Regulation.

Section 25

In high-risk AI cases, can an AI Act notified body also assess the CRA cybersecurity requirements?

Yes, in the Article 12 coordination setup.

Article 12(2) says that, for products with digital elements that are also high-risk AI systems, the relevant AI Act conformity assessment procedure applies for the covered cybersecurity requirements. For that assessment, notified bodies that are competent under the AI Act may also assess conformity with the CRA Annex I requirements, provided their compliance with the CRA notified-body requirements in Article 39 has been assessed in the AI Act notification context. Article 12(3) then preserves the CRA's own stricter routes for important and critical CRA products where the AI Act would otherwise use internal control.

Citations
Primary sources

References and citations

data.europa.eu23 citations
Referenced sections
  • recitals 3, 6, 28, 31, 32, 33 and 53; Article 2(2)-(5); Article 11; Article 12
  • recitals 25, 27 and 28; Article 2(2)-(5)
  • recitals 3, 24, 48 and 52
Show 17 more
  • recital 33
  • recital 31
  • recital 53
  • recital 50; Article 11
  • recital 30
  • recital 51; Article 12(1)-(3)
  • Article 13(4); Article 28(3); Article 31(3)
  • recital 32
  • Article 6; Article 13(2)-(4)
  • recitals 25 and 27; Article 2(2)-(4)
  • recital 26; Article 2(7)-(8)
  • Article 28(3)
  • Article 13(4); Article 31(3)
  • recital 28 and Article 2(5)
  • Article 2(2)-(4)
  • Article 69(1)
  • Article 12(2)-(3)
ec.europa.eu20 citations
Referenced sections
  • sections 2.4.1, 2.5.1, 2.7.1, 2.8.1 and 2.9.1
  • sections 2.4.1, 2.6.1, 2.7.1 and 2.9.1
  • section 1.9
Show 15 more
  • section 2.3.1
  • sections 2.4.1 and 2.4.2
  • sections 2.4.2 and 2.4.3
  • sections 2.5.1 and 2.5.2
  • section 2.5.2
  • section 2.6.1
  • sections 2.7.1, 2.7.2, 2.7.3 and 2.7.4
  • section 2.8.1
  • sections 2.9.1 and 2.9.2
  • sections 2.9.2 and 2.9.3
  • sections 1.9, 2.1.1 and 2.2.1
  • section 1.8
  • sections 2.7.4 and 6.8
  • sections 2.7.2 and 4.1.1
  • sections 2.1.1 and 2.2.1
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 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 Manufacturer Obligations FAQ | Article 13 Duties, Support Period, Reporting, Documentation
CRA FAQ on manufacturer obligations covering Article 13 duties, risk assessment, support periods, vulnerability handling, reporting, documentation.
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.