Glossary
Cyber Resilience Act glossary
Terms and abbreviations around the Cyber Resilience Act and Nebrino – briefly explained, with references.
139 terms
- Actively exploited vulnerability
A vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without permission of the system owner. It becomes reportable once you become aware of exploitation in your product – an entry in the KEV catalogue or a flag in the EUVD alone is not enough.
ReportingReference: Art. 3(42), Art. 14(1)See also:Reporting obligation,Becoming aware,KEV,EUVD,Vulnerability
- Annex IEssential cybersecurity requirements
The core of the Cyber Resilience Act. Part I covers the product's properties (including no known exploitable vulnerabilities, secure by default configuration, access protection, updates); its requirements may be justified as not applicable based on the risk assessment. Part II covers vulnerability handling (including SBOM, remediation, testing, CVD policy, free security updates) and always applies. Mandatory from 11 December 2027.
Law & obligationsReference: Annex I Parts I and IISee also:Cybersecurity risk assessment,SBOM,CVD policy,Security update,Checklist
- Annex IIInformation and instructions to the user
Specifies what information must accompany the product – including the manufacturer and the contact point for vulnerability reports, the intended purpose, the end of the support period and instructions for secure installation, use and updates. Nebrino generates an “information for users” document from it.
Law & obligationsReference: Art. 13(18), Annex IISee also:Support period,Technical documentation
- Annex IIIImportant products with digital elements
List of important products, divided into Class I (e.g. password managers, VPN products, browsers) and Class II (e.g. firewalls, hypervisors). What counts is the product's core functionality. The technical descriptions of the categories are set out in Implementing Regulation (EU) 2025/2392.
Law & obligationsReference: Art. 7, Annex IIISee also:Class I,Class II,Core functionality,Annex IV
- Annex IVCritical products with digital elements
List of critical products: hardware devices with security boxes, smart meter gateways and devices for advanced security purposes, and smartcards or similar devices including secure elements.
Law & obligationsReference: Art. 8, Annex IVSee also:Critical product,EUCC,Annex III
- Annex VEU declaration of conformity
Specifies the content of the EU declaration of conformity, including the product, the manufacturer, the standards or specifications applied and, where applicable, the notified body involved. Annex VI contains a simplified version that refers to the full text online.
Law & obligationsReference: Art. 28, Annex V, Annex VISee also:EU declaration of conformity,CE marking
- Annex VIIContent of the technical documentation
Specifies the minimum content of the technical documentation – including the product description, design and development, risk assessment, support period, standards applied, test reports and the EU declaration of conformity. Micro and small enterprises are to be able to use a simplified form for it.
Law & obligationsReference: Art. 31, Annex VIISee also:Technical documentation,Cybersecurity risk assessment,SBOM
- Annex VIIIConformity assessment procedures
Describes the procedures used to demonstrate conformity: Module A (internal control), Module B (EU-type examination) with Module C (conformity to type) and Module H (full quality assurance). Which procedure is permitted depends on the product's class.
Law & obligationsReference: Art. 32, Annex VIIISee also:Conformity assessment,Module A,Module B,Module C,Module H
- APIApplication programming interface
An interface through which programs communicate with each other. Via the Nebrino API your build pipeline uploads SBOMs automatically and queries findings; it is included from the Professional plan.
Technology & securitySee also:API key (token),CI/CD,JSON
- API key (token)
A secret key with which a program authenticates to the API. In Nebrino each key is limited to one organisation and the selected permissions, is shown only once and can be revoked at any time; store it as a secret in GitHub or GitLab.
Technology & security- Authorised representative
A person established in the EU who has received a written mandate from a manufacturer to act on its behalf in relation to specified tasks – for example to be available to market surveillance authorities and keep documents ready. The manufacturer remains responsible for its product.
Law & obligationsReference: Art. 3(15), Art. 18
- Becoming aware
The point from which the reporting deadlines run. According to the Commission's guidance (published in the Official Journal on 17 Nov 2026, not binding), this is the moment you know with reasonable certainty that a vulnerability is being exploited in your product or that a severe incident has occurred – not the first suspicion. In Nebrino this time cannot be changed once a reporting case has been created.
ReportingReference: Art. 14(2) and (4)See also:Early warning notification,Reporting case,Reporting obligation
- BSIGerman Federal Office for Information Security
Germany's federal cybersecurity authority. Its CERT-Bund is Germany's CSIRT designated as coordinator for the Cyber Resilience Act – according to ENISA's list of coordinating CSIRTs.
Organisations & bodiesSee also:CSIRT,Coordinating CSIRT
- BSI-Portal
The BSI's portal for NIS2 entities: registration (with an ELSTER organisation certificate) and reporting of significant incidents. It is not the same as ENISA's Single Reporting Platform, through which notifications under Article 14 CRA are submitted.
ReportingReference: Sections 32, 33 BSIGSee also:Significant incident,SRP,BSI,BSIG
- BSIGGerman BSI Act
German act transposing NIS2 (new version, BGBl. 2025 I No. 301; according to the BSI, the obligations have applied since 6 December 2025). Among other things, it defines which companies are important or essential entities (Section 28), which security measures they must take (Section 30), how they report significant incidents (Section 32) and that they must register with the BSI (Section 33).
Law & obligationsReference: BSIG, Sections 28–33See also:NIS2,Important and essential entity,Significant incident,BSI-Portal,BSI
- CE marking
The mark by which the manufacturer declares that the product meets all applicable EU requirements – from 11 December 2027 including those of the Cyber Resilience Act. It is affixed visibly, legibly and indelibly to the product before it is placed on the market; where the nature of the product does not allow this, to the packaging and the accompanying EU declaration of conformity. For software it appears on the EU declaration of conformity or on the website accompanying the product. It may be smaller than 5 mm as long as it remains visible and legible. The identification number of the notified body follows only where that body is involved in a procedure based on full quality assurance (module H). Open-source software stewards do not need CE marking.
Standards & conformityReference: Art. 29, Art. 30- CEN/CENELECEuropean Committee for Standardization / European Committee for Electrotechnical Standardization
European standardisation organisations that develop, among other things, the horizontal EN 40000 series for the Cyber Resilience Act (joint committee CEN/CLC/JTC 13). You obtain standards through the national standards bodies, in Germany for example via DIN Media.
Organisations & bodiesSee also:ETSI,EN 40000,M/606,Harmonised standard
- Checklist
Nebrino has two kinds of checklist: per product, the Annex I requirements with status (open, in progress, fulfilled, justified as not applicable) and evidence; and per standard applied, a checklist you work through item by item. The check questions are our own wording and do not replace the text of the standard.
Nebrino featuresSee also:Annex I,Evidence,Standards radar
- CI/CDContinuous integration / continuous delivery
An automated build, test and delivery pipeline, for example with GitHub Actions or GitLab CI. Nebrino can be integrated there: the SBOM is uploaded with every release, and with fail_on the build fails if actively exploited or critical, unassessed vulnerabilities are found.
Technology & securitySee also:API,API key (token),SBOM
- CISACybersecurity and Infrastructure Security Agency (US)
The US federal agency for cyber and infrastructure security. Relevant for Nebrino is its KEV catalogue of actively exploited vulnerabilities; it has no role under the Cyber Resilience Act.
Organisations & bodiesSee also:KEV
- Class IImportant product of Class I
Important products under Annex III Class I, e.g. identity management, browsers, password managers, anti-malware software or VPN products. Module A is only permitted if you fully apply a harmonised standard cited in the Official Journal, common specifications or a European cybersecurity certification (at least assurance level ‘substantial’); otherwise a notified body is required (Module B + C or H).
Law & obligationsReference: Annex III, Art. 32(2)See also:Annex III,Harmonised standard,Notified body,Module A,Module B
- Class IIImportant product of Class II
Important products under Annex III Class II, e.g. hypervisors and container runtime systems, firewalls and intrusion detection or prevention systems. Conformity must be demonstrated by a notified body (Module B + C or Module H) or – where a suitable scheme exists – by a European cybersecurity certification (at least ‘substantial’). Exception: FOSS under Art. 32(5).
Law & obligationsReference: Annex III, Art. 32(3)See also:Annex III,Notified body,Module B,Module H,FOSS
- Client (consultant mode)
For consultancies: each customer is a separate organisation (client) in Nebrino with its own plan and strictly separated data. The client overview shows open deadlines and alerts across all clients. The reporting obligation lies with the manufacturer – as a consultant you prepare notifications, which are submitted on behalf of the client.
Nebrino featuresSee also:Manufacturer,Reporting case,Roles (owner, admin, member)
- Common specification
Technical specifications that the European Commission can lay down by implementing act, for example where no suitable harmonised standard exists. Applying them also gives a presumption of conformity; whether any exist for the Cyber Resilience Act is shown in the standards radar.
Standards & conformityReference: Art. 27(2)- Component
A building block of a product, e.g. a library, package, module or firmware. In the SBOM each component is listed with name, version and ideally an identifier (purl or CPE) so it can be matched against vulnerability databases. Components you supply to other manufacturers are products under the Cyber Resilience Act in their own right.
Vulnerabilities & SBOMSee also:SBOM,Dependency,purl,CPE,Third-party components (supply chain)
- Conformity assessment
Demonstrating that a product meets the essential requirements before it is placed on the market. The procedure depends on the class: default products via internal control (Module A), important and critical products usually with a notified body or via certification. It ends with the EU declaration of conformity and CE marking. Mandatory from 11 December 2027.
Standards & conformityReference: Art. 32, Annex VIIISee also:Module A,Module B,Module H,Notified body,CE marking
- Coordinating CSIRTCSIRT designated as coordinator
The CSIRT that receives and coordinates your notifications under Art. 14. This is usually the Member State of your main establishment in the EU (where decisions on the cybersecurity of your products are predominantly taken); without an establishment, the state of the authorised representative, then of the importer, then of the distributor, otherwise the one with the most users – in that last case, later notifications may go to the same CSIRT that was notified first. A wrong choice can delay processing.
ReportingReference: Art. 14(7)See also:CSIRT,SRP,Authorised representative
- Core functionality
A product's main function, which determines its classification under Annex III or IV. If a product only contains such a function as an integrated part (e.g. a device with a built-in browser), it generally remains a default product.
Law & obligationsReference: Art. 7(1)See also:Annex III,Annex IV,Default product
- Corrective or mitigating measure
A measure that fixes a vulnerability (e.g. a security update) or reduces its risk (e.g. a workaround or changed configuration). As soon as such a measure is available, the 14-day deadline for the final report on a vulnerability starts; in Nebrino you record this time in the reporting case.
ReportingReference: Art. 14(2)(c)See also:Final report,Security update,Workaround,Patch
- CPECommon Platform Enumeration
A naming scheme for vendors, products and versions used by the NVD among others, e.g. cpe:2.3:a:vendor:product:1.0:… (further fields follow). Components without a purl – such as in firmware without a package manager – are matched by Nebrino via the NVD using CPE; this takes a little longer.
Vulnerabilities & SBOM- CRACyber Resilience Act – Regulation (EU) 2024/2847
EU regulation setting mandatory cybersecurity requirements for products with digital elements across their whole lifecycle. It applies directly in all Member States and entered into force on 10 December 2024. The reporting obligations under Art. 14 have applied since 11 September 2026; all other obligations (including Annex I, conformity assessment and CE marking) apply from 11 December 2027.
Law & obligationsReference: Regulation (EU) 2024/2847See also:Product with digital elements,Manufacturer,Reporting obligation,Annex I
- Critical product
A product under Annex IV. Where a delegated act under Art. 8(1) requires it, a European cybersecurity certification of at least assurance level ‘substantial’ is mandatory; otherwise the procedures for Class II apply. The FOSS relief under Art. 32(5) does not apply here.
Law & obligationsReference: Art. 8, Art. 32(4), Annex IV- CSAFCommon Security Advisory Framework
OASIS standard (version 2.0) for machine-readable security advisories. The “CSAF VEX” profile carries VEX statements; Nebrino exports your assessments per product as a CSAF VEX document – for customers, CSIRTs and authorities, for example.
Vulnerabilities & SBOMSee also:VEX,Security advisory,JSON
- CSIRTComputer Security Incident Response Team
A Member State team that handles and coordinates security incidents; CSIRTs are designated under the NIS2 Directive. For the Cyber Resilience Act, each Member State has designated one CSIRT as coordinator – in Germany CERT-Bund at the BSI.
Organisations & bodiesSee also:Coordinating CSIRT,ENISA,BSI,NIS2
- CVDCoordinated vulnerability disclosure
A process in which security researchers first report a vulnerability they have found to the manufacturer, and publication is coordinated once a remedy is available. The Cyber Resilience Act requires a policy and a contact address for reports; in Nebrino, the CVD portal covers this.
Vulnerabilities & SBOMReference: Annex I Part II points 5 and 6See also:CVD policy,security.txt,CVD portal,ISO/IEC 29147
- CVD policy
A public policy on how you receive and handle vulnerability reports: how to report, what reporters can expect, timelines for response and publication. The Cyber Resilience Act requires you to put in place and enforce such a policy; Nebrino provides a template.
Vulnerabilities & SBOMReference: Annex I Part II point 5See also:CVD,security.txt,CVD portal
- CVD portal
A public reporting page in Nebrino through which security researchers report vulnerabilities in your products – with its own address, your CVD policy and an automatically provided security.txt. Incoming reports appear under “Security reports”. Included from the Professional plan.
Nebrino featuresReference: Annex I Part II points 5 and 6See also:CVD,CVD policy,security.txt
- CVECommon Vulnerabilities and Exposures
A worldwide catalogue of publicly known vulnerabilities with unique identifiers such as CVE-2021-44228 (Log4Shell). Identifiers are assigned by CVE Numbering Authorities (CNAs) within the CVE Program run by MITRE. The CVE ID is an optional field in the reporting case.
Vulnerabilities & SBOMSee also:Vulnerability,EUVD,NVD,CVSS
- CVSSCommon Vulnerability Scoring System
An open standard by FIRST that expresses the severity of a vulnerability as a score from 0.0 to 10.0, calculated from a vector (e.g. attack vector, complexity, impact). The base score says nothing about whether the vulnerability is exploitable or being exploited in your product.
Vulnerabilities & SBOM- Cybersecurity ActRegulation (EU) 2019/881
EU regulation that sets out ENISA's mandate and establishes the framework for European cybersecurity certification, such as the EUCC scheme.
Standards & conformityReference: Regulation (EU) 2019/881- Cybersecurity risk assessment
A documented assessment of a product's cybersecurity risks that guides planning, design, development, production, delivery and maintenance. It determines how the requirements of Annex I Part I are implemented or why one of them does not apply. It is part of the technical documentation.
Law & obligationsReference: Art. 13(2)–(3)See also:Annex I,Technical documentation
- Default product
A product with digital elements that is listed neither in Annex III nor in Annex IV – this applies to most products. You demonstrate conformity yourself through internal control (Module A), without a notified body.
Law & obligationsReference: Art. 32(1)See also:Module A,Class I,Core functionality
- Demo sandbox
A separate organisation with sample data (connected device, industrial control or software) in which you can try Nebrino safely – with a running 24-hour deadline, SBOM findings, VEX, Annex I, documents, supply chain and standards. Nothing is sent from the sandbox; it is deleted after 30 days without use.
Nebrino featuresSee also:Pilot programme,Trial
- Dependency
A component that a product or another component needs in order to work. You include direct dependencies yourself; transitive ones come in through them. Under Annex I the SBOM must cover at least the top-level (direct) dependencies; vulnerabilities, however, are often found in transitive ones.
Vulnerabilities & SBOMReference: Annex I Part II point 1- Distributor
A person in the supply chain, other than the manufacturer or importer, who makes a product available on the market without affecting its properties. Distributors act with due care and check, among other things, the CE marking and manufacturer details.
Law & obligationsReference: Art. 3(17), Art. 20See also:Economic operator,Importer,Making available on the market
- DNS TXT record
A text entry in your domain's DNS settings. Nebrino uses it so you can prove that you own an email domain before SSO applies to that domain.
Technology & security- DPAData processing agreement
Agreement under Art. 28 GDPR required when a service provider processes personal data on your behalf. Nebrino, for example, processes contact details of your suppliers on your behalf; you receive the DPA with the contract, and the subprocessors are listed publicly.
Law & obligationsReference: Art. 28 GDPR
- Early warning notification
First stage of reporting: without undue delay and within 24 hours of becoming aware at the latest, with initial information – such as, where known, the Member States in which the product has been made available. Micro and small enterprises are not fined for a missed early warning notification.
ReportingReference: Art. 14(2)(a), (4)(a)See also:Notification (72 h),Becoming aware,SRP,Micro and small enterprises
- Economic operator
Collective term for manufacturers, authorised representatives, importers, distributors and other persons subject to obligations under the Cyber Resilience Act. Which obligations apply depends on the role; in Nebrino you set your company's role under Settings.
Law & obligationsReference: Art. 3(12)See also:Manufacturer,Authorised representative,Importer,Distributor
- EN 18031Standards series for the Radio Equipment Directive (RED)
Standards EN 18031-1, -2 and -3 with security requirements for internet-connected radio equipment (network protection, privacy, fraud protection) under Delegated Regulation (EU) 2022/30 to the Radio Equipment Directive (RED, Directive 2014/53/EU). They are cited in the Official Journal under the RED (with restrictions), not under the Cyber Resilience Act. Delegated Regulation (EU) 2022/30 has applied since 1 Aug 2025 and is repealed with effect from 11 Dec 2027 (Delegated Regulation (EU) 2026/339) – from then on the Cyber Resilience Act applies to this equipment.
Standards & conformityReference: Implementing Decision (EU) 2025/138- EN 40000Series “Cybersecurity requirements for products with digital elements”
Horizontal CEN/CENELEC standards series for the Cyber Resilience Act: part 1-1 vocabulary, 1-2 principles, risk management and lifecycle, 1-3 vulnerability handling, 1-4 generic security requirements. The parts are at various draft and voting stages; the standards radar shows status and citation.
Standards & conformitySee also:Harmonised standard,Horizontal and vertical standards,CEN/CENELEC,Standards radar
- ENISAEuropean Union Agency for Cybersecurity
The EU agency for cybersecurity. For the Cyber Resilience Act it operates the Single Reporting Platform (SRP), through which notifications under Art. 14 go simultaneously to the coordinating CSIRT and to ENISA, as well as the European Vulnerability Database EUVD.
Organisations & bodiesSee also:SRP,EUVD,CSIRT,Cybersecurity Act
- ETSIEuropean Telecommunications Standards Institute
The European standardisation organisation for information and communication technology. For the Cyber Resilience Act it develops the vertical standards for product categories from Annexes III and IV; it is also known for ETSI EN 303 645 for consumer IoT.
Organisations & bodiesSee also:CEN/CENELEC,ETSI EN 303 645,Horizontal and vertical standards
- ETSI EN 303 645
European standard with baseline cybersecurity requirements for consumer IoT, including no universal default passwords, updates and a way to report vulnerabilities. It is an established state-of-the-art standard, but not a harmonised standard cited under the Cyber Resilience Act.
Standards & conformity- EU declaration of conformity
The declaration by which the manufacturer confirms that the essential requirements are met and assumes responsibility for this. Content under Annex V; it must be translated into the language(s) required by the Member States where the product is made available and kept for at least ten years or for the support period, whichever is longer.
Standards & conformityReference: Art. 28, Annex V, Art. 13(13)See also:Annex V,CE marking,Technical documentation
- EUCCEuropean Common Criteria-based cybersecurity certification scheme
European certification scheme based on the Common Criteria under the Cybersecurity Act (Implementing Regulation (EU) 2024/482). For critical products, a delegated act under Art. 8(1) can make such certification of at least assurance level ‘substantial’ mandatory. Certificates are issued by certification bodies under the Cybersecurity Act, not by notified bodies under the Cyber Resilience Act.
Standards & conformityReference: Art. 8(1), Implementing Regulation (EU) 2024/482See also:Critical product,Cybersecurity Act,Class II
- EUVDEuropean Vulnerability Database
The European vulnerability database operated by ENISA, with identifiers such as EUVD-2026-12345; it also refers to CVE IDs and flags actively exploited vulnerabilities. Nebrino checks findings against it daily; the EUVD ID is an optional field in the reporting case.
Vulnerabilities & SBOMSee also:ENISA,CVE,KEV,Actively exploited vulnerability
- Evidence
Proof that a requirement has been implemented – such as a test report, a concept or a screenshot. In Nebrino you upload evidence for requirements and standards checklists; it feeds into the technical documentation. Reporting logs and supplier requests also serve as evidence for market surveillance.
Nebrino featuresSee also:Checklist,Technical documentation,Market surveillance authority
- Exploit
Code or a technique that actually exploits a vulnerability. A publicly available exploit increases the risk considerably; under the Cyber Resilience Act, however, only actual exploitation in your product is reportable.
Vulnerabilities & SBOM
- Final report
The last stage of reporting. For an actively exploited vulnerability no later than 14 days after a corrective or mitigating measure is available – describing the vulnerability including its severity and impact, information on malicious actors (where available) and details of the security update. For a severe incident no later than one month after the incident notification – with a description, severity and impact, the type of threat or root cause and the mitigating measures applied.
ReportingReference: Art. 14(2)(c), (4)(c)See also:Corrective or mitigating measure,Notification (72 h),Severity
- Finding
A match found when checking an SBOM component against vulnerability databases (OSV, NVD, CISA KEV, EUVD). You assess each finding using VEX – affected, not affected, fixed or under investigation. “Rescan” fetches the current status immediately; otherwise Nebrino checks daily.
Nebrino features- Fine
Infringements of the essential requirements in Annex I or of the obligations under Art. 13 and 14 can be fined up to €15 million or up to 2.5% of worldwide annual turnover – whichever is higher. Infringements of other obligations – such as those of importers and distributors, of notified bodies, or concerning the declaration of conformity, technical documentation and CE marking – fall under the tier of up to €10 million or 2%; supplying incorrect, incomplete or misleading information to authorities and notified bodies under the tier of up to €5 million or 1%. Micro and small enterprises are not fined for a missed 24-hour early warning notification, and open-source software stewards are not fined at all.
Law & obligationsReference: Art. 64(2)–(4), (10)See also:Reporting obligation,Micro and small enterprises,Open-source software steward
- FOSSFree and open-source software
Software whose source code is openly shared and which is made available under a licence permitting its use, modification and redistribution. If it is not made available in the course of a commercial activity, it is outside the Cyber Resilience Act; anyone monetising it (e.g. through mandatory support or data monetisation) counts as a manufacturer. For important products under Annex III, FOSS manufacturers may use Module A if they make the technical documentation publicly available – but not for critical products under Annex IV.
Law & obligationsReference: Art. 3, Art. 32(5)See also:Open-source software steward,Module A,Annex III,Technical documentation
- FprENFinal draft European standard
Final draft of a European standard in the formal vote. After a successful vote it is published as an EN; the presumption of conformity only arises once it is cited in the Official Journal.
Standards & conformitySee also:prEN,hEN,Official Journal of the EU (OJ)
- GDPRGeneral Data Protection Regulation (EU) 2016/679
EU regulation on the protection of personal data. It applies alongside the Cyber Resilience Act: if your product processes personal data you must comply with both – Annex I requires, among other things, data minimisation and protection of confidentiality.
Law & obligationsReference: Regulation (EU) 2016/679
- Harmonised standardhEN – harmonised European standard
A European standard developed by CEN, CENELEC or ETSI on a request from the European Commission (for the Cyber Resilience Act: standardisation request M/606). Once its reference is published in the Official Journal of the EU, applying it gives a presumption of conformity for the requirements it covers. The standards radar shows the current status.
Standards & conformityReference: Art. 27(1), Regulation (EU) No 1025/2012See also:hEN,Presumption of conformity,Official Journal of the EU (OJ),M/606,Standards radar
- hENHarmonised European standard
Short form for a harmonised European standard. A standard only becomes “harmonised” in the sense of the presumption of conformity once its reference is published in the Official Journal of the EU – a published EN alone is not enough.
Standards & conformitySee also:Harmonised standard,Official Journal of the EU (OJ),prEN
- Horizontal and vertical standards
Horizontal standards apply to all products (e.g. the EN 40000 series on vocabulary, risk management, vulnerability handling and generic security requirements). Vertical standards apply to specific product categories from Annexes III and IV (at ETSI the EN 304 6xx series). In addition there are established state-of-the-art standards such as IEC 62443.
Standards & conformitySee also:EN 40000,M/606,IEC 62443,Standards radar
- IdPIdentity provider
A central service that manages your employees' identities and confirms sign-ins, e.g. Microsoft Entra ID, Okta or Google Workspace. Signing out of Nebrino does not end the identity provider session.
Technology & security- IEC 62443
International standards series on the security of industrial automation and control systems (IACS). Part 4-1 describes a secure development lifecycle, part 4-2 technical security requirements for components. It is an important state-of-the-art standard and a basis for work under the standardisation request for the Cyber Resilience Act.
Standards & conformitySee also:Horizontal and vertical standards,ISO/IEC
- Important and essential entity
Companies to which NIS2 applies under the German BSIG. Manufacturers of the entity types listed in Annex 2 – such as electronics, electrical equipment, machinery, vehicles, medical devices – are important entities if they employ at least 50 people or have an annual turnover and balance sheet total of more than EUR 10 million each. Entity types in Annex 1 (e.g. cloud computing services, managed service providers) are essential entities from 250 employees or more than EUR 50 million turnover and EUR 43 million balance sheet total.
Law & obligationsReference: Section 28 BSIG, Annexes 1 and 2See also:NIS2,BSIG,Micro and small enterprises
- ImporterImporter
A person established in the EU who places on the market a product bearing the name or trademark of a person established outside the EU. Importers may only place compliant products on the market and mainly check the manufacturer's documents for this (including conformity assessment, technical documentation and CE marking).
Law & obligationsReference: Art. 3(16), Art. 19See also:Economic operator,Manufacturer,Distributor
- Information to users
After becoming aware, you inform the impacted users – and where appropriate all users – in a timely manner about the actively exploited vulnerability or severe incident and, where necessary, about measures they can take. This information is given outside the ENISA platform and has no fixed deadline in hours.
ReportingReference: Art. 14(8)See also:Reporting obligation,Security advisory,Corrective or mitigating measure
- Intermediate report
A report on relevant status updates that you only submit at the request of the coordinating CSIRT. It is not a fixed stage with its own deadline.
ReportingReference: Art. 14(6)See also:Coordinating CSIRT,Final report
- ISO/IECInternational Organization for Standardization / International Electrotechnical Commission
International standardisation organisations. Their standards (e.g. ISO/IEC 27001, 29147, 30111 or IEC 62443) are not harmonised standards under the Cyber Resilience Act but are considered state of the art and help with implementation.
Organisations & bodiesSee also:ISO/IEC 27001,IEC 62443,CEN/CENELEC
- ISO/IEC 27001
International standard for an organisation's information security management system (ISMS). It supports organisational processes but does not replace the product-level requirements of the Cyber Resilience Act.
Standards & conformity- ISO/IEC 29147
International standard on vulnerability disclosure: how manufacturers receive reports and publish security advisories. It fits the CVD requirements of Annex I Part II.
Standards & conformitySee also:CVD,ISO/IEC 30111,Security advisory
- ISO/IEC 30111
International standard for internal processes to handle reported vulnerabilities – investigation, prioritisation and remediation. It complements ISO/IEC 29147.
Standards & conformitySee also:ISO/IEC 29147,CVD
- KEVKnown Exploited Vulnerabilities (CISA catalogue)
A catalogue by the US agency CISA of vulnerabilities known to be exploited somewhere. Nebrino alerts you to every KEV match in your SBOMs so you can check quickly. A KEV entry alone does not trigger a reporting obligation – you must report once you become aware of exploitation in your product.
Vulnerabilities & SBOMSee also:CISA,Actively exploited vulnerability,Becoming aware,EUVD
- M/606European Commission standardisation request for the Cyber Resilience Act
The European Commission's request to CEN, CENELEC and ETSI to develop the harmonised standards for the Cyber Resilience Act – horizontal standards for all products and vertical standards for individual product categories from Annexes III and IV.
Standards & conformitySee also:Harmonised standard,Horizontal and vertical standards,CEN/CENELEC,ETSI
- Making available on the market
Any supply of a product for distribution or use on the EU market in the course of a commercial activity, whether in return for payment or free of charge. The first time is the placing on the market; every further supply, e.g. by distributors, is making available.
Law & obligationsReference: Art. 3See also:Placing on the market,Distributor
- Manufacturer
Anyone who develops or manufactures a product with digital elements – or has it designed, developed or manufactured – and markets it under their own name or trademark, whether for payment or free of charge. The manufacturer bears the main obligations: Annex I requirements, vulnerability handling, reporting, documentation and conformity assessment. Anyone placing a product on the market under their own name or modifying it substantially also takes on the manufacturer obligations.
Law & obligationsReference: Art. 3(13), Art. 13, 14See also:Economic operator,Substantial modification,Reporting obligation,Annex I
- Market surveillance authority
An authority of a Member State that checks whether products on the market meet the requirements. It can request documents such as the technical documentation or the SBOM and require corrective action, withdrawal or recall of a product.
Organisations & bodiesReference: Chapter V CRA, Regulation (EU) 2019/1020See also:Technical documentation,Fine,Evidence
- Micro and small enterprisesSMEs (small and medium-sized enterprises)
Small enterprises have fewer than 50 employees and at most €10 million in turnover or balance sheet total. The Cyber Resilience Act provides relief for them: no fines for a missed 24-hour early warning notification and a simplified form for the technical documentation. All other obligations still apply to them.
Law & obligationsReference: Art. 64(10)(a), Art. 33(5)See also:Fine,Early warning notification,Technical documentation
- Module AInternal control (self-assessment)
A procedure in which the manufacturer checks and documents conformity itself, without a third-party body. Permitted for default products; for Class I only when fully applying a harmonised standard cited in the Official Journal, common specifications or a European cybersecurity certification (at least ‘substantial’); and for FOSS of Classes I and II with publicly available technical documentation.
Standards & conformityReference: Art. 32(1), (2) and (5), Annex VIIISee also:Default product,Class I,FOSS,Harmonised standard
- Module BEU-type examination
A notified body examines the technical design and development of a product type as well as the vulnerability handling processes and, if successful, issues an EU-type examination certificate. Module B is always combined with Module C.
Standards & conformityReference: Annex VIIISee also:Module C,Notified body,Class I,Class II
- Module CConformity to type based on internal production control
Complements Module B: through its production process, the manufacturer ensures that each product conforms to the examined type and declares this in the EU declaration of conformity.
Standards & conformityReference: Annex VIIISee also:Module B,EU declaration of conformity
- Module HConformity based on full quality assurance
A notified body assesses and monitors the manufacturer's quality system for design, production and vulnerability handling instead of examining each product type individually. An alternative to Module B + C for Class I, Class II and – unless certification is mandatory – critical products.
Standards & conformityReference: Annex VIIISee also:Module B,Notified body,ISO/IEC 27001
- NANDONew Approach Notified and Designated Organisations
The European Commission's public database of all notified bodies, their identification numbers and the legislation and modules for which they are notified. It is the authoritative source for whether a body is approved for the Cyber Resilience Act.
Organisations & bodiesSee also:Notified body
- NIS2NIS 2 Directive (EU) 2022/2555
EU directive on the cybersecurity of entities (companies and public bodies) in certain sectors and above a certain size; it is transposed into national law, in Germany by the new BSI Act (BSIG). The Cyber Resilience Act, by contrast, regulates products. Many manufacturers are subject to both – for example in mechanical engineering or electronics from 50 employees or more than EUR 10 million annual turnover and balance sheet total. Pure SaaS services without an associated product may fall under NIS2 rather than the Cyber Resilience Act. The CSIRTs that receive notifications under the Cyber Resilience Act are designated under NIS2.
Law & obligationsReference: Directive (EU) 2022/2555See also:CRA,BSIG,Important and essential entity,CSIRT,Remote data processing
- Notification (72 h)Vulnerability notification / incident notification
Second stage: without undue delay and within 72 hours of becoming aware at the latest. It contains general information about the product, the nature of the exploit or incident, the corrective or mitigating measures taken and measures users can take themselves, as well as an indication of how sensitive the information is.
ReportingReference: Art. 14(2)(b), (4)(b)See also:Early warning notification,Final report,Corrective or mitigating measure,PEC
- Notified bodyNotified conformity assessment body
An independent body that a Member State has notified to the European Commission for conformity assessments under the Cyber Resilience Act; it carries a four-digit identification number. It is required for Module B + C or Module H. Notifications under the Cyber Resilience Act have been possible since 11 June 2026; the NANDO database is authoritative.
Standards & conformityReference: Chapter IV CRASee also:NANDO,Module B,Module H,Conformity assessment
- Official Journal of the EU (OJ)
The EU's official publication for legal acts and notices. Crucial for standards: only once the reference of a harmonised standard is published in the Official Journal does applying it give a presumption of conformity. Nebrino monitors the Official Journal for new citations under the Cyber Resilience Act.
Standards & conformityReference: Art. 27(1)- Open-source software steward
A legal person, other than a manufacturer, that systematically provides sustained support for the development of specific free and open-source software intended for commercial activities – such as a foundation. Stewards need neither CE marking nor an EU declaration of conformity, but must put in place a cybersecurity policy and cooperate with market surveillance. No fines are imposed on stewards.
Law & obligationsReference: Art. 3(14), Art. 24, Art. 64(10)(b)See also:FOSS,Manufacturer,Fine
- OSVOpen Source Vulnerabilities (osv.dev)
An open database of vulnerabilities in open-source packages that aggregates entries from many ecosystems (e.g. npm, PyPI, Maven) and can be queried by package name and version. Nebrino checks components with a purl against OSV daily.
Vulnerabilities & SBOM
- Patch
A change to the code that fixes a bug or vulnerability; usually delivered as an update. For your product, a patch to a component may also be required – for instance by updating a library.
Vulnerabilities & SBOMSee also:Security update,Workaround,Corrective or mitigating measure
- PECParticular exceptional circumstances
Option in the vulnerability notification: at the manufacturer's request and under narrow conditions, the coordinating CSIRT can delay dissemination to ENISA, for example if the exploitation is likely to concern only the Member State of the coordinating CSIRT or dissemination would create an imminent high cybersecurity risk. Only possible in the notification (72 h).
ReportingReference: Art. 16(2)See also:Notification (72 h),Coordinating CSIRT,SRP
- Pilot programme
A limited offer during Nebrino's launch phase: participating organisations use all features free of charge for a set period and give feedback in return. Afterwards they choose a plan – with a pilot discount. Seats and sign-up deadline are shown on the pilot page.
Nebrino featuresSee also:Trial,Plans (Starter, Professional, Business),Demo sandbox
- Placing on the market
The first making available of a product on the EU market. From this point the product must meet the requirements applicable at that time; most obligations under the Cyber Resilience Act are linked to it.
Law & obligationsReference: Art. 3See also:Making available on the market,Manufacturer,Importer
- Plans (Starter, Professional, Business)
Starter includes product inventory, SBOM monitoring, the reporting cockpit as well as VEX and CSAF. Professional adds the API, Annex I with evidence, documents, the CVD portal and the standards radar; Business also adds the supply chain module, the Trust Center, the four-eyes release, read-only access for auditors, the portfolio report and single sign-on. Reporting cases and deadlines always remain accessible.
Nebrino featuresSee also:Trial,Pilot programme,SSO,API
- prENDraft European standard
Draft of a European standard that is open for comment in the public enquiry. A prEN can offer guidance but gives no presumption of conformity; content and number may still change.
Standards & conformitySee also:FprEN,hEN,Presumption of conformity
- Presumption of conformityPresumption of conformity
Anyone applying a harmonised standard whose reference is published in the Official Journal is presumed to meet the requirements it covers – for the parts of the standard applied. For Module A with Class I, however, the standard must be applied in full. Drafts (prEN) and standards not cited give no presumption.
Standards & conformityReference: Art. 27(1), Art. 32(2)See also:Harmonised standard,Official Journal of the EU (OJ),Common specification,Class I
- Product with digital elementsPDE
A software or hardware product including its remote data processing solutions; this also covers software or hardware components placed on the market separately. It falls under the Cyber Resilience Act if its intended purpose or reasonably foreseeable use includes a direct or indirect data connection to a device or network – USB, Bluetooth, radio or a maintenance port count too. Pure cloud and SaaS services without an associated product are not such products.
Law & obligationsReference: Art. 2(1), Art. 3(1)See also:Remote data processing,Component,CRA
- purlPackage URL
A uniform identifier for a software package with ecosystem, name and version, e.g. pkg:npm/lodash@4.17.21. A purl allows a component to be matched reliably against databases such as OSV; Nebrino also uses the purl namespace to assign components to suppliers.
Vulnerabilities & SBOM
- Recital
Numbered statements of reasons at the beginning of an EU regulation. They do not create obligations themselves but help to interpret the articles – in the Cyber Resilience Act, for example, on open source or on relief for small enterprises.
Law & obligationsSee also:CRA
- Remote data processing
Data processing at a distance whose software is designed and developed by or under the responsibility of the manufacturer and without which the product could not perform one of its functions – such as the cloud back end of an app or a connected device. It is part of the product and must meet its requirements too.
Law & obligationsReference: Art. 3(2)See also:Product with digital elements,NIS2
- Reporting case
In Nebrino, the file for an actively exploited vulnerability or a severe incident. From the time of becoming aware, Nebrino calculates the deadlines, reminds all team members six hours beforehand and when a deadline is missed, prepares drafts with the fields of the ENISA platform and records every submission immutably.
Nebrino featuresSee also:Reporting obligation,Becoming aware,SRP,Early warning notification
- Reporting obligationReporting obligations under Art. 14 CRA
Manufacturers notify actively exploited vulnerabilities and severe incidents simultaneously to the coordinating CSIRT and ENISA via the Single Reporting Platform (SRP). Deadlines: early warning notification without undue delay and within 24 hours at the latest; notification without undue delay and within 72 hours at the latest; final report. The obligation has applied since 11 September 2026 – including for products already on the market.
ReportingReference: Art. 14See also:Actively exploited vulnerability,Severe incident,Early warning notification,Notification (72 h),Final report,SRP
- Retention period
The technical documentation and EU declaration of conformity must be kept for at least ten years after placing on the market or for the support period, whichever is longer, and made available to market surveillance authorities on request. Keep your documents in your own systems as well.
Standards & conformityReference: Art. 13(13)See also:Technical documentation,EU declaration of conformity,Support period
- Roles (owner, admin, member)
Permissions within an organisation's team: members work on products, findings and reporting cases. Admins additionally manage the team, settings and subscription. Owners can also appoint further owners.
Nebrino featuresSee also:Client (consultant mode),SSO
- SAMLSecurity Assertion Markup Language 2.0
An open standard through which an identity provider confirms to an application who is signing in. For set-up, both sides exchange metadata – for Nebrino the entity ID and ACS URL (reply URL) on one side and the identity provider's metadata URL on the other.
Technology & securitySee also:SSO,IdP,DNS TXT record
- SBOMSoftware bill of materials
A machine-readable list of a product's components with versions and dependencies. Annex I requires an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies; it is part of the technical documentation but does not have to be published. Nebrino checks your SBOMs (CycloneDX as JSON or XML, SPDX as JSON or tag-value) daily against vulnerability databases.
Vulnerabilities & SBOMReference: Annex I Part II point 1See also:CycloneDX,SPDX,Component,Dependency,Finding
- Security advisory
A manufacturer's publication on a vulnerability: affected products and versions, impact, severity and remediation. Under Annex I you publish information on fixed vulnerabilities once an update is available – in justified cases only after users have had the chance to apply it. CSAF makes this machine-readable.
Vulnerabilities & SBOMReference: Annex I Part II point 4See also:CSAF,CVD,Information to users
- Security update
An update that fixes a vulnerability. During the support period, available security updates must be disseminated without delay and free of charge, accompanied by advisory messages for users; where technically feasible separately from functionality updates and – where applicable – automatically.
Law & obligationsReference: Annex I Part II points 2, 7, 8See also:Support period,Patch,Vulnerability,Annex I
- security.txtFile according to RFC 9116
A text file at /.well-known/security.txt on your website stating how security researchers can report vulnerabilities (contact, policy, expiry date). Nebrino provides it automatically for your CVD portal.
Vulnerabilities & SBOMReference: RFC 9116See also:CVD,CVD policy,CVD portal
- Severe incidentSevere incident having an impact on the security of the product
An incident is severe if it negatively affects or is capable of negatively affecting the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or if it has led or is capable of leading to the introduction or execution of malicious code in the product or in a user's systems. It must be reported like an actively exploited vulnerability.
ReportingReference: Art. 14(3) and (5)See also:Reporting obligation,Early warning notification,Final report
- Severity
The rating of a finding. Nebrino derives it from the CVSS base score: critical from 9.0, high from 7.0, medium from 4.0, low below that; “unknown” without a score. For prioritisation, whether the vulnerability is actively exploited (KEV/EUVD) also counts.
Vulnerabilities & SBOM- Significant incident
Reporting trigger under NIS2 and the German BSIG: a security incident that has caused or can cause severe operational disruption of the services or financial losses for the entity, or that has affected or can affect other persons by causing considerable material or non-material damage. It is reported to the BSI and BBK: early warning within 24 hours, notification within 72 hours, final report one month after the notification. Not to be confused with the severe incident under the Cyber Resilience Act, which relates to the security of the product.
ReportingReference: Section 2 No. 11, Section 32 BSIGSee also:Severe incident,BSIG,BSI-Portal,NIS2
- SPDXSoftware Package Data Exchange
An open format from the Linux Foundation for SBOMs, originally developed for licence information and standardised as ISO/IEC 5962. Nebrino reads SPDX 2.2/2.3 as JSON and in tag-value format, and SPDX 3.0 as JSON-LD.
Vulnerabilities & SBOM- SRPSingle Reporting Platform (ENISA)
Platform operated by ENISA through which manufacturers submit notifications under Art. 14; they go simultaneously to the coordinating CSIRT and ENISA. The platform currently (as of 10/2026) offers no interface – Nebrino prepares the notifications with the platform's fields, and you submit them there.
ReportingReference: Art. 16See also:ENISA,Coordinating CSIRT,Reporting obligation,Reporting case
- SSOSingle sign-on
Signing in via your company's central identity provider instead of a separate password. Nebrino supports SSO via SAML in the Business plan; you can block password sign-in for your domains, while owners keep it as emergency access.
Technology & security- Standards radar
Nebrino's overview of the status of harmonised standards for the Cyber Resilience Act and established state-of-the-art standards – with status (draft, enquiry, vote, published, cited in the OJ), changes and the number of your products in which a standard is recorded. Included from the Professional plan.
Nebrino featuresSee also:Harmonised standard,Official Journal of the EU (OJ),Checklist
- Substantial modification
A change after placing on the market that affects compliance with the essential requirements in Annex I Part I or changes the intended purpose for which the product was assessed. Anyone carrying out a substantial modification – including importers, distributors or third parties – takes on the manufacturer obligations for the affected part, or for the whole product if the change affects its cybersecurity as a whole.
Law & obligationsReference: Art. 3, Art. 21, Art. 22See also:Manufacturer,Annex I,Conformity assessment
- Supply chain module
Nebrino feature for third-party components: supplier register, assigning components to suppliers and requesting an SBOM, VEX document or security information via an upload link without an account – with automatic reminders. Included in the Business plan.
Nebrino featuresReference: Art. 13(5)See also:Third-party components (supply chain),VEX,SBOM
- Support period
The period during which the manufacturer handles vulnerabilities effectively and provides security updates. It must reflect the expected period of use and is at least five years – shorter only if the product is expected to be in use for less time. You state the end of the support period clearly at the time of purchase (at least month and year). Each security update remains available for at least ten years after it was issued or for the remainder of the support period, whichever is longer. If you have placed a substantially modified subsequent version of a software product on the market, you may limit vulnerability remediation to the latest version, provided users can switch to it free of charge and without additional costs for adjusting their environment.
Law & obligationsReference: Art. 13(8)–(10), Art. 13(19)
- Technical documentation
The documents with which the manufacturer demonstrates conformity: product description, risk assessment, implementation of Annex I, SBOM, standards applied, test reports and more (Annex VII). It is drawn up before placing on the market, kept up to date and retained for at least ten years or for the support period, whichever is longer; market surveillance authorities can request it.
Standards & conformityReference: Art. 31, Annex VII, Art. 13(13)See also:Annex VII,Cybersecurity risk assessment,SBOM,Evidence,Retention period
- Third-party components (supply chain)
Manufacturers must exercise due diligence when integrating third-party components – including open source – so that they do not compromise the product's cybersecurity. If you find a vulnerability in a component, from 11 December 2027 you inform the person or entity manufacturing or maintaining it. Requests to suppliers and their responses serve as evidence.
Vulnerabilities & SBOMReference: Art. 13(5) and (6)See also:Component,Supply chain module,VEX,SBOM
- TOMsTechnical and organisational measures
Measures by which a controller or processor ensures the security of personal data – e.g. encryption, access control, backups. They are usually described in an annex to the DPA.
Law & obligationsReference: Art. 32 GDPR- TOTPTime-based one-time password
A method (RFC 6238) in which an authenticator app generates a new code, usually every 30 seconds, from a secret key and the current time. You import the key via QR code during set-up.
Technology & securityReference: RFC 6238See also:2FA / MFA
- Transitional provisions
Products placed on the market before 11 December 2027 are subject to the requirements of the Cyber Resilience Act only if they undergo a substantial modification from that date. The reporting obligations under Art. 14, by contrast, have applied since 11 September 2026 to all products in scope – including those already on the market before. EU type-examination certificates and approval decisions issued on cybersecurity requirements under other Union harmonisation legislation remain valid until 11 June 2028 unless they expire earlier.
Law & obligationsReference: Art. 69See also:Substantial modification,Placing on the market,Reporting obligation
- Trial
14 days of free use of all features, without a credit card – for new organisations outside the pilot programme (which has its own pilot period). Without a plan, data, reporting cases and deadlines remain accessible afterwards: you can continue working on reporting cases; requirements, documents and the other plan features are read-only.
Nebrino featuresSee also:Plans (Starter, Professional, Business),Pilot programme
- VEXVulnerability Exploitability eXchange
A machine-readable statement of whether a product is affected by a vulnerability: affected, not affected, fixed or under investigation. “Not affected” requires a justification – for example that the vulnerable code is not present or not executed. Nebrino never applies supplier VEX statements automatically.
Vulnerabilities & SBOMSee also:CSAF,Finding,SBOM,Third-party components (supply chain)
- Voluntary notification
Vulnerabilities, cyber threats and near misses without a reporting obligation can be notified voluntarily to a CSIRT or ENISA by manufacturers and others. This helps others to protect themselves.
ReportingReference: Art. 15See also:Reporting obligation,CSIRT,ENISA
- Vulnerability
A weakness, susceptibility or flaw of a product that can be exploited by a cyber threat. Known vulnerabilities usually carry a CVE or EUVD identifier. Not every vulnerability in a component affects your product – you record this using VEX.
Vulnerabilities & SBOMReference: Art. 3See also:CVE,EUVD,VEX,Actively exploited vulnerability,Exploit
- Workaround
An interim measure that reduces the risk of a vulnerability without fixing it – such as disabling a feature or blocking a port. A workaround can be a mitigating measure in the sense of the reporting obligation.
Vulnerabilities & SBOMSee also:Corrective or mitigating measure,Patch
- 2FA / MFATwo-factor / multi-factor authentication
Signing in with a second factor in addition to the password, e.g. a one-time code from an authenticator app. This protects your account even if the password becomes known. In Nebrino you set up two-factor authentication for your own account under Settings.
Technology & security
Short explanations, not legal advice. The text of Regulation (EU) 2024/2847 is authoritative. Full text of the regulation (EUR-Lex)