Why does CRA compliance need governance, process and technology working as one?
CRA obligations run across the whole product lifecycle. A compliance binder assembled before launch will not carry you through a multi-year support period. We look at every CRA programme in three layers:
- Governance: who classifies the product, who approves the support period, who signs off an Article 14 report. These decisions belong in your existing management system and delegation of authority.
- Process: requirements, engineering, procurement, release and customer support already run every day. Each one picks up the CRA requirements that naturally land on it.
- Technology: SBOM generation, vulnerability matching and signed updates live in the build pipeline and produce evidence automatically.
Fix only one layer and the usual result is policies nobody follows, or tools whose output nobody owns. The value of integration is that each piece of evidence is created once, then serves management and compliance upstream and engineering downstream.
That is how we work. We start from the management system you already operate and build the CRA requirements into it rather than standing up a parallel one, cutting duplicated effort now and maintenance cost later. One team covers risk management, standards and regulatory compliance, implementation and security engineering, and process improvement, and VP- and director-level consultants lead the engagement end to end, never outsourced. For the engineering detail, see CRA technical integration. This page is about what comes next: continuous improvement and supply chain assurance.
How does Ahura let CRA evidence be reused across other standards and regulations?
CRA evidence has a long shelf life and many readers: notified bodies, EU customers, market surveillance authorities, and your own ISO 27001 or IEC 62443 auditors. Continuous integration starts from one principle: a single evidence record and a single sign-off chain should be referenced by every framework that needs it, instead of each project keeping its own copy.
The Ahura enterprise risk management platform is currently at proof-of-concept (POC) stage. Everything below refers to the POC version.
- Available in the POC: 100% on-premises deployment; an end-to-end evidence chain in which every sign-off is recorded and compatible with EU eIDAS certificates; a group-wide distributed architecture; EU multilingual interface; modular extension for EU regulations and international standards. CRA workflows cover threat modelling, SBOM-based vulnerability management, tracking of the 24- and 72-hour ENISA reporting deadlines, and generation and sign-off of technical documentation.
- In development, released as the POC progresses: cross-standard comparison, gap analysis on uploaded documents, regulatory version timelines and regulatory change tracking.
The synergy comes in two stages. Today, SBOMs, vulnerability handling records and reporting timelines are signed off on one chain and can be cited both in the CRA technical documentation and in audits of your other management systems. Once the development features ship, the goal is to map the same evidence to clauses across several standards and to show which evidence needs a second look when a regulation changes.
What does outsourcing your CRA internal audit to Winners Consulting deliver?
Once a product is on the market, the CRA expects its mechanisms to keep working: vulnerabilities handled, updates shipped, reporting clocks met. Internal audit is how you check that they actually do. Our internal audit outsourcing service typically covers the PSIRT path from intake to regulatory report, the SBOM and vulnerability handling records for each release, update records across the support period, and whether technical documentation keeps pace with product versions.
Objectivity comes first. Under ISO 9000:2015, 3.13.1, an internal (first-party) audit may be conducted by the organisation itself or on its behalf, and independence can be demonstrated by freedom from responsibility for the activity being audited. ISO/IEC 27001:2022, clause 9.2, likewise requires auditors to be selected and audits conducted so that the audit process is objective and impartial. Our principle follows directly: a consultant never audits a process they designed. The audit is performed by a consultant who had no part in that design.
After the audit we sit down with your management team, review the findings and sort the improvements into three horizons: fixes that cannot wait, work for the next product generation, and longer-term capability building. The result is a roadmap you can track, not a report that sits on a shelf. An internal audit is not third-party certification and does not replace a notified body's conformity assessment; Winners Consulting provides consulting only and does not issue certifications.
How do supplier audits extend CRA Article 13(5) due diligence into your supply chain?
Article 13(5) of the CRA requires manufacturers to exercise due diligence when integrating components sourced from third parties, so that those components do not compromise the product's cybersecurity, and this includes free and open-source components not supplied in the course of a commercial activity. Article 13(6) requires manufacturers who find a vulnerability in a component to report it to whoever maintains it. A large share of your product's security sits with your suppliers.
Our CRA supplier audit service carries out those audits on your behalf. Under ISO 9000:2015, 3.13.1, an audit performed by a customer or by someone acting for the customer is a second-party audit. It is not certification: the findings belong to you and feed directly into supplier terms and corrective actions, giving you supply chain assurance you can evidence.
| Supplier type | Audit focus (CRA requirement) | Evidence retained |
|---|---|---|
| Commercial software and firmware component vendors | Art. 13(5): component origin, versions, maintenance status | Component due diligence records, supplier SBOMs |
| Open-source components | Art. 13(5) and 13(6): maintenance status, upstream vulnerability reporting | Component assessments, upstream reports |
| Outsourced development partners | Art. 13(5): secure development and scanning of deliverables | Scan reports, delivered SBOMs, audit report |
| Hardware and module ODMs | Art. 13(5): firmware component inventory and update mechanism | Firmware SBOMs, update signing records |
| Cloud back-end providers for the product | Art. 14: timely flow of vulnerability and incident information | Notification clauses, reporting drill records |
Open-source communities usually cannot be audited, so we assess them instead. To scope a supplier audit programme, contact us.
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
- ISO/TC 176 — Terms and definitions in TC 176 standards (ISO 9000:2015, 3.13.1 audit, Notes 1–4)
- ISO CASCO — Conformity assessment techniques: Auditing (first-, second-, third-party audits)
