Help: En bref · Onglet par onglet
Thermostat connecté TC-200 (exemple fictif) — proof path
Five steps, in order. Each upload happens right here; the tabs give the detail.
CRA deadlines: reporting of actively exploited vulnerabilities and severe incidents (Art. 14) since 11 September 2026 (Declarations); full application from 11 December 2027.
⓪ Your product — to do
Thermostat connecté TC-200 (exemple fictif) — Not classified yet: the class tells which conformity assessment applies. Version: 2.4.1.
① Your requirements — ✓
8 requirement(s) in the project.
They come from the EU (the CRA, Annex I: import the CRA catalogue), from your plan or from your ALM (Jira, Polarion…: Requirements tab). The SBOM is not a source of requirements: it serves as evidence, step ③.
② Your test results — to rework
1 run(s) received; 6/8 requirement(s) proven, 1 case(s) never run — latest run: 22/11/2026, 04:07:03.
Templates: JUnit XML · TAP · JSON · plan — the rule: the name of each test starts with its reference in the plan. The format, in detail.
0 manual test(s) in the plan — review, inspection, bench: enter a result.
latest run: 6 passed, 0 failing — Test runs tab
③ Your SBOM — ✓
SBOM of version 2.4.1 uploaded (CycloneDX); quality 53 % (BSI TR-03183).
④ Your vulnerabilities — to do
22 known vulnerability(ies): 22 to assess.
Assess them and record your notes — affected, not affected (justification), fixed.
⑤ Your deliverable — ✓
Issued now for 2.4.1, it would carry the verdict NON-COMPLIANT.
Why: at least one requirement is not proven by a test that was run and passed
Reservations: test runs not tied to version "2.4.1" (reports without a validation report): all of the project's runs are taken into account; 22 known vulnerability(ies) to be assessed (under investigation); partial coverage: 1 component(s) could not be analysed (no covered ecosystem, no CPE)
Issue and seal · 1 deliverable(s) already issued · then: technical file, notifications.