Agentic compliance for the CRA

The Cyber Resilience Act, from product inventory to CE marking.

Be ready for the CRA reporting duties now and for CE marking in 2027. GetTeddy's agents classify your products, map the essential requirements and run the reporting process, and a compliance engineer helps you prepare for the conformity assessment.

  • Art. 14 reporting process ready
  • Every product classified
  • Hosting in the EU, Germany or US

Reviewed by Sven Moritz, former CISO · October 2026

Backed byAntlerHosting in the EU, Germany or USShaped with our CISO Panel

What the CRA asks for

The CRA is an EU regulation and applies directly to products with digital elements on the EU market, from connected devices to installable software. Most duties fall on manufacturers.

Show the six obligations
Art. 7 and 8, Annexes III and IVScope and product class

Check which products are in scope and whether each is a default, important (class I or II) or critical product. The class decides the conformity route.

In GetTeddyProduct inventory with a class per product
Art. 13, Annex I Part ISecurity by design

Each product is designed, developed and produced on the basis of a cybersecurity risk assessment and meets the essential requirements, such as secure defaults and protection against unauthorised access.

In GetTeddyRequirements mapped per product, with evidence
Annex I Part IIVulnerability handling

An SBOM covering at least top-level dependencies, a coordinated vulnerability disclosure policy and security updates provided free of charge during the support period.

In GetTeddySBOM and disclosure process tracked
Art. 13(8)Support period

Manufacturers set a support period that reflects how long the product is expected to be used, generally at least five years, and handle vulnerabilities effectively during it.

In GetTeddySupport periods recorded per product
Art. 14Reporting

Actively exploited vulnerabilities and severe incidents are reported through ENISA's single reporting platform to the coordinating CSIRT and ENISA: an early warning within 24 hours, a notification within 72 hours, then a final report.

In GetTeddyReporting process and templates, with named owners
Art. 28 and 30, Annex VIIConformity and CE marking

Technical documentation, a conformity assessment, the EU declaration of conformity and the CE marking before a product is placed on the market.

In GetTeddyTechnical documentation assembled from your evidence
10 Dec 2024In forceRegulation (EU) 2024/2847
11 Sep 2026Reporting appliesArt. 14, also for products already on the market
11 Dec 2027Full applicationEssential requirements and CE marking
Per productSupport periodGenerally at least five years

Map once. Comply everywhere.
Run easy.

Your ISMS already covers much of what the CRA expects from your organisation. GetTeddy keeps one control set for ISO 27001, NIS2 and the CRA and shows only what each product adds.

How it works

Products you can place
on the market

GetTeddy's agents classify, map and track per product. Product and security teams decide, and a compliance engineer helps you prepare for the conformity assessment.

01
Gap Audit Agent

Classify every product

GetTeddy drafts the product inventory and proposes a class for each product with the reasoning, so product and legal can confirm it.

Product inventory · Acme Inc.Draft
Acme Gateway · routerImportant, class I
Acme Desktop AgentDefault
Acme AppDefault
Teddy: Routers are listed in Annex III, class I. Without a harmonised standard applied in full, a third-party assessment is needed.
02
Gap Audit Agent

Essential requirements per product

Each product is checked against Annex I. Controls you already run for ISO 27001, such as secure development and incident handling, count where they apply.

Annex I · Acme GatewayGap audit
Part I requirements met11 of 13
SBOM, top-level dependenciesPartial
Coordinated disclosure policyMissing
03
Evidence Agent

SBOM and vulnerabilities from your repositories

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

Acme GatewayFirmware 4.2
gateway-firmware · SBOMCollected
Known exploited vulnerabilities1 open
Support period5 years
Teddy: The TLS library in gateway-firmware has an actively exploited vulnerability. This may be reportable under Art. 14.
04
Policy Agent

A reporting process with owners

The Policy Agent drafts the Art. 14 process with roles, criteria and templates, so everyone knows who decides and who files.

Art. 14 reportingENISA platform
Early warning · 24 hoursTemplate ready
Notification · 72 hoursTemplate ready
Final reportTemplate ready
Teddy: Security decides whether a vulnerability is actively exploited. Legal submits through the ENISA platform.
05
Certification Agent

Technical documentation built from your evidence

Risk assessment, Annex I mapping, SBOM and support period come together as the technical documentation for your conformity assessment.

Technical documentationAnnex VII
Cybersecurity risk assessmentApproved
Annex I mappingLinked
EU declaration of conformityDraft

How long CRA readiness takes

TypicalYears, not months

Fewer than half of manufacturers expect to be fully compliant by December 2027. Awareness is high, readiness stays low.

With GetTeddyWithin weeks

Products classified, Annex I mapped, SBOMs and support periods tracked and an Art. 14 reporting process in place, well before December 2027.

  • Products already on the market: the product rules generally reach them only after a substantial modification. The reporting duties apply to them now.
  • Fines for reporting breaches: up to €15 million or 2.5% of worldwide turnover.
The problem

Where CRA projects
get stuck

Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents. From December 2027, every product placed on the market has to meet the essential requirements.

01
The class of each product

GetTeddy classifies every product and shows how it has to be assessed.

02
Who reports a vulnerability

One named owner and a tested process for reports via the ENISA platform.

03
Documentation per product

Risk assessment, list of software components (SBOM) and update period, tracked for each release.

04
Product teams, a ticking clock and an AI chat. Still no owner.

An exploited vulnerability hits the gateway firmware, product says security owns it, security says legal files reports, and the SBOM is a spreadsheet from last year. ChatGPT can explain Art. 14, but it does not know your products. GetTeddy maps each product to its obligations and supports the reporting process with named owners.

SMSven MoritzCo-founder of GetTeddy, former CISOLast reviewed: October 2026
From the audit room

Where manufacturers get the CRA wrong

  1. “The CRA is a 2027 problem.”

    The reporting duties have applied since September 2026, more than a year before full application. They also continue after a product's support period ends.

  2. The reporting account is set up during the first incident.

    Registration on the platform takes time, and reporting is a manual workflow for now. Register only when it happens, and the first hours go to setup instead of the report.

  3. Marketing sets the support period without asking engineering.

    It decides how long you must handle vulnerabilities and ship updates. Agree on it with the teams who have to deliver, before you publish it.

Why teams start with GetTeddy

The same result, without months of spreadsheets and consultant hours.

Consultants and spreadsheetsGetTeddy
Product classificationLegal review per productSupported by our agents
Annex I requirementsGeneric checklistsMapped to your controls
SBOMsCollected by handTracked per product
ISO 27001 or NIS2Separate projectsBuilt on the same controls
OngoingYearly reviewGap audits every week

GetTeddy at a glance

GetTeddy is a compliance platform by Teddy Technologies GmbH, based in Berlin, built for start-ups and mid-sized companies. The platform runs in the region you choose: EU, Germany or US, in line with GDPR. Start-ups and Antler portfolio companies get special terms.

FAQ

Questions about the CRA

Does the CRA apply to SaaS?

Pure SaaS is generally outside the CRA. Remote data processing that a product needs to perform its functions is in scope as part of that product. GetTeddy checks each product and its cloud components.

What applies before December 2027?

The reporting obligations under Art. 14 have applied since 11 September 2026, also for products placed on the market earlier. The essential requirements and the CE marking apply to products placed on the market from 11 December 2027.

Do we need a notified body?

It depends on the class. Default products can use internal control. Important class I products can too if they apply harmonised standards or certification schemes in full. Class II and critical products need a third-party assessment or a European certification scheme.

Do you help us with notified bodies?

Yes. A compliance engineer helps with product classification, finding a notified body where one is needed and preparing the technical documentation with you.

We have ISO 27001. How much counts?

Your ISMS covers organisational controls such as incident handling, secure development and supplier security. The CRA adds duties per product: risk assessment, SBOM, support period, technical documentation and CE marking.

Where is our data hosted?

In the region you choose: the EU, Germany or the US. Each customer's data is kept separate and encrypted. GetTeddy connects read-only by default and does not train on customer data. Details are on our security page.

By industry CRA requirements for connected products · The CRA for chips and components · NIS2 and the CRA for machinery makers · EU AI Act and CRA for defense tech · Rules by industry

Every product mapped and
every report on time.

See it on your own products in a 30-minute demo.

  • Backed by Antler
  • Hosting in the EU, Germany or US
  • Compliance engineer included