TiCS · Software composition and the CRA

Your software components, and their vulnerabilities, under control

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.

Cyber Resilience Act · timeline
10 December 2024in force

Entry into force of the regulation

11 September 2026in force

Reporting of actively exploited vulnerabilities and severe incidents

11 December 2027

Full application: essential requirements, SBOM, CE marking

Software composition analysis

Know what your product contains

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.

◆

Known vulnerabilities

The published vulnerabilities of the components you use, with the weaknesses (CWEs) that cause them: you understand the problem, not just its number.

◆

Licenses

The licenses of each component, their risks and the obligations they impose on you.

◆

SBOM

The complete, machine-readable inventory of the components of your software (Software Bill of Materials).

◆

Priorities

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.

Cyber Resilience Act

What the regulation changes for your components

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 requiresWhat the SCA analysis providesWhat remains your responsibility
Identify and document components in a machine-readable SBOM (at least the top-level dependencies)The SBOM of the analyzed productKeeping it up to date at every version
Place on the market a product without known exploitable vulnerabilitiesThe known vulnerabilities of the components, ranked by severityJudging their exploitability in your product, fixing them
Handle vulnerabilities throughout the support period (five years in principle), with security updatesA repeatable measurement that can be integrated into your continuous integrationThe handling and disclosure process, the updates
Report actively exploited vulnerabilities: early warning within 24 h, notification within 72 h, then a final reportKnowing quickly whether one of your products contains the component concernedThe reporting itself, to ENISA and the national CSIRT

What about your own code?

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.

Are you concerned?

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.

What for

Beyond the CRA

◆

In development

Spot a vulnerable component or an incompatible license early, before they are integrated everywhere.

◆

Facing audits

Show your customers and auditors that your open-source components are under control.

◆

For your standards

Keep the inventory of third-party components: the SOUP list of IEC 62304, the supply chain of IEC 62443.

◆

Before an acquisition

Assess the software risks of a company or a product before committing.

How it works

From request to results, in about a week

The analysis is performed by TIOBE. Precilog is your point of contact in France.

01

Scope

Together, we define the product, its repositories and your deadline. A pressing date? Let us know: we will do our best to meet it.

Precilog
02

Analyze

The analysis runs in your environment; your source code does not leave your premises.

TIOBE
03

Use the results

Vulnerabilities, licenses, SBOM and priorities, from the dashboard down to the details of each component.

Results
04

Monitor over time

If you wish, the analysis is integrated into your continuous integration pipeline, for a measurement at every version.

Optional

Take stock of your components

Tell us about the product concerned and your deadline: we will get back to you with a proposal.

Request an SCA analysis →

TiCS  ·  Standards  ·  TQI quality audit