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.
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.
GetTeddy drafts the product inventory and proposes a class for each product with the reasoning, so product and legal can confirm it.
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.
The Evidence Agent collects SBOMs from connected repositories and watches for vulnerabilities in the components you ship.
The Policy Agent drafts the Art. 14 process with roles, criteria and templates, so everyone knows who decides and who files.
Risk assessment, Annex I mapping, SBOM and support period come together as the technical documentation for your conformity assessment.
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.
GetTeddy classifies every product and shows how it has to be assessed.
One named owner and a tested process for reports via the ENISA platform.
Risk assessment, list of software components (SBOM) and update period, tracked for each release.
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.
See it on your own products in a 30-minute demo.