CRA Compliance

Can a RED or EUCC body certify your product under the CRA?

By CVD Portal
••Last updated 2026-11-16••10 min read

No. A Radio Equipment Directive or EUCC accreditation confers no automatic status under the Cyber Resilience Act. Every conformity assessment body needs separate notification in NANDO under Regulation (EU) 2024/2847. On 16 November 2026, ENISA published CRA-Module B and H: CABs accreditation for notification (version 2.6), mapping the exact competence gaps across RED and EUCC bodies.

Manufacturers of Annex III Class II products, Annex IV products using a third-party route, and Annex III Class I products without harmonised standards applied in full must engage a CRA notified body before 11 December 2027. Knowing where existing laboratories already hold the required technical competence, and where they fall short, prevents wasted assessment bookings during 2027.

Key takeaways

  • ENISA's 83-page publication of 16 November 2026 is a non-binding technical reference for notifying authorities and national accreditation bodies. An existing accreditation or notification confers no automatic eligibility for CRA notification.
  • Under EA-2/17 M:2026, CRA Module B (Annex VIII Part II) rests on EN ISO/IEC 17065:2012 with linked inspection and testing competence, while CRA Module H (Annex VIII Part IV) rests on EN ISO/IEC 17021-1:2015.
  • RED Module H bodies face the smallest competence gap to CRA Module H, EUCC certification bodies partnered with an ITSEF face a moderate gap to CRA Module B, and RED Module B laboratories relying on EN 18031 face the largest gap.
  • Unlike point-in-time RED type examination or EUCC evaluation, CRA Module B requires periodic post-certificate audits of the manufacturer's Annex I Part II vulnerability handling processes under Annex VIII Part II point 8.
  • Operational 24-hour reporting under Article 14 sits outside notified body conformity assessment, and Annex I Part I(1) does not require the manufacturer to operate a secure development lifecycle.

What is the ENISA notified body gap analysis?

CRA-Module B and H: CABs accreditation for notification, subtitled Gap analysis for Module B and Module H vs RED and EUCC, is an 83-page ENISA report at version 2.6, published on 16 November 2026 under CC BY 4.0 (ISBN 978-92-9204-820-4, doi 10.2824/7808161, catalogue number TP-01-26-027-EN-N).

Chapter IV of Regulation (EU) 2024/2847, covering the notification of conformity assessment bodies in Articles 35 to 51, entered into application on 11 June 2026 under Article 71(2). That window lets Member State notifying authorities and national accreditation bodies assess and designate conformity assessment bodies ahead of full CRA applicability on 11 December 2027. On that same date, Commission Delegated Regulation (EU) 2026/339 repeals Commission Delegated Regulation (EU) 2022/30 under the Radio Equipment Directive, moving connected radio products placed on the market from 11 December 2027 onto the CRA. See does RED DA work count toward CRA compliance for how product evidence carries across that handoff.

Section 1.1 of the ENISA report states its legal status clearly. The document is a non-binding technical reference for notifying authorities and national accreditation bodies. It does not determine accreditation or notification eligibility. Each conformity assessment body must demonstrate compliance with the CRA requirements for the scope it requests, and the notifying authority keeps the notification decision.

Which accreditation standards apply to CRA Module B and Module H?

On 25 June 2026, European co-operation for Accreditation published EA-2/17 M:2026 (EA Document on Accreditation for Notification Purposes) with a one-year implementation period for national accreditation bodies, following the May 2026 EA Accreditation for Notification Project Report. Section 4 and Section 5.2 of the ENISA report set out the resulting accreditation baselines for the two CRA third-party procedures.

CRA conformity procedureBase accreditation standardLinked EA-2/17 M:2026 competence codesHow competence links inside one accreditation
Module B, EU-type examination (Annex VIII Part II)EN ISO/IEC 17065:2012 (product certification)cd + pk + tLinked through Clause 6.2 of EN ISO/IEC 17065:2012 to EN ISO/IEC 17020:2012 clauses 6.1.2, 6.1.3 and 6.1.6 to 6.1.10 for product-related professional judgement, including the assessment of Annex I Part II vulnerability handling processes (referencing ISO/IEC 30111:2019 and ISO/IEC 29147:2018), and to EN ISO/IEC 17025:2017 clauses 6 and 7 (excluding 7.9) for testing
Module H, full quality assurance (Annex VIII Part IV)EN ISO/IEC 17021-1:2015 (management system certification)pk + qapk refers to EN ISO/IEC 17020:2012 clauses 6.1.2, 6.1.3 and 6.1.6 to 6.1.10 for product-related professional judgement, and qa covers the competence to assess and approve the manufacturer's quality system. Separate EN ISO/IEC 17020 accreditation is not implied

Two accreditation rules in the ENISA report affect assessments during 2026 and 2027:

  1. One accreditation per module covers linked tasks. A Module B notified body holds EN ISO/IEC 17065:2012 accreditation and demonstrates the applicable clauses of EN ISO/IEC 17020 and EN ISO/IEC 17025 within that assessment, rather than holding three separate accreditations (ENISA section 4 and section 5.2). The report notes that the international transition from ISO/IEC 17020:2012 to ISO/IEC 17020:2026 takes three years, and EA-2/17 S1 M:2026 cites the 2012 clauses.
  2. Draft standards cannot serve as normative accreditation criteria. Under EA TMB Resolution 2026 (25) 01, draft horizontal standards in the prEN 40000 series and draft vertical standards in the ETSI EN 304 6xx series cannot be cited directly in an accreditation scope as normative standards. Until a standard is formally published and cited in the Official Journal of the European Union, a conformity assessment body can include a draft at Level 5 only as its own developed and validated internal assessment method (ENISA section 1.2).

Under Module H, Sections 1.2 and 8.2 also clarify the manufacturer side. A manufacturer's quality system is assessed against CRA Annex VIII Part IV. Existing certificates under ISO 9001:2015 or ISO/IEC 27001:2022 can provide a foundation when extended for CRA product design and vulnerability handling controls (for example using national technical guidelines such as BSI TR-03183-H), while holding ISO 9001 or ISO/IEC 27001 remains optional and insufficient on its own.

How do the four transition paths compare?

Section 2 of the ENISA report compares four starting positions for existing conformity assessment bodies and testing laboratories. The gap size depends on both the accreditation standard already held and the depth of technical testing already performed.

Transition pathStarting standardTarget CRA standardOverall gapMain structural and technical adjustments
RED Module H body to CRA Module HEN ISO/IEC 17021-1:2015EN ISO/IEC 17021-1:2015SmallestStructural requirements match. Body adds assessment of development controls and Annex I Part II vulnerability handling inside the quality system (Annex VIII Part IV points 3.2, 3.3 and 4), and extends product competence beyond radio equipment
EUCC certification body with ITSEF to CRA Module BEN ISO/IEC 17065:2012 plus EN ISO/IEC 17025:2017EN ISO/IEC 17065:2012 (cd + pk + t)ModerateOne of the most direct routes to CRA Module B. Must shift from a scoped Target of Evaluation to the whole product placed on the market (including qualifying Article 3(2) remote data processing), add periodic Annex I Part II audits, keep non-testing reviews under EN ISO/IEC 17065 control per EA TMB Resolution 2022 (09) 01, and close targeted Annex I testing gaps
EUCC ITSEF alone to CRA Module BEN ISO/IEC 17025:2017 onlyEN ISO/IEC 17065:2012 (cd + pk + t)Not rated. An ITSEF cannot qualify on EN ISO/IEC 17025 aloneTesting laboratories lack EN ISO/IEC 17065 certification decision and impartiality structures. Must obtain EN ISO/IEC 17065:2012 accreditation, or serve as a testing subcontractor to a CRA notified body under Article 41
RED Module B body or EN 18031 lab to CRA Module BEN ISO/IEC 17065:2012 (often backed by EN 18031 lab checks)EN ISO/IEC 17065:2012 (cd + pk + t)LargestOrganisational EN ISO/IEC 17065 evidence can be reused, whereas point-in-time EN 18031 mechanism checks leave high gaps in code and binary analysis, isolation testing, development evidence review, and lifecycle vulnerability handling audits

Section 7.7 draws an essential legal distinction on the EUCC side. Under CRA Article 27(8), Article 27(9), and Article 8(1), a product holding a qualifying European cybersecurity certificate under Implementing Regulation (EU) 2024/482 (EUCC) can gain a presumption of conformity or satisfy a third-party route directly through that product certificate. That product-level certification route is legally distinct from an EUCC conformity assessment body obtaining notification in NANDO as a CRA Module B notified body. For the manufacturer view of those routes, see CRA conformity assessment routes.

Where do RED and EUCC testing labs fall short on CRA Annex I?

Tables 1 and 2 of the ENISA report rate the competence gaps that accreditors will examine when a RED body or an EUCC ITSEF applies for CRA Module B work. The report uses four levels. None means existing competence covers the requirement. Low means limited familiarisation. Medium means a materially new domain that needs training and guidance. High means skills, tools or expertise outside the current evaluation approach.

Table 1 covers bodies accredited for RED Module B.

CompetenceCRA basis given by ENISAGapENISA rationale
Code and binary analysisAnnex I Part I(2)(a), Part II(1)HighRED Module B has no equivalent activity. A body qualified only for EN 18031 must establish source code and binary analysis capability
Manufacturer development and vulnerability handling process assessmentArticle 13(2), Annex I Part I(1) and Part II, Annex VIII Part II points 1, 4.1 and 8HighRED Module B has no equivalent to the assessment and periodic audit of the CRA vulnerability handling framework
Isolation and containment testingAnnex I Part I(2)(k)HighEN 18031 does not prescribe process isolation, sandboxing or container and virtual machine separation testing as distinct activities
Data minimisation assessmentAnnex I Part I(2)(g)Medium to HighMedium for bodies qualified under EN 18031-2, High for bodies whose RED scope does not include it
Physical and hardware security testingAnnex I Part I(2)(d), (j) and (k), where applicableMedium to HighDebug interface security, tamper resistance and specialised hardware attack techniques fall outside EN 18031. The CRA does not require this testing for every product
Support-period documentation reviewArticle 13(8) and (19), Annex II, Annex VIIMediumRED Module B has no comparable support-period regime. No new technical skills or tools are needed
Vulnerability analysis methodologyAnnex I Part I(2)(a) and, where relevant, (j) and (k)MediumEN 18031 gives a limited base through its GEC-1 checks for publicly known exploitable vulnerabilities

Table 2 covers EUCC ITSEFs. Several rows refer to extended Common Criteria components that ENISA proposed in a January 2025 study. They are analytical mappings, not current EUCC components.

CompetenceGapENISA rationale
Data minimisation review (proposed ADV_PDM.1)MediumCC and CEM do not generally assess whether data processing is necessary or proportionate
SBOM verification (proposed ALC_SBM.1)MediumA new evidence type. Evaluators must assess machine-readable SBOMs in CycloneDX 1.4 or higher or SPDX 2.3 or higher
Periodic security review assessment (proposed ALC_PSR.1)MediumExtends one-off evaluation to a continuing security testing programme
Decommissioning assessment (proposed AGD_DEC.1)MediumNeeds product-specific knowledge of data destruction methods
Risk-based review of design and risk assessment documentationMediumAn ITSEF does not normally assess the manufacturer's complete cybersecurity risk assessment at product level
DoS resilience testingLow to MediumDepends on the evaluated requirements and the product risks
Harmonised standard conformity verificationLow to MediumLow for standards-based testing, Medium where alternative solutions need broader judgement
Secure default configuration review, secure update mechanism testing, permanent data removal and secure transfer, flaw-separation reviewLowLimited CRA-specific familiarisation is enough

ITSEF accreditation alone does not cover every activity above. Under EA TMB Resolution 2022 (09) 01, activities that are not testing may need to be performed or controlled within the EN ISO/IEC 17065 certification function.

The Key Findings add a capacity warning. EUCC is not restricted to a closed list of product categories, but the CRA covers a much broader range. ENISA says that extending coverage to the 20+ product families and the emerging vertical standards may need significant investment in testing methods, tools and personnel. Section 5.4 gives examples from the draft vertical standards. In draft ETSI EN 304 626 for operating systems, static source code analysis (MI-SSCA) is mandatory for 15 of 17 security profiles, and MI-FZ95 requires instrumented execution that reaches at least 95% code coverage. Table 16 adds that code-level exploitation mitigations such as ASLR, stack canaries and DEP are not covered by EUCC at the substantial assurance level.

What sits outside a CRA notified body assessment?

Section 2 and Table 16 of the ENISA report set four boundaries on what a CRA notified body checks during Module B or Module H conformity assessment.

Requirement or conceptLegal referenceInside Module B or H technical assessment?What the ENISA report and Commission guidance clarify
Periodic vulnerability handling audits under Module BAnnex VIII Part II point 8, Annex I Part IIYes, ongoing post-certificate dutyUnlike RED Module B or EUCC, CRA Module B requires periodic audits of the manufacturer's Annex I Part II vulnerability handling processes after the type certificate is issued
Certified or formal secure development lifecycle (SDLC)Annex I Part I(1), Commission guidance C(2026) 5252 section 7.2NoAnnex I Part I(1) does not require the manufacturer to operate an SDLC, and the notified body does not assess whether one exists. Development evidence may still support the product conformity assessment
24-hour incident and vulnerability reportingArticle 14Outside notified body conformity assessmentArticle 14 reporting is an operational manufacturer obligation, not an Annex I essential requirement. Compliance falls to the competent authorities, CSIRTs and market surveillance
Free-of-charge security updates and commercial support lengthAnnex I Part II(8), Article 13(8) and (19), Annex II, Annex VIIDocumentation consistency check onlyProviding security updates free of charge (subject to the B2B tailor-made exception) is a non-technical legal duty, and notified bodies verify support-period consistency across Annex II and Annex VII rather than approving commercial pricing or duration

What should manufacturers check before engaging a candidate body?

Section 2 of the ENISA report gives a direct warning to manufacturers with multi-product portfolios: an incumbent Radio Equipment Directive notified body will only be able to assess CRA products after closing the gaps for each specific product category and module. Five checks keep third-party timelines on track ahead of 11 December 2027.

  1. Confirm active CRA notification in NANDO. Check the CRA notified bodies directory and verify in the European Commission's NANDO database that the body is notified specifically under Regulation (EU) 2024/2847 for your Annex III or Annex IV category and for Module B or Module H.
  2. Match the module to your release cadence. Module B plus Module C anchors on an approved product type and requires reporting substantial modifications back to the notified body, alongside periodic Annex I Part II audits. Module H approves and surveils the quality system under EN ISO/IEC 17021-1:2015, which suits frequent software releases across multiple variants.
  3. Ask how testing and subcontracting are structured. If a candidate body subcontracts penetration testing or binary analysis to an EN ISO/IEC 17025 ITSEF under Article 41, confirm that the subcontractor holds competence for your vertical and that non-testing evaluations remain controlled by the EN ISO/IEC 17065 body.
  4. Prepare Annex VII and Annex I Part II evidence before intake. Assemble your product risk assessment, Annex I Part I applicability justification, CycloneDX or SPDX SBOM, coordinated vulnerability disclosure policy, and signed update documentation (see what is the ENISA Technical Advisory on Secure Update Mechanisms) before requesting a quote.
  5. Run Article 14 reporting readiness on a separate track. Because notified bodies do not assess Article 14 operational reporting and Article 14 has applied since 11 September 2026, test your 24-hour early warning and 72-hour notification workflow independently of your certificate schedule.

How does CVD Portal fit alongside a notified body?

CVD Portal is CRA compliance and vulnerability disclosure software. Only a designated notified body or an accredited European cybersecurity certification body issues third-party certificates under Article 32.

Where a product requires Module B plus Module C or Module H, CVD Portal builds and maintains the evidence package that the notified body inspects: product classification, cybersecurity risk assessment, Annex I Part I and Part II control mapping, CycloneDX and SPDX SBOM tracking, Annex VII technical documentation, and the coordinated vulnerability disclosure portal and triage records audited during periodic Annex VIII Part II point 8 reviews. In parallel, CVD Portal manages the 24-hour, 72-hour, and 14-day or one-month Article 14 reporting workflow for the ENISA Single Reporting Platform, covering the operational reporting obligation that sits outside notified body conformity assessment.

Primary sources

Frequently asked questions

Does a Radio Equipment Directive notified body automatically qualify under the CRA?

No. CRA notification requires a separate assessment and designation in NANDO under Chapter IV of Regulation (EU) 2024/2847. In its 16 November 2026 publication CRA-Module B and H: CABs accreditation for notification (version 2.6), ENISA finds that RED Module H bodies face the smallest gap to CRA Module H, whereas RED Module B laboratories relying on EN 18031 face high competence gaps in code analysis, isolation testing, and periodic vulnerability handling audits.

Can an EUCC testing laboratory (ITSEF) issue a CRA Module B certificate on its own?

No. An ITSEF accredited only under EN ISO/IEC 17025:2017 holds testing accreditation rather than product certification accreditation. Under EA-2/17 M:2026, a CRA Module B notified body requires EN ISO/IEC 17065:2012 accreditation with linked inspection and testing competence. An ITSEF can work as a testing subcontractor to a CRA notified body or obtain EN ISO/IEC 17065:2012 accreditation itself.

Do CRA notified bodies audit Article 14 incident reporting or require a formal SDLC?

No. Operational 24-hour vulnerability and incident reporting under Article 14 sits outside Module B and Module H conformity assessment and is enforced by market surveillance authorities and CSIRTs. In addition, the ENISA report cites Commission guidance C(2026) 5252 (section 7.2, paragraphs 164 to 166) for the point that Annex I Part I(1) does not require the manufacturer to operate a secure development lifecycle.

CRA deadline briefing

A short email on the Cyber Resilience Act obligations and the run-up to full application on 11 December 2027.

We use your email only to send the briefing. Unsubscribe any time with one click.