Cyber Resilience Act · Regulation (EU) 2024/2847
The CRA asks for evidence.
Kodator supplies it.
Anyone who sells software, devices or machinery with digital elements in the EU will have to prove that they are secure. Kodator turns your security scans into the evidence the CRA asks for, clause by clause.
- 11 Sep 2026Already applies
Reporting of actively exploited vulnerabilities: early warning within 24 hours, notification within 72 hours (Art. 14).
- 11 Dec 2027Deadline
From then on all other obligations apply: product requirements, technical documentation, declaration of conformity and CE mark.
- 10 yearsRetention
The technical documentation and the declaration of conformity must stay available for at least this long for every product (Art. 13(13)).
Scope · Art. 2, 3
Who the CRA applies to
The CRA is an EU law and regulates a product, not the organisation. It applies to products with digital elements that are placed on the EU market and can connect, directly or indirectly, to a device or network.
Software vendors
Applications, libraries and components that are sold as a product.
Device and machine builders
Connected devices, controllers and machines with their firmware and the software that belongs to them.
Importers and distributors
Whoever brings such products into the EU or distributes them there. The CRA sets out duties of their own for them.
Step by step
The road to conformity, and who contributes what
The order follows a product from classification to record keeping. Each step says whether Kodator supplies the evidence, helps with it, or whether the task is entirely yours.
How to read the steps
Kodator 2 / 12Kodator produces the evidence from scans and remediation.
Kodator helps 5 / 12Kodator supplies part of the evidence. The task stays with you.
You 5 / 12Outside of what a scanner can give evidence for.
Classify the product
The first step is to classify the product under the CRA.
- Kodator supplies
- No contribution.
- Stays with you
- The classification of the product.
Carry out the cybersecurity risk assessment
The manufacturer assesses the risks of the product, documents the assessment and keeps it up to date during the support period. It states which requirements of Annex I apply.
- Kodator supplies
- No contribution.
- Stays with you
- Carry out, document and maintain the risk assessment. A scanner cannot replace it.
Design and develop securely
Secure defaults, access protection, confidentiality, integrity, a small attack surface and further properties have to be built into the product.
- Kodator supplies
- Findings from source code, secrets, infrastructure-as-code and runtime scans give indications for points (b), (d), (e), (f), (j) and (k). The report shows this as "partly indicated".
- Stays with you
- Architecture and implementation. A scanner cannot give evidence for points (c), (g), (h), (i), (l) and (m), among them updates, data minimisation, availability and logging.
Keep a software bill of materials (SBOM)
Components and vulnerabilities of the product have to be identified and documented, with a machine-readable SBOM covering at least the top-level dependencies.
- Kodator supplies
- A CycloneDX SBOM per asset, frozen for every release. SBOMs from suppliers (CycloneDX 1.2 to 1.7, SPDX 2.2/2.3) can be imported; bought software, firmware and hardware can be added by hand.
- Stays with you
- Declare what cannot be scanned. Kodator lists components without a machine-readable package identifier (purl) as "declared, not monitored".
Ship without known exploitable vulnerabilities
Products must not be placed on the market with known exploitable vulnerabilities.
- Kodator supplies
- Known vulnerabilities in the scanned scope at the time of the release, with CVSS, exploit probability and a flag for actively exploited ones, together with a statement of what was not examined.
- Stays with you
- Judge whether a vulnerability is exploitable in your product, and decide on the release.
Remediate vulnerabilities without delay
Vulnerabilities have to be remediated without delay in relation to the risk, including through security updates.
- Kodator supplies
- Remediation deadlines per severity, times to fix, overdue findings and risk acceptances with justification and expiry date, recorded in the audit log.
- Stays with you
- Fix the vulnerabilities, set your own deadlines and provide security updates.
Test and review regularly
The security of the product has to be tested and reviewed effectively and regularly.
- Kodator supplies
- Scheduled scans across six scan types; every run is recorded, including missed and incomplete runs.
- Stays with you
- Manual reviews such as code reviews by people, and penetration tests.
Set up processes for reports and updates
Required are a coordinated vulnerability disclosure policy, a contact address, secure distribution of security updates free of charge, and information about fixed vulnerabilities.
- Kodator supplies
- As input: the list of vulnerabilities fixed in the last twelve months.
- Stays with you
- Disclosure policy, contact address, update mechanism and security advisories.
Compile the technical documentation
One file per product: description, design, vulnerability handling processes including the SBOM, risk assessment, standards applied, test reports.
- Kodator supplies
- Evidence report per product and release, the frozen SBOM and the frozen list of findings (JSON, CSV) as building blocks for the file.
- Stays with you
- Write all other parts of the file, bring them together and keep them up to date.
Assess and declare conformity, affix the CE mark
Before the product is placed on the market, its conformity is assessed, the EU declaration of conformity is drawn up and the CE mark is affixed.
- Kodator supplies
- No contribution.
- Stays with you
- Conformity assessment, signed EU declaration of conformity and CE mark.
Monitor and report during the support period
Vulnerabilities of the product continue to be handled during the support period. Actively exploited vulnerabilities and severe incidents have to be reported through the ENISA reporting platform: early warning within 24 hours, notification within 72 hours.
- Kodator supplies
- New vulnerabilities are matched daily against the current SBOM of every asset, without a new scan. Actively exploited ones are flagged.
- Stays with you
- Decide whether a report is due, submit it in time and inform affected users.
Keep the documentation for at least ten years
Technical documentation and declaration of conformity have to be kept for at least ten years after the product was placed on the market.
- Kodator supplies
- A release cannot be changed or deleted after it has been frozen; its content hash is in the audit log.
- Stays with you
- Keep the file for the whole period, including your own backups of the exported evidence.
In the product
CRA evidence report per product and release
Every clause with status, figures and the wording of the Official Journal. You see at once what is proven, what is only partly visible and what you have to contribute yourself, without flattering traffic lights.
- Proven
- Partly indicated
- Not covered
- The report opens with a coverage statement: what was examined and what was not.
- There is no overall score and no verdict such as "passed", only the state of the evidence per clause.
- Frozen for a release, live for a product.
In development
What we are working on next:
- VEX statements on exploitability
- Evidence report as PDF and a complete evidence package
- SBOM quality check against BSI TR-03183-2
- Retention rules for stored releases
What Kodator is not
Kodator supplies evidence from scans and remediation. It does not make a product compliant, does not assess conformity and does not issue a declaration. Risk assessment, conformity assessment and declaration of conformity stay with the manufacturer.
Reporting duty · Art. 14
Spot actively exploited vulnerabilities early
Since 11 Sep 2026 manufacturers have had to report actively exploited vulnerabilities in their products on the ENISA reporting platform. The deadlines are short. What counts is knowing early that one of your own products is affected.
Early warning
24 hours
First notice after you become aware of the active exploitation.
Notification
72 hours
Details of the product, the vulnerability and the measures you have taken.
Final report
14 days
After a fix or another mitigation is available.
How Kodator helps today
- Kodator matches newly published vulnerabilities against the stored bill of materials (SBOM) of every asset each day. You learn about a new issue without scanning again.
- Findings whose vulnerability is known to be actively exploited are marked as such.
- For every finding you see the affected component and version, the severity and the likelihood of exploitation.
- Remediation deadlines and the audit log record when a vulnerability was found and when it was fixed.
What stays with you: assess whether the vulnerability is actually exploited in your product, submit the report on the ENISA platform and inform affected users. Kodator does not submit reports.
Next step
See Kodator on your own code.
Tell us which product and which requirement you are dealing with. In a demo we show you which evidence Kodator supplies for it, and which it does not.