This document is under active development and has not been finalised.
Skip to content

Chapter 3: Vulnerability Management

3.1 Overview

Vulnerability management is one of the core obligations under the CRA. Manufacturers must identify, assess, remediate, and report vulnerabilities in their products throughout the entire support period.

LEGAL BASIS

Art. 10(6) CRA: The manufacturer shall have effective and regular procedures in place to identify vulnerabilities in the product.

Annex I, Part II, No. 2: The manufacturer shall identify and document the vulnerabilities and components of the product and remediate known vulnerabilities without delay.

3.2 Process Architecture

                         +---------------------+
                         |  SBOM (per release)  |
                         +----------+----------+
                                    |
              +----------+----------+----------+----------+
              v          v          v          v          v
    +--------------+ +--------+ +--------+ +--------+ +--------+
    |CVE Monitoring| |Dependa-| | Trivy  | |  OSV-  | | Grype  |
    |(daily SBOM)  | |  bot   | | Scan   | |Scanner | |(option)|
    |              | |(PR)    | |(CI/CD) | |(CI/CD) | |        |
    +------+-------+ +---+----+ +---+----+ +---+----+ +---+----+
           |             |          |          |          |
           +-------------+----------+----------+----------+
                                    v
                         +----------------------+
                         |  Triage & Assessment  |
                         |  (CVSS / Severity)    |
                         +----------+-----------+
                                    |
                   +----------------+----------------+
                   v                v                 v
         +-----------------+ +--------------+ +--------------+
         |  CRITICAL/HIGH   | |  MEDIUM/LOW  | |  No CVEs     |
         |  -> Immediate    | |  -> Planned  | |  -> Continue  |
         |     patch        | |  -> Next     | |    monitoring |
         |  -> ENISA report | |    release   | |              |
         |     if required  | |              | |              |
         +-----------------+ +--------------+ +--------------+

3.3 Chapter Structure

SectionTopicDescription
3.1CVE MonitoringDaily scan of all product SBOMs against CVE databases
3.2Dependency MonitoringContinuous monitoring via Dependabot + GitHub Security Alerts
3.3Patch ManagementSLA-based process for vulnerability remediation
3.4Risk AssessmentMethodology for assessment in the product context
3.5Handling Requirements (Annex I Part II)8 vulnerability handling requirements

3.4 Responsibilities

RoleTask
Security LeadTriage, risk assessment, escalation, ENISA reporting
DevOps LeadCVE monitor operations, pipeline maintenance
Development TeamPatch development, testing
Product OwnerPrioritisation, release planning

Documentation licensed under CC BY-NC 4.0 · Code licensed under MIT