Skip to content
  • Reporting since 11 Sept 2026
  • Full application from 11 Dec 2027
  • Servers in Germany
  • System status →
Cyber Resilience Act for manufacturers

Detect. Report. Prove.

Nebrino guides software, IoT and embedded manufacturers towards compliance with the Cyber Resilience Act: classify products, check SBOMs daily, meet reporting deadlines, build the documentation. Hosted on servers in Germany.

Request a pilot seatFree CRA checkNo credit card required

Sample data · HomeGate X2 · firmware 1.4.2

Overnight · daily matching

New vulnerability in a component

  • openssl 3.0.13…
  • busybox 1.36.1…
  • log4j-core 2.14.1…

CVE-2021-44228 · actively exploited (CISA KEV)

Immediately

Your team is alerted

Email to your team · Webhook, e.g. to Teams or Slack

In the morning · awareness recorded

Reporting case opened

Early warning due within

24:00:00

  • Fields for the ENISA platform prepared
  • Deadlines in your calendar
  • Emergency sheet at hand

Submission: by you, via the ENISA platform

Ready: matching your components

Am I affected?

Three typical manufacturers.

Examples, not customer references: what the Cyber Resilience Act means in three common situations – each with the legal reference and what Nebrino takes over.

Machinery and plant engineering

Controller with embedded Linux

Your machine has a controller or operator panel running Yocto Linux with remote maintenance. The devices run at customer sites for many years.

What the Regulation requires

  • Controller and software are products with digital elements – remote maintenance is the data connection. Art. 2(1), Art. 3(1)
  • Report actively exploited vulnerabilities since 11 Sep 2026 – also for machines already delivered. Art. 14, Art. 69(3)

How Nebrino helps

  • Upload SPDX 3.0 straight from the Yocto build; matching by CPE against the NVD, even without a package manager
  • Support period per version, with a reminder before it ends
Guide: Machinery Regulation →
IoT and smart home

Connected radio device

You build a security camera or a smart door lock with Wi-Fi and an app – with a small team and no compliance department.

What the Regulation requires

  • Smart home products with security functionalities are important products of Class I: self-assessment only with a fully applied harmonised standard, otherwise with a notified body. Annex III Class I No. 17, Art. 32(2)
  • Radio equipment has had to meet cybersecurity requirements under the Radio Equipment Directive (EN 18031 standards) since 1 Aug 2025 – until the Cyber Resilience Act replaces them on 11 Dec 2027. Delegated Reg. (EU) 2022/30 and 2026/339

How Nebrino helps

  • The CRA check assigns the device to a class and shows the conformity route
  • Checklists for Annex I and EN 18031
Guide: important and critical products →
Software company

Installable software

You sell software that customers install themselves – in their own data centre, on the desktop or as an app. Releases ship every few weeks.

What the Regulation requires

  • Pure software is a product with digital elements too; pure SaaS services without an associated product are not. Art. 2(1), Art. 3(1)
  • An SBOM covering at least the top-level dependencies; remediate vulnerabilities without delay. Annex I Part II (1) and (2)

How Nebrino helps

  • Upload the SBOM from CI on every release; the build stops if a component is actively exploited
  • Assess findings with VEX and share them with customers as CSAF or OpenVEX
Guide: EU declaration of conformity →
Reporting obligation · 11 Sept 2026

The clock starts at awareness.

Reporting obligations under Art. 14 have applied since 11 Sept 2026, including for products already on the market.

  • 24 h

    Early warning

  • 72 h

    Notification

  • 14 days

    Final report

    after corrective or mitigating measure

The Cyber Resilience Act sets upper limits for fines (Art. 64); the penalties themselves are laid down by the Member States. Open the fine calculator

Timetable

The Cyber Resilience Act applies in stages. The next one is the last.

  1. 10 Dec 2024

    Entry into force

    Regulation (EU) 2024/2847 enters into force.

  2. 11 Jun 2026

    Notified bodies

    Rules on conformity assessment bodies apply.

  3. 11 Sept 2026

    Reporting obligations

    Art. 14: report actively exploited vulnerabilities and severe incidents.

  4. 11 Dec 2027

    Full application

    All requirements, conformity assessment and CE marking.

    next stage

Features

Your CRA obligations in one place.

Instead of spreadsheets and inboxes.

What stays with you

Deciding and submitting: you decide whether a product is affected and what is reported, and you submit the notification yourself via ENISA’s reporting platform. Nebrino prepares, reminds and documents – it is not legal advice.

  1. Matching
  2. Match
  3. assessed
  4. fixed
Illustration

Illustration: the network shows a product’s software components. The daily check runs across it; a component with a vulnerability is marked red and the connections to the components depending on it are highlighted; once fixed, it returns to normal.

  1. 01 · Annex III · IV

    Classify

    Classify products

    A questionnaire assigns products to a category based on Annexes III and IV of the Cyber Resilience Act and shows the possible conformity assessment procedures – as a reasoned proposal.

    • Default, important Class I/II, critical
    • Open-source software stewards
    • Support period per version
  2. 02 · OSV · NVD · KEV · EUVD

    Check SBOMs

    SBOM monitoring, every day

    Nebrino matches every component of your SBOMs that has a package URL or CPE against public vulnerability databases every day – including versions shipped long ago.

    • CycloneDX (JSON, XML) and SPDX (JSON, tag-value, 3.0 JSON-LD)
    • Alert by email or webhook for actively exploited vulnerabilities (CISA KEV, EUVD)
    • Record per finding whether your product is affected (VEX)
  3. 03 · Art. 14 CRA · Section 32 BSIG

    Report

    Cyber Resilience Act and NIS2 in one reporting case

    Nebrino starts the deadlines from awareness, prepares every notification with the fields of the ENISA Single Reporting Platform and reminds the person responsible and their deputy. If your company is a NIS2 entity in Germany, the notifications to the BSI run in the same case.

    • Competent CSIRT under Art. 14(7)
    • Early warning 24 h, notification 72 h, final report
    • Emergency sheet and deadlines as a calendar file
  4. 04 · Annex I · II · V · VII

    Evidence

    One body of evidence per product

    Annex I requirements as a checklist with evidence, risk assessment and documents generated from your input – in one place, with an audit log, exportable as an evidence package per product.

    • Annex I Part I (product) and Part II (vulnerability handling)
    • Technical documentation (Annex VII), EU declaration of conformity (Annex V), information for users (Annex II)
    • Hash-chained log of every change
For developersOne file. Every release checked.
For developers

One file. Every release checked.

Generate the SBOM
Syft · cdxgen · Yocto (create-spdx) · Zephyr (west spdx)
Formats
CycloneDX 1.4–1.7 (JSON, XML) · SPDX 2.2/2.3 (JSON, tag-value) · SPDX 3.0 (JSON-LD)
Upload
REST API with token · Templates for GitHub Actions, GitLab CI, Azure DevOps, Jenkins and shell · Release gate for actively exploited vulnerabilities
Pass on
Alert webhook (e.g. Teams, Slack) · CSAF, OpenVEX and CycloneDX VEX · Share links for customers

API and CI templates from the Professional plan.

.github/workflows/nebrino-sbom.yml
# Nebrino SBOM upload - GitHub Actions
# Copy to .github/workflows/nebrino-sbom.yml.
# Secret NEBRINO_TOKEN (Settings > Secrets and variables > Actions): API token with sbom:write and findings:read.
name: Nebrino SBOM

on:
  push:
    branches: [main]
    tags: ["v*"]
  workflow_dispatch:

permissions:
  contents: read

jobs:
  sbom:
    runs-on: ubuntu-latest
    timeout-minutes: 20
    env:
      NEBRINO_URL: ${{ vars.NEBRINO_URL }}
      NEBRINO_PRODUCT_ID: ${{ vars.NEBRINO_PRODUCT_ID }}
      # none | exploited | critical - see the README
      NEBRINO_FAIL_ON: exploited
      NEBRINO_SBOM: sbom.cdx.json
    steps:
      - uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1
        with:
          persist-credentials: false

      # CycloneDX SBOM with Syft. For npm projects alternatively:
      #   - run: npx --yes @cyclonedx/cyclonedx-npm@6.0.1 --output-file sbom.cdx.json
      - name: Generate SBOM
        uses: anchore/sbom-action@3ad7283483fc7af8ff2b4ea19663c2d5ca935e26 # v0.24.2
        with:
          path: .
          format: cyclonedx-json
          output-file: sbom.cdx.json
          syft-version: v1.52.0
          upload-artifact: false
          upload-release-assets: false

      - name: Upload SBOM to Nebrino
        shell: sh
        env:
          NEBRINO_TOKEN: ${{ secrets.NEBRINO_TOKEN }}
        run: |

… shortened – the button copies the complete template

Trust

A security tool has to be secure itself.

  • Servers in Germany

    Hetzner, Falkenstein and Nuremberg

  • ISO/IEC 27001 data centres

    Certificate of our host Hetzner

  • No AI services

    Your data trains no language model

  • Two-factor and single sign-on

    TOTP for every account, SAML per domain

  • Security contact per RFC 9116

    security.txt, written replies

  • Daily encrypted backups

    Export and deletion at any time

Pricing

Transparent pricing. No consulting days.

Pilot phase

Become a pilot customer.

Nebrino is new and is currently being trialled with the first manufacturers. All features described are available – whatever is still missing, we build together with you.

  • All features free of charge for 60 days – sign up by 31 December 2026, while pilot seats last
  • 20% discount on the first contract year
  • Direct line to us instead of a ticket system
  • Help with setup and your first SBOM
  • Your requirements feed directly into the roadmap

Starter

129 € / month

up to 5 products

For small manufacturers who want to get the reporting obligations under control first.

ProfessionalRecommended

349 € / month

15 products included

For manufacturers who must implement all requirements of the Cyber Resilience Act by December 2027.

Business

790 € / month

up to 50 products

For product portfolios with several teams and suppliers.

Net, billed annually.

See pricing →
Questions

Frequently asked questions

Does the Cyber Resilience Act apply to my company?

If you place hardware or software products with digital elements on the EU market, very likely yes – from apps and desktop software to firmware, IoT devices and machine controls. Pure SaaS offerings without an associated product are generally not covered by the Cyber Resilience Act. The free CRA check gives you an initial assessment within a few minutes.

We are based outside the EU – does the Cyber Resilience Act apply to us?

Yes. The Cyber Resilience Act attaches to the product, not to where the manufacturer is established: anyone who markets products with digital elements in the EU has the same obligations, including the reporting obligations. Without a main establishment in the EU, the competent CSIRT is determined by your authorised representative, importer, distributor or where most of your users are (Art. 14(7)). From 11 December 2027, importers check your documents before placing products on the market (Art. 19). More in the guide “Manufacturers outside the EU”; the free CSIRT finder determines the competent CSIRT.

What do I have to do since 11 September 2026?

You report actively exploited vulnerabilities in your products and severe incidents via the ENISA Single Reporting Platform: an early warning notification without undue delay and in any event within 24 hours, a notification without undue delay and in any event within 72 hours and a final report no later than 14 days after a corrective or mitigating measure is available (vulnerability) or one month after the notification (incident). You inform impacted users in a timely manner after becoming aware (Art. 14(8)). This also applies to products already on the market.

Do I have to report every vulnerability in the KEV catalogue?

No. An entry in the CISA KEV catalogue shows that a vulnerability is being exploited somewhere. According to the Commission guidelines (published in the Official Journal on 17 Nov 2026, not binding), the reporting obligation only applies once you know with reasonable certainty that it is being exploited in your product. Nebrino alerts you to every KEV match so you can check this quickly – and records what is affected and what is not.

Does Nebrino submit the notifications for me?

No. The ENISA Single Reporting Platform currently (as of 10/2026) offers no API, so you submit there yourself. Nebrino prepares every notification with the fields of the platform, calculates the deadlines, reminds your team and documents the time and reference number of the submission.

We are also a NIS2 entity – does Nebrino help with that?

With reporting, yes: if your company is an important or essential entity under the German BSI Act (BSIG), the notifications to the BSI run in the same reporting case – initial notification within 24 hours, notification within 72 hours, final notification one month later – with their own deadlines and reminders. SBOM monitoring, the supplier portal and coordinated vulnerability disclosure also cover part of the measures under Section 30 BSIG: supply chain security and vulnerability handling. Nebrino is not a full information security management system – you keep documenting backups, business continuity, access control and management training where you do today. The guide “NIS 2 and the Cyber Resilience Act: what applies to manufacturers?” gives an overview.

Ready?

Be prepared before things go wrong.

Request a pilot seat. Once approved, add your first product – from then on, Nebrino checks every day and alerts you when it matters.