Cyber Resilience Act · Regulation (EU) 2024/2847
CRA compliance for your product, across its entire lifecycle.
Trackle Guardian is the platform manufacturers use to keep vulnerability handling under control across firmware, apps and hardware: from the SBOM to the fix, through advisories and reports, with a record of every decision.
Release 3.2.0
Industrial gateway X200
Grade
Firmware 3.2.0
Software component
App 2.8.1
Software component
Hardware rev. C
Hardware component
Art. 14 · Early warning
due in 18 h
Security advisory published
VEX · Not affected
VEX analysis inherited from 3.1.4
In force since 11 September 2026
Reporting
Actively exploited vulnerabilities and severe incidents must be reported
From 11 December 2027
All obligations
All other requirements of the regulation apply
Fines up to
€15M
or 2.5% of worldwide annual turnover
The context
The Cyber Resilience Act
What it is
Regulation (EU) 2024/2847 sets the cybersecurity requirements for products with digital elements sold in the European Union. It is a prerequisite for CE marking.
Who it applies to
Anyone placing digital products on the EU market. The main obligations fall on the manufacturer: whoever sells the product under their own name or trademark.
What it requires
Design the product according to the essential cybersecurity requirements
Handle vulnerabilities for the whole support period (normally at least 5 years)
Report actively exploited vulnerabilities and severe incidents
Technical documentation, conformity assessment, EU declaration, CE marking
What it means for the manufacturer
Vulnerability handling lasts as long as the product
The manufacturer must guarantee it for the entire product lifecycle, not only at launch.
01
Know and monitor
Always know which components are in the product, with a machine-readable SBOM, and check every new vulnerability for the whole support period.
02
Fix and inform
Place products on the market without known exploitable vulnerabilities. Fix without delay, distribute secure and free updates, publish security advisories.
03
Report
Report actively exploited vulnerabilities and severe incidents to the CSIRT and ENISA.
24 h
Early warning
72 h
Notification
14/30 d
Final report
Monitoring dependencies is no longer enough. You must prove what was done, when, and for which product.
Lifecycle
Alongside the product, from the first SBOM to the last update
Every phase leaves a trace in the product history: the evidence of compliance the CRA asks for.
01
Compose
Firmware, apps and hardware described as a single system, each with its SBOM or identifier.
02
Release
A release combines versions into one bill of materials. Releases with known exploitable vulnerabilities are blocked.
03
Monitor
Continuous checks against public sources and an A–F grade per version, product and portfolio.
04
Analyse and fix
VEX analyses inherited across versions, cases with priority, plan and deadlines.
05
Communicate
Security advisories linked to case and release, public trust center for customer visibility.
06
Report
Art. 14 register with 24-hour, 72-hour and final report deadlines.
For the whole support period · normally at least 5 years
The supply chain
The manufacturer stays in control
One supplier builds the firmware, another the app. But under the CRA, the manufacturer is accountable.
Today
SBOMs scattered across suppliers, when they exist.
Each supplier only looks at its own software.
"Everything is fine" is the supplier's word.
No view of the finished product, no record of decisions.
With Trackle Guardian
One view per product
Firmware, apps and hardware together.
Suppliers upload, the manufacturer decides
Each supplier sends its SBOM with a dedicated token; analysis, priorities and decisions stay with the manufacturer.
Independent verification
Vulnerabilities are checked against public sources, not on the supplier's word.
Everything tracked
Analyses, cases, advisories and reports stay in the product history.
“The tool manufacturers can trust to keep vulnerability handling for their products under control.”
The model
The product as a system of components
A digital product is not a single piece of software: it is a system of firmware, apps and hardware.
Software components: each firmware and app has its own versions and SBOM, continuously monitored.
Hardware components: each hardware item is identified by manufacturer, part number, revision and firmware version.
Release: combines firmware, app and hardware versions into a single bill of materials.
Each component can be assigned to several products and managed only once.
Product · 2 SBOMs
Firmware
Software component
App
Software component
Hardware
Hardware component
Platform
Service / platform
Release
Firmware, app, hardware and platform in a single bill of materials
The platform
From vulnerability to fix
The vulnerability handling process, with deadlines always in sight.
A to F grade
One grade per version, product and portfolio, computed by a proprietary algorithm on the vulnerabilities still open.
Inherited analyses
Each vulnerability is analysed with VEX: exploitable, not affected (with justification), under analysis, resolved. New versions inherit the analysis.
To do
The dashboard shows what to do every day, per product and portfolio, with upcoming obligations up front.
Cases
Every vulnerability to fix becomes a case, with priority, remediation decision and a plan with date and target.
Art. 14 register
For actively exploited vulnerabilities or severe incidents: 24-hour, 72-hour and final report deadlines. Submission stays with the manufacturer.
Security advisories
Once fixed, an advisory is generated, linked to the case and the release. Trackle Guardian flags fixes still without an advisory.
Automatic triage
Your team only gets the vulnerabilities that matter
A firmware can receive hundreds of reports, but many concern code your product doesn't contain or doesn't use. Trackle Guardian sorts them in three steps: your engineers only work on the ones that really affect the product.
01
Rules out what isn't in the product
For Linux-based firmware, every vulnerability is checked against the actual version and configuration of the system. If the flaw is already fixed, or the faulty code never made it into your product, it is ruled out with its justification.
Much of the noise disappears without taking anyone's time.
02
Assesses how the component is used
For the remaining vulnerabilities, artificial intelligence considers the role of each component in the product and the platform it runs on, and estimates whether the flaw can really be reached. Every estimate comes with its explanation.
The team starts from a reasoned proposal, not a raw list.
03
Verifies on the code, with evidence
Cases still open go to the developers, who check them on the source code with the AI assistant they already use. The result comes back to Trackle Guardian with evidence: where the code is and why the flaw can, or cannot, be reached.
Only real vulnerabilities become remediation work.
The decision stays with you
The three steps produce proposals, never decisions. A person on your team confirms them, even all at once: name, date and justification stay in the product history.
Fewer engineering hours
Analysis focuses on the vulnerabilities that really affect the product.
Defensible decisions
Every ruled-out vulnerability has its justification, ready for a customer or a market surveillance authority.
The most dangerous first
Actively exploited vulnerabilities are analysed first.
Versions already analysed
Analyses carry over to the next version and certain exclusions apply automatically to new vulnerabilities.
Transparency
Communicating with customers and the market
The CRA requires manufacturers to be reachable and transparent.
Disclosure policy and contact
security.txt (RFC 9116) with the coordinated disclosure policy and a contact for whoever finds a vulnerability.
Public advisories
Security advisories published per product, once the update is available.
Trust center
A public page with the manufacturer's brand: products, support period, advisories and, optionally, SBOMs.
Customer access
Business customers check the security status of the products they bought, without email requests.
Coverage
What Trackle Guardian covers
All CRA vulnerability handling obligations (Annex I, Part II) and all requirements of the draft standard prEN 40000-1-3.
The platform checks and shows the status, product by product.
SBOM for every software component and supplier coverage
Vulnerability analysis and fixes without delay
No known exploitable vulnerabilities, with release blocking
Advisories published for fixed vulnerabilities
Coordinated disclosure policy and contact
Support period
The manufacturer runs the process in Trackle Guardian, which keeps its history.
Cases, with acknowledgement and fix deadlines
Art. 14 reporting register, with deadlines and phases
Security advisories and trust center
Outside the scope of the platform.
Risk assessment and product design requirements
Device security testing
Submitting reports to CSIRT and ENISA
Technical documentation, conformity assessment, EU declaration, CE marking
Plans
Plans per organization
Start from monitoring and grow into full compliance management.
Start
Vulnerability monitoring
Up to 5 product families, 25 monitored SBOMs (*), CI/CD API
A–F grade, "Fix first"
SBOM quality checks
VEX analyses inherited across versions
Email notifications for new vulnerabilities
Member management with role-based access
Premium
Vulnerability handling and compliance
Up to 10 product families, 50 monitored SBOMs (*), CI/CD API
Everything in Start, plus:
CRA compliance status
Cases, security advisories, reporting register
Component certifications with expiry dates
Public trust center
Enterprise
Tailored plans for large companies
Up to 50 product families, 250 monitored SBOMs, CI/CD API
Everything in Premium, plus:
99.5% SLA with response times by severity
SSO, MFA, access log
History retained for 10 years
(*) Add-on packs: +5 product families and +25 monitored SBOMs.
Reporting is already mandatory.
Since 11 September 2026 manufacturers must report exploited vulnerabilities and severe incidents; from 11 December 2027 everything else applies. Let's get vulnerability handling for your products under control, now.
