Skip to content
Reltime
THE REGULATORY RAILS · Rail 3 / 8
CRA · Regulation (EU) 2024/2847

Every product version, proven.

Cyber Resilience Act

Anyone placing a product with digital elements on the EU market must handle vulnerabilities for the whole support period and report exploited ones within 24 hours. Reltime makes every version and every report provable.

Who it hits.

Manufacturers, importers and distributors of hardware and software with digital elements sold in the EU, wherever they are based. Retailers selling under their own brand count as manufacturers.

What it demands.

  1. Annex ISecurity by design and vulnerability handling for the full support period
  2. Annex I, Part IIA software bill of materials for the product
  3. Art. 14Report actively exploited vulnerabilities and severe incidents through the single reporting platform
  4. Art. 28, 31Technical documentation and an EU declaration of conformity
The clock
24 h
Early warning
72 h
Notification
14 days
Final report after a fix is available

Reporting since 11 Sep 2026 · Main obligations from 11 Dec 2027

Up to EUR 15m or 2.5% of global turnover

What Reltime runs. In real time.

Evidence per version

SBOM, tests and approvals anchored to each release as it ships.

Vulnerability clock on proof

Detection, assessment and fix tracked live. The 24-hour and 72-hour reports are drafted from the proof.

Supplier evidence chain

Component suppliers anchor their evidence once. You and your customers verify it.

Updates gated

Security updates released only when the required sign-off is anchored.

Documentation that holds

Technical file and declaration tied to the exact version they describe.

RELTIME VERIFICATION RECEIPTExample
Event
Vulnerability triage · fw 4.2.1
Assessed by
psirt.lead · verified
Rule
cra-vuln-policy v1.0
Time
2026-10-14 11:47:30.019 CET
Fingerprint
9e2c…a771 · unchanged ✓

One receipt. Every auditor.

Who acted, which rule applied and whether anything changed. Created the second it happened. Verified by any authorised party without access to your systems.

Live in four weeks.

  1. Week 1

    Map one product line and connect the build and ticketing systems

  2. Week 2

    Configure the rail, roles and alerts

  3. Week 3

    Test with your counsel or auditor

  4. Week 4

    Run in real time and deliver the first evidence pack

Related rails