For electronics and hardware makers

CRA evidence for every component,
before customers ask

Our AI agents propose a class for every component and keep the SBOM current.

Example data

At a glance

The CRA for components at a glance

Chips and modules you sell separately also fall under the CRA. Since September 2026, you report actively exploited vulnerabilities, and from December 2027 every product you place on the market needs CE marking.

GetTeddy proposes a class with a reason per product family, and your team confirms.

  • Classes Default, important class I or II, or critical
  • Conformity route Internal control, notified body or certification scheme, by class
  • Reporting Early warning on actively exploited vulnerabilities within 24 hours
  • Support Usually at least five years per product family
  • TISAX® Only if a customer from the automotive industry asks for it
  • Hosting In the EU, Germany or the US, as you choose
Obligations check

Which class applies to your component?

Do you place the component on the EU market yourself, and can it have a data connection?

The class follows the core functionality of the component. For finished connected devices, use the helper on the Connected products page. This helper is not legal advice.

Are your components ready for the CRA?

Tick what you can already prove. Your result stays in your browser.

Components and classes
Development
Reporting and customers
Company
Your status0%

The foundation is still missing.

Book a demo
What electronics makers deal with

A component
is a product too

01
Components sold separately fall under the CRA

This covers hardware and software components with a data connection.

02
Security chips land in higher classes

Microprocessors, microcontrollers, ASICs and FPGAs with security-related functions are class I. Tamper-resistant versions are class II. Smartcards and secure elements are critical.

03
Your customers must check you

Whoever builds in your component must exercise due diligence. Questions about SBOM, support period and vulnerabilities come to you.

04
Your plant is a NIS2 sector

Electronics and electrical equipment are NIS2 sectors.

How it works

From the MCU family
to the answer your customer needs

Our AI agents propose a class for every component and keep the evidence current with every release. They prepare answers to customer questions from that evidence.

01
Gap Audit Agent

Propose a class for every component, with a reason

GetTeddy builds the component inventory and proposes a class per family, with the reason from Annex III or IV. Your team confirms.

02
Gap Audit Agent

Check the essential requirements per family

GetTeddy checks each family against Annex I. Controls from your ISO 27001 program count where they apply.

03
Evidence Agent

SBOM for firmware and SDK

The Evidence Agent collects SBOMs from connected repositories and watches vulnerabilities in the components you ship.

04
Policy Agent

One reporting process for the CRA and the BSI Act

The Policy Agent drafts the reporting process and templates with roles and deputies.

05
Questionnaire Agent

Evidence for your customers

The Questionnaire Agent prepares answers to customer requests from approved evidence. Open questions go to the right person.

Deadlines

CRA reporting has applied since 11 September 2026

6 Dec 2025NIS2 applies in GermanyThe new BSI Act is in force.
11 Jun 2026Notified bodiesThe rules for conformity assessment bodies apply.
11 Sep 2026CRA reportingReport actively exploited vulnerabilities and severe incidents.
11 Dec 2027CRA applies in fullEvery product placed on the market from then on needs conformity and CE marking.
Per familySupport periodUsually at least five years.

CRA reporting since September 2026

Ask GetTeddy

A customer asks
if your module changes their class

Every team asks the same questions in its own words. GetTeddy answers from inventory, SBOM and evidence.

1
Ask GetTeddy
Which class is our new MCU family? Which support period did we commit to? Every answer links to its source.
2
Our team backs you up
A compliance engineer helps you prepare for the conformity assessment.
Teddy
Your company · Example data
A customer asks if our module changes the class of their product.
No. Building in our class I module does not by itself make their product class I. Legal approved this answer.
Send answer to Sales
Ask our team
CE
Your compliance engineer
 helps you prepare for the conformity assessment.
Before and after

Your components get their own class and their own evidence

TypicalThe CRA as the device makers' problem
With GetTeddyYour components with their own class and evidence
TypicalWith GetTeddy
ClassificationDebated again for each requestProposal with a reason, confirmed by your team
SBOMsBy hand when a customer asksPer release from your repositories
Customer requestsEach one handled aloneFrom one approved record
Plant and productNIS2 and the CRA kept apartOne control set
FAQ

CRA questions from electronics and component makers

Does the Cyber Resilience Act apply to chips sold to device makers?

Yes. Components you sell separately also fall under the CRA. That covers chips, modules and firmware with a data connection. The device maker who builds them in must check them with due diligence and will ask you for evidence. GetTeddy prepares that evidence from your controls.

Does a built-in chip make the end device an important CRA product?

No, not by being built in. The class follows what the product itself does, its core functionality. A microcontroller with security-related functions is class I on its own. Built into a device, it does not by itself move that device into class I or II.

Do component makers need a notified body under the CRA?

It depends on the class. Class I needs one only if you apply no harmonized standard, no common specifications and no European certification scheme at assurance level substantial or higher in full. Class II needs a notified body or such a scheme. For critical products a European scheme can become mandatory.

CRA conformity routes

Does NIS2 apply to electronics manufacturers?

Often it does. Electronics and electrical equipment are NIS2 sectors. With 50 or more staff, or more than €10 million in both turnover and balance sheet, you are an important entity under § 28 BSIG. You register with the BSI within three months.

Do electronics makers need TISAX®?

Only if a customer from the automotive industry asks for it. TISAX® assesses against the VDA ISA, the automotive industry's catalog. The label is valid for three years. GetTeddy builds TISAX® on the same control set as the CRA and NIS2. Your ISO 27001 controls cover much of it, so you start from what you already run.

TISAX® for automotive suppliers

Read next Connected products and the CRA · CRA · NIS2 for your plant · One control set for several frameworks · Aerospace and defense suppliers

One product family
is enough for the demo

In 30 minutes we show you how it works on one of your product families.

  • Backed by Antler
  • Compliance engineer included

TISAX® is a registered trademark of the ENX Association. GetTeddy is not affiliated with ENX.