FAQ: Frequently asked questions
Regulations
What is the Cyber Resilience Act (CRA)?
The Cyber Resilience Act is a landmark EU regulation that for the first time establishes EU-wide cybersecurity requirements for products with digital elements. This means that almost all connected devices and software products must meet basic security standards to be authorized for the European market. The focus is on the entire lifecycle – from development to regular security updates.
When will the CRA become mandatory for me?
The CRA entered into force on 10 December 2024. The reporting obligations for actively exploited vulnerabilities and severe incidents have applied since 11 September 2026, all other requirements apply from 11 December 2027. Since the CRA requires documentation across the entire lifecycle, products that will still be on the market at the end of 2027 must be recorded today. Anyone who only starts in 2027 will have a documentation deficit for all existing versions.
What does the Machinery Directive 2006/42/EC still mean for me today?
The Machinery Directive remains the legal basis for all machinery placed on the market until 19 January 2027, for its entire lifetime. For these existing products the technical file must be available for at least ten years, and the risk assessment and instructions must match the actual state of the machine. Particularly important for machines with software: firmware updates, new HMI versions or retrofitted connectivity must be documented and checked for whether they constitute a substantial modification. The machine then counts as new and needs a new conformity assessment.
What does the Machinery Regulation (EU) 2023/1230 change?
The Machinery Regulation applies directly in all member states from 20 January 2027 and replaces the Machinery Directive for newly placed machinery. New above all are the cybersecurity requirements: the machine must be protected against corruption, and the control system must remain safe even under attack from outside. The regulation also defines substantial modification, which can be triggered by software updates, and allows digital instructions. The CRA provides that machinery meeting its requirements is deemed to conform with the cybersecurity requirements of the Machinery Regulation. Anyone keeping the CRA documentation therefore has the basis for this part of the technical file.
Which legal basis applies to my machine?
The decisive factor is the date of placing on the market. Machinery placed on the market until 19 January 2027 falls under the Machinery Directive and stays there. Machinery placed on the market from 20 January 2027 must meet the Machinery Regulation, there is no transition period. If an existing machine is substantially modified, it counts as newly placed on the market and is subject to the law applicable at that time. Products with digital elements additionally fall under the CRA. A final classification should be made by a specialised consultant where needed.
How does a product inventory like ProductShield help implement these regulations?
All three regulations ask the same questions: what is in which product, in which version, with which risks, and what was changed when? ProductShield answers them from one data basis. You create machines and products with their hardware, software and firmware assets, import or generate SBOMs, have components checked for vulnerabilities and document your risk decisions with reasoning. Every change is recorded as a version. From this, the CRA conformity report and the exports for the technical file under the Machinery Directive and the Machinery Regulation are generated, without you maintaining separate documentation for each regulation.
Which companies is ProductShield designed for?
ProductShield was specifically developed for manufacturers who develop and distribute hardware and software products (including embedded systems). Our focus is on medium-sized companies, particularly in sectors such as mechanical engineering, industrial automation, medical technology, and IoT solutions. We help translate often complex regulatory requirements into a structured, manageable process.
Does ProductShield replace a management system such as ISO 27001 or IEC 62443?
No. An information security management system or a secure development process according to IEC 62443-4-1 governs organisation, roles and procedures in your company. ProductShield is the system in which you keep the product data for it: which components are in which product, which vulnerabilities were assessed and how, which measures and support periods apply. You integrate this evidence into an existing management system or use it as the basis for building one.
Functions & Technology
What is the difference between SBOM and CBOM?
Both are essential inventory lists for compliance:
SBOM (Software Bill of Materials): An inventory list of all software components. It makes visible which third-party libraries (open source or proprietary) you are using.
CBOM (Cryptography Bill of Materials): A specialized list of all cryptographic assets (algorithms, protocols, keys). The CRA requires transparency about how you protect data and what encryption is used.
SBOM (Software Bill of Materials): An inventory list of all software components. It makes visible which third-party libraries (open source or proprietary) you are using.
CBOM (Cryptography Bill of Materials): A specialized list of all cryptographic assets (algorithms, protocols, keys). The CRA requires transparency about how you protect data and what encryption is used.
Can ProductShield map complex product structures?
Yes. Unlike simple scanners, ProductShield allows for the linking of assets. You can define: "This product consists of hardware board A, on which firmware B runs, which in turn communicates with cloud backend C." This holistic view is crucial for a CRA-compliant risk analysis that goes beyond pure software vulnerabilities.
Does the platform support automatic EOL checks?
Yes, this is a core function for hardware manufacturers. You can store lifecycle data for components. ProductShield compares these and warns you proactively when a component reaches "End-of-Life" (EOL) status or the support period ends. This way, you avoid compliance gaps for long-term available industrial products.
How does AI help with risk assessment?
Hundreds of new vulnerabilities (CVEs) are discovered every day. Our AI engine helps filter this flood. It checks: "Is this vulnerability even exploitable in your specific hardware context?" The AI makes suggestions for prioritization and helps to efficiently create the necessary written justification for the risk assessment (a CRA mandatory point).
Service & Support
Does netzmal also offer consulting for CRA implementation?
Yes. ProductShield is the tool, but we know that the path to compliance also requires process consulting. We offer onboarding packages and workshops in which we carry out the first inventory together with your developers and product owners and clarify the distribution of roles in the company.
Is there an API for existing CI/CD pipelines?
Yes, API access is included in the Professional and Enterprise packages. This allows you to integrate the generation or upload of SBOMs directly into your build process, so that ProductShield always knows the latest status of your software versions.
Is my product data safe?
Absolutely. Product security and confidentiality are extremely important to us. We host ProductShield exclusively on certified servers in Germany. All data is stored encrypted and we do not grant access to third parties. For companies with particularly high security requirements, we also offer on-premise options or dedicated cloud instances.