Which existing processes does the CRA plug into: product planning, engineering, releases or customer support?
The CRA is product legislation, so its obligations follow each product from planning to end of support. We do not recommend a separate stack of “CRA project documents”. Instead we find the processes you already run and attach the legal requirements to them.
- Product planning and requirements: carry out the Article 13(2) cybersecurity risk assessment at the requirements stage, decide which Annex I Part I(2) requirements apply, and set the support period (Article 13(8)).
- Engineering and CI/CD: security design reviews, code and dependency scanning and SBOM generation all live in the build pipeline, not in a last-minute paperwork push before release.
- Procurement and component management: third-party and open-source components need due diligence (Article 13(5)); the component master data is where the SBOM starts.
- Releases and updates: security updates go out without delay and, in principle, free of charge, separately from functionality updates where technically feasible (Annex I Part II(2) and (8)).
- Customer support and vulnerability intake: support tickets, distributor reports and researcher emails must all reach the PSIRT, which decides whether Article 14 reporting is triggered.
Done this way, every requirement has an existing owner instead of landing on one compliance officer. There is no time to wait: Article 14 reporting has applied since 11 September 2026, including products already on the market, and the remaining obligations apply from 11 December 2027.
Which technologies implement SBOM, VEX, PSIRT and CVD under the CRA, and what evidence do they leave?
The table maps the legal text to what engineering teams actually build. The first column follows the official text; the implementation column is our good-practice recommendation, not legal wording. VEX, SPDX and CycloneDX are common industry practice; the CRA itself does not prescribe a format.
| Requirement (article / control) | Implementation technology | Evidence left behind |
|---|---|---|
| Article 13(2): cybersecurity risk assessment | Threat modelling, attack-surface and data-flow inventory | Risk assessment report, versioned threat model |
| Annex I Part I(2): secure by default, access control, data protection, limited attack surface and more | Security design review, default configuration baseline, SAST and dependency scanning in CI/CD | Design review records, scan reports, build logs |
| Annex I Part II(1); Article 13(5): identify components, draw up an SBOM, component due diligence | Machine-readable SBOM generated at build time (e.g. SPDX, CycloneDX), checks on component origin and maintenance status | SBOM per release, component due-diligence records |
| Annex I Part II(2) and (3): remediate according to risk, regular security testing | SBOM matched against public vulnerability data, VEX statements on exploitability, scheduled security tests | Remediation records, VEX documents, test reports |
| Annex I Part II(5) and (6); Article 13(6): CVD policy, contact point, reporting upstream | Published CVD policy and contact address, PSIRT ticketing | CVD policy, intake records, upstream reports |
| Article 14(1)–(4); Article 16: 24/72-hour reporting | Awareness timestamps, deadline countdowns, report templates, submission via the single reporting platform | Early warning, notification, final report and timeline |
| Annex I Part II(7) and (8); Article 13(9): secure distribution of updates | Signed updates with verification, security updates separated from feature updates | Update advisories, signing and distribution records |
| Article 13(8); Annex VII: support period and technical documentation | Documented support-period rationale, version-controlled technical documentation | Support-period rationale, technical documentation, EU declaration of conformity |
The point is not the number of tools but that every output traces back to a specific release. Article 13(13) requires the technical documentation and EU declaration of conformity to be kept for at least 10 years or the support period, whichever is longer, so evidence needs versions, timestamps and named approvers from day one.
As for sequence, we recommend getting SBOM generation and vulnerability matching running automatically in CI/CD first, because the same output feeds remediation, the reporting decision and the technical documentation. Publish the CVD policy and contact point early, so external reporters have somewhere to go. Remote data processing designed by the manufacturer that the product needs to function, such as a cloud back-end, is part of the product, so its components must be managed too.
How does CRA product risk connect to legal requirements, technical controls and monitoring metrics?
We run every product risk through the same chain:
- Risk identification: threat modelling surfaces the attack surface, such as remote management interfaces, the firmware update channel or cloud back-end APIs.
- Legal requirement: map it to specific items in Annex I Part I(2) and Part II, and confirm the product class and assessment route (Articles 7, 8 and 32; Implementing Regulation (EU) 2025/2392).
- Technical control: for example signature verification on the update channel, unnecessary services off by default, automatic SBOM-to-vulnerability matching.
- Monitoring metric: for example whether every release has an SBOM, how long it took from becoming aware of an actively exploited vulnerability to sending the early warning, and whether the final report went out within 14 days of a fix becoming available.
This chain breaks whenever it changes hands. At Winners, one team plans the legal scoping, the processes and the technical controls together. We first determine the class of each product family and the supply-chain role of each product line, get the Article 14 reporting process running, then complete the Annex I requirements and technical documentation, and finally streamline the processes.
Winners has been commissioned by Taiwan’s Ministry of Digital Affairs and the software industry association TISSA to support exporters with CRA readiness; as of October 2026, six companies are in CRA advisory engagements with us. Our own delivery pipeline generates, signs and monitors SBOMs every day, so what we teach comes from practice.
The cost of an uncontrolled risk is explicit: breaching Annex I, Article 13 or Article 14 carries fines of up to EUR 15 million or 2.5% of worldwide annual turnover, whichever is higher (Article 64(2)).
Which departments, systems, data and evidence must be integrated vertically for the CRA?
Vertical integration means each piece of data is produced once and serves compliance and management above as well as engineering below. The most common waste in CRA projects is engineering already having build records while compliance asks someone to fill in forms before release, or support receiving a vulnerability report without anyone realising the reporting clock has started.
| Department | System | Data | Evidence |
|---|---|---|---|
| Product management | Requirements and portfolio management | Product families, intended purpose, support period | Classification determination, support-period rationale |
| Engineering / DevOps | Version control, CI/CD, SBOM tooling | Source code, dependencies, build artefacts | Scan reports, SBOM per release, build logs |
| QA / testing | Test management, vulnerability scanning, penetration testing | Test cases, vulnerability lists | Test reports, VEX decisions |
| PSIRT / customer support | Ticketing, vulnerability reporting channel | Vulnerability reports, time of awareness | Reporting timeline, user notification records |
| Procurement / supply chain | Component and supplier master data | Component origin, licences, maintenance status | Due-diligence records, upstream reports |
| Compliance / legal | Document management, approval workflow | Technical documentation, draft declaration of conformity | Annex VII technical documentation, EU declaration of conformity |
We usually integrate in this order: PSIRT and support first, because Article 14 already applies; then CI/CD outputs feeding the technical documentation; procurement and component master data last. Each evidence item needs a named owner and storage location, so that when an auditor or authority asks, it comes out of one place rather than someone’s inbox.
The table is also our interview checklist at project start: for each row we find the counterpart, confirm what data the systems already hold, and fill only the gaps, so the CRA does not spawn a parallel set of records.
What does Ahura do in a CRA project, and how does the data flow?
The Ahura Enterprise Risk Management Platform is a Taiwan-born RegTech platform developed by Winners Consulting. It is currently at the POC (proof-of-concept) stage, and everything below describes the POC build.
CRA workflow capabilities (POC build): threat modelling, SBOM vulnerability management, tracking of the 24/72-hour ENISA statutory reporting deadlines, and CRA technical documentation with sign-off records. The POC interface includes threat-modelling, compliance sign-off and ENISA reporting screens.
Data flow:
- Consultant deliverables (classification, risk assessment, CVD policy) and the SBOMs, scan and test records produced by your CI/CD go into Ahura, deployed on your premises.
- Every sign-off enters the evidence chain, compatible with EU eIDAS certificates.
- Auditors, certification bodies or authorities retrieve evidence from that same chain.
Deployment and architecture: 100% on-premises; client documents and data never go to the cloud or leave your environment. A group-style distributed architecture keeps HQ policy uniform while each site stays locally compliant. The interface supports EU languages such as German, French, Dutch and Czech, plus Traditional Chinese and English.
Ahura is built to the same discipline: automated SSDLC gates (static analysis, dependency and secret scanning) leave evidence on every build, and security scans, SBOMs, tests and change records are all logged.
In development, released as the POC progresses: document upload with compliance gap analysis, regulatory version timelines, cross-standard comparison and regulatory change tracking.
The split is clear: consultants handle scoping, processes and documentation; Ahura keeps the evidence inside your own environment.
What governance, risk, efficiency and continuous-compliance results does CRA integration produce?
We describe results in ways that can be checked:
- Governance: every product family has a classification, a support period and an owner; management sees reporting-drill results and timelines, not just “implemented”.
- Risk: actively exploited vulnerabilities follow a fixed assessment and reporting path, and the 24/72-hour deadlines are backed by timestamps; component risk becomes visible at procurement and build time.
- Efficiency: SBOMs, scans and tests are generated at build time and referenced directly by the technical documentation, so nothing has to be rebuilt before each audit. The same SBOM answers customer questionnaires and supply-chain audits.
- Continuous compliance: vulnerability handling and updates during the support period are recorded; each security update stays available for at least 10 years or the rest of the support period, whichever is longer (Article 13(9)).
We start from the management system you already run and build the CRA requirements into your existing engineering, quality and support processes instead of setting up a separate one, cutting duplicated effort now and maintenance cost later. Companies with an ISO 27001 or IEC 62443 foundation can reuse existing controls and records, so one set of evidence serves several regulations and customer requirements.
VP- and director-level consultants lead the work end to end, never outsourced, and our consultants hold ISO Lead Auditor qualifications. Winners provides consulting only and does not issue certifications; where third-party conformity assessment is needed, a notified body carries it out, and Article 39(4) of the CRA bars notified bodies from providing consultancy services.
To find out where your product should start, contact us.
Continuous assurance & trusted supply chain: EU CRA Internal Audit Outsourcing & Supplier Audits
Technical integration for related services
Official sources
- Regulation (EU) 2024/2847 (Cyber Resilience Act), OJ L, 20.11.2024 — EUR-Lex
- European Commission — The Cyber Resilience Act: summary of the legislative text
- Commission Implementing Regulation (EU) 2025/2392 — technical description of important and critical product categories — EUR-Lex
- ENISA — Cyber Resilience Act Requirements Standards Mapping
