Your products include open-source and third-party components. TIOBE's software composition analysis (SCA) inventories them, identifies their known vulnerabilities and their license obligations, and produces the SBOM. A concrete first step towards the Cyber Resilience Act.
Entry into force of the regulation
Reporting of actively exploited vulnerabilities and severe incidents
Full application: essential requirements, SBOM, CE marking
The code you did not write is often the largest part of your software. The analysis makes it visible, from the dashboard down to the details of each component.
The published vulnerabilities of the components you use, with the weaknesses (CWEs) that cause them: you understand the problem, not just its number.
The licenses of each component, their risks and the obligations they impose on you.
The complete, machine-readable inventory of the components of your software (Software Bill of Materials).
Issues ranked by severity and impact: your teams know what to fix first.
The analysis runs in your environment: your source code does not leave your premises. Results usually come within one work week.
Regulation (EU) 2024/2847 applies to products with digital elements placed on the European market: hardware and software, components included. Part of its requirements directly concern the components you integrate.
| What the CRA requires | What the SCA analysis provides | What remains your responsibility |
|---|---|---|
| Identify and document components in a machine-readable SBOM (at least the top-level dependencies) | The SBOM of the analyzed product | Keeping it up to date at every version |
| Place on the market a product without known exploitable vulnerabilities | The known vulnerabilities of the components, ranked by severity | Judging their exploitability in your product, fixing them |
| Handle vulnerabilities throughout the support period (five years in principle), with security updates | A repeatable measurement that can be integrated into your continuous integration | The handling and disclosure process, the updates |
| Report actively exploited vulnerabilities: early warning within 24 h, notification within 72 h, then a final report | Knowing quickly whether one of your products contains the component concerned | The reporting itself, to ENISA and the national CSIRT |
SCA covers other people's code. Weaknesses in your own code are a matter for static analysis: TiCS brings together the results of your analyzers, and security is part of the TQI. TiCS also accepts SCA tools, such as Black Duck or Mend, to track components in the same dashboard.
Medical devices, motor vehicles subject to type approval, civil aviation and marine equipment fall under their own legislation and are excluded from the CRA. Other sectors, such as industry or energy, do not benefit from these exclusions. Check the scope product by product.
Non-compliance with the essential requirements can cost up to €15 million or 2.5% of worldwide turnover. This page summarizes the regulation; it does not constitute legal advice.
Spot a vulnerable component or an incompatible license early, before they are integrated everywhere.
Show your customers and auditors that your open-source components are under control.
Keep the inventory of third-party components: the SOUP list of IEC 62304, the supply chain of IEC 62443.
Assess the software risks of a company or a product before committing.
The analysis is performed by TIOBE. Precilog is your point of contact in France.
Together, we define the product, its repositories and your deadline. A pressing date? Let us know: we will do our best to meet it.
The analysis runs in your environment; your source code does not leave your premises.
Vulnerabilities, licenses, SBOM and priorities, from the dashboard down to the details of each component.
If you wish, the analysis is integrated into your continuous integration pipeline, for a measurement at every version.
Tell us about the product concerned and your deadline: we will get back to you with a proposal.