Features for the Cyber Resilience Act
From classifying your products and monitoring SBOMs every day to reporting on time: how Nebrino maps the obligations of the Cyber Resilience Act, and what stays with you.
01Platform
The key obligations under the Cyber Resilience Act in one place.
Instead of spreadsheets and inboxes.
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)
- OSV by package identifier, NVD by CPE for firmware and libraries without a package manager
- Alert by email or webhook for actively exploited vulnerabilities (CISA KEV, EUVD), EPSS per finding
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.
- Default, Class I/II, critical
- Open-source software stewards
- Support period per version
From the alert to informing users: Nebrino starts the deadlines, prepares every notification with the fields of the ENISA Single Reporting Platform and logs every step immutably. If your company is a NIS2 entity in Germany, the notifications to the BSI run in the same reporting case.
- Early warning 24 h, notification 72 h, final report – under the Cyber Resilience Act and Section 32 BSIG side by side
- Reporting person, deputy and escalation before the deadline
- Submissions with time and reference number as evidence
All essential cybersecurity requirements as a checklist: record the status, describe the implementation, upload evidence.
- Part I (product) and Part II (vulnerability handling)
- Risk assessment per product with matrix and residual risk
- Notice when your assessment contradicts the platform data
Product data, checklist and SBOMs turn into the documents market surveillance authorities and customers want to see – to review, print and save as PDF.
- Technical documentation (Annex VII)
- EU declaration of conformity (Annex V) and information for users (Annex II)
- Take over details between variants of a product family
A public page with your coordinated vulnerability disclosure policy and a reporting form – the single point of contact required by Annex I Part II.
- security.txt according to RFC 9116
- Inbox with status and product assignment
- Protection against spam and abuse
For the whole team
Unlimited users with roles, several organisations per account, deadline reminders to everyone and a designated deputy – so a notification never fails because one person is on holiday.
02Division of tasks
What Nebrino takes on.
And what stays with you.
Nebrino takes routine, deadlines and paperwork off your hands. Responsibility as the manufacturer stays with you – that is how the Cyber Resilience Act is designed.
Nebrino takes on
- Checking SBOMs every day against OSV, NVD, CISA KEV and EUVD and alerting you to actively exploited vulnerabilities
- Calculating reporting deadlines under the Cyber Resilience Act and NIS2 in one case, sending reminders and escalating to the person responsible and their deputy
- Preparing report texts along the fields of the ENISA Single Reporting Platform, with an emergency sheet and calendar file
- Classifying products against Annexes III and IV (as a reasoned proposal), assessing risks and evidencing the requirements of Annex I point by point
- Receiving reports from security researchers through the CVD portal and publishing security advisories as CSAF or VEX
- Generating the technical documentation, declaration of conformity and user information from your input, archiving released versions and sharing them with customers via share link
- Logging evidence, assessments and every change with time and person, and reminding you of the end of the support period of your products
Stays with you
- Submitting the notification yourself via the ENISA platform – Nebrino does not submit anything for you
- Deciding whether a case must be reported – the check questions in Nebrino help
- Drawing up the declaration of conformity and standing behind it as the manufacturer
- Developing and providing security updates
- Involving a notified body where the Cyber Resilience Act requires it
- Legal advice in individual cases – Nebrino does not replace it
03Integration
Fits into your build.
No manual work at release time.
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.Guide: SBOM from the CI/CD pipeline
04Why Nebrino
A security tool has to be secure itself.
And easy to understand.
Every obligation with its source
Deadlines, requirements and guides refer to the article of the Regulation or the Commission guidelines – verifiable rather than taken on trust.
Your vulnerabilities stay yours
Public databases (OSV, NVD) only receive component names and versions – not which manufacturer or product they belong to.
Strict tenant isolation
Each organisation only sees its own data. The isolation is enforced in the database itself and tested automatically with every change.
Evidence that holds up
Submitted notifications and the log of every reporting case are stored immutably – with the time and the person who acted. The change log is protected against later tampering by a hash chain.
Built for SMEs
No consulting days, no enterprise rollout: once approved, add a product and upload an SBOM – on the same day.
In English and German
Interface and document templates in English and German; generated documents also in French, Italian, Spanish, Dutch, Polish and Czech, the EU declaration of conformity in all other official EU languages. All subprocessors openly listed (in German).
Details: Subprocessors (German) · Privacy policy · Security contact
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.
Cancellable at the end of the annual term