Cyber Resilience Act · Regulation (EU) 2024/2847

CRA compliance software, built into your pipeline.

VamiAppSec is a CRA compliance platform for manufacturers of products with digital elements. It generates an SBOM for every release, watches shipped components for actively exploited vulnerabilities and prepares the Art. 14 reports to ENISA and the CSIRT — while SAST, SCA, secrets scanning and AI-powered DAST produce the per-release evidence for Annex I.

11 Sep 2026
Reporting obligation for actively exploited vulnerabilities applies
11 Dec 2027
Full application of the CRA
24 h · 72 h · 14 d
Early warning, notification and final report
What the CRA requires

Four obligations, one evidence trail.

The CRA applies to manufacturers, importers and distributors of hardware and software products with digital elements on the EU market. For manufacturers, four blocks of obligations shape day-to-day engineering:

Annex I · Part I

Secure by design

Products are placed on the market without known exploitable vulnerabilities, with a secure default configuration, a limited attack surface and protection of the confidentiality, integrity and availability of data.

Annex I · Part II

Vulnerability handling

Identify and document components — including an SBOM in a machine-readable format that covers at least the top-level dependencies — fix vulnerabilities without delay, test regularly, run a coordinated vulnerability disclosure policy and ship security updates.

Article 14

Reporting obligations

Actively exploited vulnerabilities and severe incidents are reported via ENISA's Single Reporting Platform: early warning within 24 hours, notification within 72 hours, final report within 14 days after a fix is available (one month for incidents).

Article 13 · Annex VII

Technical documentation

Manufacturers document how the essential requirements are met, keep that documentation for at least ten years and provide security updates throughout the support period — as a rule at least five years.

How VamiAppSec covers it

From requirement to evidence.

Every pipeline run turns a CRA requirement into a machine-generated record that your PSIRT, auditor or notified body can check.

CRA requirementWhat VamiAppSec doesEvidence per release
SBOM Annex I, Part II (1)Syft builds CycloneDX or SPDX SBOMs in the pipeline, including transitive dependencies.Versioned, signed SBOM stored with each release
No known exploitable vulnerabilities Annex I, Part I (2)(a)SAST (Semgrep with LLM review), SCA (Grype, Trivy), secrets (Gitleaks), IaC and containers (Checkov, Trivy) and VamiDAST — the release gate blocks on critical findings.Scan results and the quality-gate decision
Fix without delay, test regularly Annex I, Part II (2) and (3)Every finding lands in OWASP DefectDojo with SLAs, deduplication and risk acceptance — synced to Jira, Azure DevOps Boards or ServiceNow.Audit trail per finding, from detection to fix
Actively exploited vulnerabilities Art. 14Released SBOMs are matched against NVD, OSV and GitHub advisories plus CISA KEV and ENISA EUVD, prioritised with EPSS — with a reachability check and a VEX draft.Pre-filled 24-hour, 72-hour and 14-day report drafts
Information on fixed vulnerabilities Annex I, Part II (4)VEX statements and vulnerability disclosure reports generated from the tracked findings.VEX / VDR export per release
Technical documentation Annex VIISBOMs, scan results, gate decisions and vulnerability-handling records are bundled for every release.Evidence bundle as input for your conformity assessment
Art. 14 in practice

The 24-hour clock starts when you know.

The reporting obligation also covers products that are already on the market. VamiAppSec watches every shipped release around the clock, so awareness doesn't depend on someone reading the news.

01

Detect

A component in a released SBOM shows up in CISA KEV or ENISA's EU Vulnerability Database — VamiAppSec flags the affected products and releases.

02

Assess

The LLM checks whether the vulnerable code path is reachable in your product and drafts the VEX status: affected, not affected, fixed or under investigation.

03

Draft

VamiAppSec pre-fills early warning, vulnerability notification and final report with product, version, component and mitigation details.

04

Decide and submit

Your PSIRT reviews, decides and submits via ENISA's Single Reporting Platform; the finding stays tracked in DefectDojo until the fix ships.

Art. 14 deadlines for an actively exploited vulnerability
24 hEarly warning
72 hVulnerability notification
14 dFinal report, once a fix or mitigation is available

Reports go to the CSIRT designated as coordinator and to ENISA at the same time. Deadlines run from the moment the manufacturer becomes aware.

Where it runs

Your compliance data stays in Germany.

SaaS on T Cloud Public

Exclusively in German data centers operated by Deutsche Telekom — EU jurisdiction, GDPR by design.

On-prem on your Kubernetes

Scanners, VamiDAST, DefectDojo and the LLM on your own cluster — air-gapped if needed.

Your choice of LLM

Qwen3.8, operated by VamiSec in Sankt Augustin or on your own GPUs — or Anthropic or OpenAI. Your data is never used for AI training.

VamiAppSec doesn't certify your product and doesn't take decisions away from your PSIRT. Conformity is assessed by you or, depending on the product category, by a notified body — VamiAppSec supplies the evidence they ask for.

FAQ

CRA compliance, answered.

Who has to comply with the Cyber Resilience Act?

Manufacturers, importers and distributors of hardware and software products with digital elements that are made available on the EU market. Products covered by their own sector rules — for example medical devices under MDR/IVDR or type-approved vehicles — are excluded from the CRA.

When do the CRA obligations apply?

The reporting obligations under Art. 14 apply from 11 September 2026, also for products already on the market. All other obligations, including the essential requirements of Annex I and the conformity assessment, apply from 11 December 2027.

What does the CRA require for the SBOM?

Annex I, Part II requires an SBOM in a commonly used, machine-readable format that covers at least the top-level dependencies. It does not have to be published, but it is part of the technical documentation and must be provided to market surveillance authorities on request. VamiAppSec generates CycloneDX or SPDX SBOMs, including transitive dependencies, for every release.

What counts as an actively exploited vulnerability?

A vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Art. 14 then requires an early warning within 24 hours, a notification within 72 hours and a final report no later than 14 days after a fix or mitigation is available.

Does VamiAppSec make my product CRA-compliant?

No tool can do that on its own. VamiAppSec automates the evidence-heavy parts — SBOM, vulnerability monitoring, testing, tracking and report drafts — and documents them per release. Conformity is assessed by you or, depending on the product category, by a notified body.

How does VamiAppSec fit into our existing pipeline?

Native integrations for GitLab, GitHub and Azure DevOps — pipeline templates, PR/MR checks and quality gates — plus Bitbucket and Jenkins. Results are available as SARIF, CycloneDX / SPDX and via a REST API; findings sync to Jira, Azure DevOps Boards or ServiceNow.

See your CRA evidence in 30 minutes.

We connect a sample repository, run the pipeline from SAST to VamiDAST and show you the SBOM export, the exploited-vulnerability watch and an Art. 14 report draft.

No credit card · SaaS from Germany or on-prem on Kubernetes · SaaS live in 24h