FAQEUCyber Resilience Act

EU Cyber Resilience Act FAQ Module B+C

Understand the CRA's two-step Module B+C route: what the notified body examines, what evidence the manufacturer submits, what production-control duties remain, and when certificate changes require approval.

Built for certification, engineering, legal, and compliance teams using or reviewing the CRA type-examination route.

Author
Sorena AI
Published
Mar 10, 2026
Updated
Mar 10, 2026
Questions
32

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

Under the Cyber Resilience Act, Module B+C combines notified-body EU-type examination with manufacturer-led conformity to type based on internal production control. This FAQ focuses on the evidence package for Module B, the notified body's role, the Module C declaration and CE-marking consequences, record retention, post-certificate changes, and the limited audit duty for vulnerability-handling processes.

Search this module

Find a question or answer quickly

32 of 32 questions
Question 1

What is Module B+C under the Cyber Resilience Act?

Module B+C is a two-step conformity-assessment route.

Module B is EU-type examination by a notified body. Module C is conformity to the approved type based on the manufacturer's internal production control. Together, they cover both the examination of the product type and the manufacturer's obligation to keep actual production in line with that approved type.

Citations
Cyber Resilience Act

Identifies Module B+C as EU-type examination followed by conformity to EU-type based on internal production control.

Question 2

When is Module B+C mandatory under the Cyber Resilience Act?

Module B+C is one of the mandatory third-party routes for:

- important products of class I where Article 32(2) requires third-party assessment for the relevant requirements

- important products of class II, such as hypervisors and container runtime systems, firewalls, intrusion detection and prevention systems, and tamper-resistant microprocessors or microcontrollers

- critical products listed in Annex IV, unless the applicable certification route under Article 8(1) applies

Citations
Cyber Resilience Act

Sets when class I, class II, and critical products must use Module B+C, Module H, or an applicable cybersecurity certification route.

Question 3

Can a manufacturer also choose Module B+C voluntarily under the Cyber Resilience Act?

Yes.

Article 32(1) allows manufacturers to use Module B+C for products generally covered by paragraph 1, even where module A would also be available.

Citations
Cyber Resilience Act

Allows manufacturers to choose Module B+C among the general Article 32(1) conformity assessment procedures.

Question 4

Does Module B+C always involve a notified body under the Cyber Resilience Act?

Yes.

Module B is the notified-body part of the route. Module C then follows with the manufacturer's own internal production control against the approved type.

Citations
Cyber Resilience Act

Module B is performed by a notified body; Module C is the manufacturer's internal production-control step.

Question 5

How many notified bodies can be involved in one CRA module B application?

Only one.

The manufacturer must lodge the EU-type examination application with a single notified body of its choice and must declare that the same application has not been lodged with any other notified body.

Citations
Cyber Resilience Act

Requires the Module B application to go to one notified body and include a declaration that no duplicate application was lodged elsewhere.

Question 6

What does the manufacturer have to submit for CRA module B?

The application must include:

- the manufacturer details and, where relevant, the authorised representative's details

- a declaration that the same application has not been lodged with another notified body

- technical documentation that allows conformity to be assessed, including an adequate analysis and assessment of the risks

- supporting evidence for the adequacy of the technical design, development solutions, and vulnerability-handling processes

Where necessary, the supporting evidence must include test results from the manufacturer's own laboratory or another testing laboratory acting on its behalf and under its responsibility.

Citations
Cyber Resilience Act

Lists the manufacturer details, non-duplicate-application declaration, technical documentation, risk analysis, supporting evidence, and test evidence required for Module B.

Question 7

Does CRA module B cover only the product's technical design, or also vulnerability handling?

It covers both.

EU-type examination is not limited to the product's technical design and development. The notified body also examines the vulnerability-handling processes put in place by the manufacturer against Part II of Annex I.

Citations
Cyber Resilience Act

Shows that EU-type examination covers both the product's technical design and the manufacturer's vulnerability-handling processes.

Question 8

Does the CRA notified body assess only documents, or also specimens and tests?

It assesses both.

Annex VIII Part II requires examination of the technical documentation and supporting evidence, plus examination of specimens of one or more critical parts of the product. The notified body must also carry out appropriate examinations and tests, or have them carried out.

Citations
Cyber Resilience Act

Requires the notified body to examine documentation, supporting evidence, specimens of critical parts, and appropriate examinations or tests.

Question 9

What exactly does the notified body check during CRA module B?

The notified body checks:

- whether the technical documentation and supporting evidence are adequate

- whether the examined specimens match the documentation

- which elements were designed and developed using relevant harmonised standards or technical specifications and which were not

- whether the manufacturer's chosen solutions satisfy the applicable essential cybersecurity requirements

Citations
Cyber Resilience Act

Sets the notified body's checks on documentation, specimens, harmonised-standard use, and alternative solutions.

Question 10

Can CRA module B tests be carried out at the manufacturer's site or elsewhere?

Yes.

Annex VIII Part II point 4.5 says the notified body and the manufacturer agree on the location where the examinations and tests will be carried out.

Citations
Cyber Resilience Act

Allows the manufacturer and notified body to agree where Module B examinations and tests are performed.

Question 11

What does the manufacturer receive if CRA module B is successful?

The manufacturer receives an EU-type examination certificate.

The certificate identifies the approved type and the vulnerability-handling processes, and it records the conclusions of the examination and any validity conditions.

Citations
Cyber Resilience Act

Defines the EU-type examination certificate contents when the type and vulnerability-handling processes meet Annex I.

Question 12

What happens under CRA Module B+C if the notified body concludes that the type or vulnerability-handling processes do not comply?

It must refuse to issue the EU-type examination certificate and give detailed reasons for the refusal. Annex VIII frames that refusal around both the type and the vulnerability-handling processes, so a process failure can block the certificate even if the product design evidence is otherwise strong.

Citations
Cyber Resilience Act

Requires refusal and detailed reasons when the type or vulnerability-handling processes do not satisfy the applicable requirements.

Question 13

Under CRA Module B+C, does the EU-type examination certificate approve only the type or also vulnerability-handling processes?

It covers both.

Annex VIII Part II point 6 ties the certificate to both the approved type and the examined vulnerability-handling processes. That is why later modifications to either can matter for certificate validity.

Citations
Cyber Resilience Act

Ties the certificate to both the approved type and the examined vulnerability-handling processes.

Question 14

What does CRA module C add after module B?

Module C is the production-control step.

After obtaining the EU-type examination certificate, the manufacturer must ensure and declare that the products actually manufactured remain in conformity with the approved type and continue to satisfy the essential cybersecurity requirements.

Citations
Cyber Resilience Act

Defines Module C as conformity to type based on internal production control after the Module B certificate.

Question 15

Under CRA Module B+C, does module C mean the notified body supervises the production phase directly?

Not in the way module H does.

Under module C, the manufacturer itself must take the necessary measures so that production and production monitoring ensure conformity with the approved type and the applicable essential cybersecurity requirements. Module C is therefore not a full-quality-assurance route supervised like Module H.

Citations
Question 16

What must the manufacturer do under CRA module C before placing products on the market?

The manufacturer must:

- ensure that production conforms to the approved type

- affix the CE marking to each individual compliant product

- draw up a written declaration of conformity for the product model

Citations
Cyber Resilience Act

Requires production conformity, CE marking on each compliant product, and a written declaration of conformity for the product model.

Question 17

Under CRA module C, is the declaration of conformity for each individual product or for the product model?

It is for the product model.

Annex VIII Part III point 3.2 requires a written declaration of conformity for a product model. That differs from module A wording, which refers to each product with digital elements.

Citations
Cyber Resilience Act

States that Module C uses a declaration of conformity for a product model and identifies that model.

Question 18

Does the CE marking still have to go on each individual product under CRA Module B+C?

Yes.

Even though the declaration under module C is for the product model, the CE marking must still be affixed to each individual product with digital elements that conforms to the approved type.

Citations
Cyber Resilience Act

Requires CE marking on each individual product that conforms to the approved type and satisfies the CRA.

Question 19

What happens under CRA Module B+C if the approved type or vulnerability-handling processes change after certification?

The manufacturer must inform the notified body that holds the technical documentation relating to the certificate of any modifications that may affect conformity or the conditions for validity of the certificate.

Those modifications require additional approval in the form of an addition to the original EU-type examination certificate.

Citations
Cyber Resilience Act

Requires manufacturer notification and certificate additions for modifications that may affect conformity or certificate-validity conditions.

Question 20

Is CRA Module B+C reassessment required only for "substantial modifications"?

Not only for that label.

Annex VIII Part II point 7 is framed more broadly: the trigger is any modification to the approved type or the vulnerability-handling processes that may affect conformity with Annex I or the conditions for validity of the certificate.

Citations
Cyber Resilience Act

Uses a conformity-or-certificate-validity trigger for post-certificate modifications, not only a label such as substantial modification.

Question 21

Does CRA Module B+C include surveillance after the certificate is issued?

Yes, but it is limited.

The notified body must carry out periodic audits to ensure that the vulnerability-handling processes in Part II of Annex I are implemented adequately. This is not the same as the broader quality-system surveillance under module H.

Citations
Cyber Resilience Act

Requires periodic notified-body audits of the manufacturer's vulnerability-handling processes.

Question 22

Under CRA Module B+C, who gets informed about issued, refused, withdrawn, suspended, or restricted EU-type examination certificates?

The notified body must inform its notifying authorities and the other notified bodies about those certificate outcomes.

The Commission and Member States can also obtain copies of the certificates and, on request, copies of the technical documentation and examination results.

Citations
Cyber Resilience Act

Sets the notified body's information duties for certificate issuance, withdrawal, refusal, suspension, restriction, and requests by authorities.

Question 23

How long must the manufacturer keep CRA Module B+C records?

The manufacturer must keep:

- the EU-type examination certificate, its annexes and additions, together with the technical documentation

- the declaration of conformity for the product model

Those records must be kept at the disposal of national authorities for 10 years after the product is placed on the market or for the support period, whichever is longer.

Citations
Cyber Resilience Act

Requires retention of the certificate package and product-model declaration for 10 years after market placement or the support period, whichever is longer.

Question 24

Can an authorised representative handle some CRA Module B+C steps?

Yes, but only where the mandate expressly covers them.

Under Annex VIII Part II point 11, the authorised representative may lodge the module B application and fulfil the obligations relating to modifications and record retention. Under Annex VIII Part III point 4, the authorised representative may fulfil the declaration obligations in module C.

Citations
Cyber Resilience Act

Allows an authorised representative to handle specified Module B+C obligations only where the mandate covers them.

Question 25

Can important free-and-open-source software still use CRA Module B+C?

Yes.

Article 32(5) allows manufacturers of Annex III products qualifying as free and open-source software to use one of the procedures listed in Article 32(1), provided the technical documentation is made public at the time of placing on the market. That means they may use module A, but they may also choose Module B+C.

Citations
Cyber Resilience Act

Allows Annex III free-and-open-source software manufacturers to use Article 32(1) procedures, including Module B+C, if the technical documentation is public at market placement.

Question 26

Under the Cyber Resilience Act, do older EU-type certificates issued under other Union product laws automatically disappear on 11 December 2027?

No.

Article 69(1) provides a transition rule: EU-type examination certificates and approval decisions issued regarding cybersecurity requirements for products with digital elements under other Union harmonisation legislation remain valid until 11 June 2028, unless they expire earlier or that other legislation specifies otherwise.

Citations
Cyber Resilience Act

Keeps certain pre-CRA cybersecurity EU-type certificates and approval decisions valid during the CRA transition period, subject to expiry and other-law limits.

Question 27

What usually makes a CRA Module B+C file workable in practice?

A workable file is one that lets the notified body trace the compliance claim, the supporting design choice, the evidence, and the tested specimen without gaps.

Grounded in Annex VIII Part II and Annex VII, that usually means the application clearly identifies the applicable requirements, includes the risk analysis and assessment, explains any reliance on or departure from harmonised standards or technical specifications, and contains the supporting evidence and test results needed for the notified body's examination.

Citations
Cyber Resilience Act

Connects the Module B application file to the technical documentation contents, risk analysis, standards mapping, supporting evidence, and tests.

Question 28

Does CRA Module B+C require the notified body's identification number next to the CE marking?

No.

Under Article 30(4), the CE marking is followed by the notified body's identification number only where that body is involved in the conformity assessment procedure based on module H. Under Module B+C, the manufacturer still affixes the CE marking to each individual compliant product under module C, but the CRA does not require a notified-body number next to that marking.

Citations
Question 29

In what language can CRA Module B+C technical documentation and correspondence be submitted to the notified body?

They must be in an official language of the Member State where the notified body is established, or in another language acceptable to that body.

That rule applies to the technical documentation and correspondence relating to any CRA conformity assessment procedure, including Module B+C.

Citations
Question 30

Under CRA Module B+C, does every change after certification have to go back to the notified body?

No.

The legal trigger in Annex VIII Part II point 7 is any modification to the approved type or the vulnerability-handling processes that may affect conformity with Annex I or the conditions for validity of the certificate. Those changes require additional approval from the notified body in the form of an addition to the original certificate.

The practical split is evidence-based: changes that may affect Annex I conformity or certificate-validity conditions need notified-body approval; changes that do not affect those points should still be recorded internally so the manufacturer can explain why reassessment was not triggered.

Citations
Cyber Resilience Act

Defines which approved-type and vulnerability-handling-process changes require an addition to the original certificate.

Question 31

After a substantial modification, does the new CRA Module B+C assessment have to start from scratch for unchanged parts?

Not necessarily.

Not necessarily. For the CRA certificate, the notified-body trigger remains whether the modification to the approved type or vulnerability-handling processes may affect Annex I conformity or certificate-validity conditions.

The Blue Guide gives the product-law evidence principle for modified products: when a modified product is treated as new, technical documentation has to be updated only as far as the modification affects applicable requirements, and tests or documentation need not be repeated for aspects not impacted by the modification. In practice, a Module B+C reassessment file should identify the changed parts, explain why any unchanged parts are still covered by existing evidence, and submit the affected type or process changes for approval where Annex VIII point 7 is triggered.

Citations
Cyber Resilience Act

Requires additional notified-body approval when changes to the approved type or vulnerability-handling processes may affect conformity or certificate validity.

Question 32

Do the periodic audits under CRA Module B+C cover the whole production system in the same way as module H?

No.

Under Annex VIII Part II point 8, the periodic audit duty is specifically to ensure that the vulnerability-handling processes in Part II of Annex I are implemented adequately. Module C separately leaves production conformity control to the manufacturer. So this is narrower than a module H full-quality-assurance assessment.

Citations
Cyber Resilience Act

Limits Module B periodic audits to vulnerability-handling processes while Module C leaves production conformity control with the manufacturer.

Primary sources

References and citations

data.europa.eu
Referenced sections
  • Limits Module B periodic audits to vulnerability-handling processes while Module C leaves production conformity control with the manufacturer.
"vulnerability handling processes"
ec.europa.eu
Referenced sections
  • Explains the CRA transition treatment of existing cybersecurity certificates issued under other Union product laws.
"remain valid until 11 June 2028"
Related guides

Explore more topics

CRA Applicability Test for Products With Digital Elements
Check whether the EU Cyber Resilience Act applies to a hardware, software, firmware, open-source, or connected product before conformity planning.
CRA Article 14 Reporting Obligations for Vulnerabilities and Incidents
Article 14 guide to CRA reports for actively exploited vulnerabilities and severe product-security incidents, including deadlines, CSIRT routing, users, and evidence.
CRA Blue Guide Concepts FAQ | Placing on the Market, Making Available, Distance Sales
CRA FAQ explaining Blue Guide market-access concepts for products with digital elements: placing on the market, making available, imports, CE marking, operator roles, online sales, stock, and testing exceptions.
CRA CE Marking FAQ | Conformity Assessment, EU Declaration, Evidence
Practical CRA CE marking answers for products with digital elements: conformity assessment, EU declaration, technical documentation, standards, software placement, and launch evidence.
CRA Component Due Diligence FAQ | Third-Party Software, FOSS, SBOMs
Cyber Resilience Act FAQ on manufacturer due diligence for integrated components, third-party software, FOSS dependencies, SBOMs, vulnerability handling, and evidence records.
CRA Conformity Assessment and CE Marking
How to choose a Cyber Resilience Act conformity route, prepare technical documentation, issue the EU declaration of conformity, and affix CE marking.
CRA Conformity Assessment Routes FAQ | Module A, Module B+C, Module H, Important and Critical Products
Cyber Resilience Act FAQ on when manufacturers can use module A, when module B+C or module H is required, and how important and critical products affect the route.
CRA Cybersecurity Risk Assessment FAQ | Article 13, Annex I, Updates
CRA FAQ on Article 13 cybersecurity risk assessments, Annex I applicability, intended purpose, foreseeable use, technical documentation, and update evidence.
CRA deadlines and compliance calendar | EU Cyber Resilience Act
Track the Cyber Resilience Act entry into force, staged application dates, Article 14 reporting deadlines, transitional rules, and review dates.
CRA Declaration of Conformity FAQ | Annex V, Simplified Declaration, CE Marking
FAQ on the Cyber Resilience Act EU Declaration of Conformity: Annex V contents, simplified Annex VI wording, CE marking link, technical documentation, retention, updates, and operator duties.
CRA Economic Operators FAQ | Manufacturers, Importers, Distributors, Authorised Representatives
CRA FAQ on economic-operator roles: manufacturers, importers, distributors, authorised representatives, substantial modification, traceability, and evidence controls.
CRA Essential Cybersecurity Requirements FAQ | Annex I Part I and Part II
CRA FAQ on Annex I product cybersecurity requirements, vulnerability handling, secure-by-default design, risk assessment, documentation, lifecycle duties, and user information.
CRA Essential Cybersecurity Requirements in Annex I
A grounded guide to the Cyber Resilience Act Annex I requirements for product security, vulnerability handling, secure-by-design controls, documentation, and evidence.
CRA Hardware and Software Boundaries FAQ | Product Scope, Components, RDPS
FAQ on Cyber Resilience Act hardware and software boundaries: combined products, standalone software, source code, components, remote data processing, SaaS and market-placement changes.
CRA Harmonised Standards FAQ | Presumption of Conformity, Common Specifications
Cyber Resilience Act FAQ on how harmonised standards, common specifications, certification schemes, and OJ publication affect CRA conformity evidence.
CRA Important and Critical Products FAQ | Annex III, Annex IV, Conformity Assessment
FAQ on CRA important and critical products, Annex III and Annex IV classification, core functionality, and conformity assessment consequences.
CRA Integrated Components and Dependencies FAQ | Third-Party Software and SBOM Evidence
Cyber Resilience Act FAQ on integrated components, third-party software, remote data processing, SBOM-style evidence, upstream fixes, FOSS dependencies, and manufacturer responsibility.
CRA Interplay With EU Product Laws FAQ | RED, Machinery, Data Act
Grounded CRA FAQ on overlap with the Radio Equipment Directive, Machinery Regulation, GPSR, Data Act, exclusions, declarations, documentation, and existing certificates.
CRA Known Exploitable Vulnerabilities at Launch FAQ
FAQ for Cyber Resilience Act launch decisions: known exploitable vulnerabilities, CVEs, component flaws, secure-by-default settings, release gates, Article 14 reporting, and evidence.
CRA Legacy Products FAQ | Pre-11 December 2027 Products
Cyber Resilience Act FAQ on products placed on the market before 11 December 2027, Article 14 reporting, substantial modification, distributor stock, spare parts, and records.
CRA Manufacturer Obligations FAQ | Article 13, Annex I, CE Marking
FAQ for Cyber Resilience Act manufacturers covering Article 13 duties, risk assessment, Annex I, vulnerability handling, support periods, documentation, conformity assessment, reporting, CE marking, and evidence controls.
CRA Market Surveillance and Enforcement FAQ | Authorities, Corrective Action, Safeguards
Cyber Resilience Act FAQ on market-surveillance authorities, investigations, corrective action, withdrawal, recall, safeguards, sweeps, documentation access, and penalties.
CRA Module H FAQ | Full Quality Assurance, Notified Body Surveillance, CE Marking
CRA Module H FAQ explaining the full-quality-assurance route, notified-body assessment, quality-system scope, technical documentation, CE marking, declarations, and records.
CRA Notified Bodies FAQ | Scope, Modules B+C and H, Certificates
Practical CRA FAQ on when notified bodies are needed, how CRA bodies are designated, what their notified scope means, and how Module B+C and Module H assessments work.
CRA Open-Source Software FAQ | FOSS Scope, Stewards, Manufacturers
Cyber Resilience Act FAQ for free and open-source software: commercial activity, steward duties, manufacturer due diligence, vulnerability handling, public documentation, and user obligations.
CRA Over-the-Air Updates FAQ
Cyber Resilience Act FAQ on OTA updates, automatic security updates, secure update distribution, support-period evidence, and offline update paths.
CRA penalties and fines FAQ | Article 64 fine caps
FAQ on EU Cyber Resilience Act Article 64 penalties: maximum fine tiers, turnover caps, national enforcement, economic operators, reporting duties, and open-source steward carve-outs.
CRA Penalties and Fines: Article 64 Caps and Enforcement Context
Article 64 of the EU Cyber Resilience Act sets administrative fine ceilings for Annex I, manufacturer, reporting, economic-operator, notified-body, and information-request breaches.
CRA Product Families FAQ | Variants, Shared Assessments, Family Reuse, Conformity Scope
CRA FAQ on product families, variant grouping, shared technical documentation, conformity evidence, and when cybersecurity-relevant differences need separate assessment.
CRA Products with Digital Elements Scope | EU Cyber Resilience Act
Apply the EU Cyber Resilience Act scope test for software, hardware, remote data processing, components, open-source software, exclusions, and economic-operator roles.
CRA Products With Digital Elements Scope FAQ
EU Cyber Resilience Act FAQ on products with digital elements, software, firmware, remote data processing, components, exclusions, market placement, and CRA operator boundaries.
CRA Remote Data Processing Solutions FAQ | Product Scope, Cloud and Backend Boundaries
FAQ on how the EU Cyber Resilience Act treats remote data processing solutions, manufacturer-controlled backends, third-party cloud services, SaaS, risk assessment, documentation, and user information.
CRA Reporting Obligations FAQ | Article 14, CSIRTs, ENISA, User Notices
Cyber Resilience Act FAQ on Article 14 reporting for actively exploited vulnerabilities and severe incidents, including timing, CSIRT routing, ENISA access, user notices, and evidence.
CRA Requirements | Annex I, Manufacturer Duties and CE Evidence
Map Cyber Resilience Act requirements from Annex I to manufacturer duties, vulnerability handling, user information, technical documentation, declaration of conformity, and CE marking evidence.
CRA SBOM and Vulnerability Management Template
Build a CRA-ready SBOM and vulnerability handling record with component inventory, triage, remediation, disclosure, reporting, update, and technical documentation fields.
CRA Secure-by-Default FAQ | Default Configuration and Annex I Controls
Cyber Resilience Act FAQ on secure-by-default configuration, automatic security updates, attack surface reduction, authentication, data minimisation, user information, and tailor-made products.
CRA Security Updates vs Functionality Updates FAQ
Cyber Resilience Act FAQ on classifying security updates, functionality updates, support-period duties, automatic updates, user notices, and substantial-modification review.
CRA Substantial Modification FAQ | Updates, Repairs, Manufacturer Duties
Cyber Resilience Act FAQ on when software updates, repairs, spare parts, and post-market changes become substantial modifications and trigger CRA manufacturer, evidence, and conformity duties.
CRA Support Period FAQ | Expected Product Lifetime, Security Updates, User Information
Practical CRA FAQ on how manufacturers determine support periods, disclose support end dates, keep security updates available, and document support-period evidence.
CRA Tailor-Made Products FAQ | Bespoke Products, Market Placement, Evidence
FAQ on when a bespoke product may be treated as tailor-made under the EU Cyber Resilience Act, what the carve-out changes, and what manufacturers still need to document.
CRA Technical Documentation FAQ | Annex VII Evidence and Technical File
CRA FAQ explaining Annex VII technical documentation, risk assessment evidence, conformity assessment files, vulnerability handling records, product families, RDPS, language, and authority access.
CRA Transition Period FAQ | Entry Into Force, Application Dates, Reporting, Legacy Products
CRA FAQ on the transition period covering entry into force, 2026 reporting, 2027 application, legacy products, stock, customs timing, and software versions.
CRA Update Availability and Software Archives FAQ
FAQ on CRA security-update availability, support-period notices, optional public software archives, historical versions, and Article 13(10) software-version limits.
CRA User Information and Transparency FAQ | Annex II Instructions
Practical CRA FAQ on Annex II user instructions, support-period disclosure, vulnerability contacts, update notices, importer and distributor information.
CRA vs RED Cybersecurity Delegated Act
Compare the EU Cyber Resilience Act with the RED cybersecurity delegated act for connected and radio equipment, including scope, timing, evidence, and transition treatment.
CRA vs UK PSTI Act | Cyber Resilience Act Comparison
Compare grounded EU Cyber Resilience Act duties with UK PSTI planning points, with UK legal details clearly marked for separate source review.
CRA Vulnerability Handling and Disclosure | Article 14 Reporting and Security Updates
How EU Cyber Resilience Act manufacturers should run vulnerability intake, remediation, coordinated disclosure, Article 14 reporting, secure updates, and evidence records.
CRA Vulnerability Handling FAQ | Support Periods, Components, Reporting
Practical CRA FAQ on vulnerability handling: SBOMs, remediation, coordinated disclosure, component issues, security updates, support periods, Article 14 reporting, and user notices.
Cyber Resilience Act Module A FAQ | Internal Production Control
FAQ on when CRA Module A internal production control is available, when it is blocked, and what documentation, testing, standards, and evidence it still requires.
EU CRA Compliance Program for Manufacturers and Economic Operators
Build a Cyber Resilience Act compliance program around product scope, Annex I security requirements, conformity assessment, technical documentation, vulnerability reporting, and market surveillance.
EU Cyber Resilience Act Checklist for Product Security and CE Marking
A CRA checklist for products with digital elements: scope, Annex I security controls, vulnerability handling, Article 14 reporting, technical documentation, conformity assessment, CE marking, and support-period evidence.
EU Cyber Resilience Act Core Functionality FAQ | CRA Product Classification
CRA FAQ on core functionality, product boundaries, remote data processing, integrated components, ancillary functions, and software changes that affect product classification.
EU Cyber Resilience Act FAQ
Direct CRA FAQ answers on scope, economic-operator roles, essential requirements, vulnerability reporting, conformity assessment, CE marking, support periods, and market surveillance.
EU Cyber Resilience Act Repairs and Spare Parts FAQ
CRA FAQ for repairs, spare parts, legacy products, security updates, substantial modification, and responsibility after product changes.
EU Cyber Resilience Act Technical Documentation and Audit File
Build an audit-ready CRA technical file around Article 31 and Annex VII: product scope, risk assessment, vulnerability handling, conformity evidence, testing, and retention.