How you work with ProductShield

From the first product to the evidence in four steps – structured and traceable instead of spreadsheet chaos.

1Record products and assets

Create machines, hardware, software, SaaS and cloud products with versions and owners: existing machines under the Machinery Directive as well as new products under the CRA and the Machinery Regulation. This is the foundation all further evidence refers to.

Functions in this step

  • Product and Asset Management Centrally create, structure, and document versions of products. Track the compliance maturity level per product.
  • Version Management Document the entire lifecycle of your products and every change to software and firmware. This proves what was changed when, and whether an update constitutes a substantial modification under the Machinery Directive or the Machinery Regulation.
  • Hardware EOL Check Check the end-of-life status of your hardware components and identify obsolete parts early.
Product overview with versions and status
Product overview with versions and status

2Import or generate SBOMs and CBOMs

Import existing bills of materials or generate them directly in ProductShield. Cryptographic components are kept separately in the CBOM.

Functions in this step

  • SBOM Creation & Import Create SBOMs for your software products or import existing lists in common formats.
  • CBOM Management Maintain Cryptography Bill of Materials to document cryptographic assets and algorithms traceably.
SBOM import with detected components
SBOM import with detected components

3Assess vulnerabilities and risks

Libraries are checked for known vulnerabilities, risks are pre-assessed with AI support and documented traceably – you decide what is relevant.

Functions in this step

  • Library & Vulnerability Analysis Automatically check used libraries for known vulnerabilities and derive necessary measures.
  • AI-supported Risk Assessment Assess risks at product and asset level with the support of artificial intelligence.
Risk assessment per component
Risk assessment per component

4Generate evidence

The maintained data turns into the CRA conformity report as a structured basis for your technical documentation. You export the same data for the technical file under the Machinery Directive and the Machinery Regulation or as evidence for your customers.

Functions in this step

  • CRA Compliance Reports Create technical documentation and status reports for internal audits, customers, or auditors. The same data is available as evidence for the Machinery Directive, the Machinery Regulation and customer audits.
Conformity report and evidence exports
Conformity report and evidence exports