{
  "slug": "cra-product-makers",
  "topic": "CRA for product makers",
  "status": "published",
  "order": 68,
  "capability": "software/cra",
  "title": "Cyber Resilience Act: can you still sell your products in the EU after 11 December 2027?",
  "short": "Report exploited flaws within 24 hours now, and give every product a risk assessment, SBOM, support period and CE marking by 11 December 2027.",
  "answer": "Be ready now to report an actively exploited vulnerability or severe incident in any product on the EU market within 24 hours. Before 11 December 2027, give every product a class, a support period, a risk assessment, an SBOM and technical documentation, so it can carry the CE marking.",
  "audience": "Companies that make, import or distribute hardware or software sold in the EU, and open-source stewards",
  "version": "1.0",
  "lastReviewed": "2026-11-05",
  "reviewEveryDays": 30,
  "blocks": [
    {
      "type": "ranked",
      "id": "first",
      "title": "If you only do five things",
      "navTitle": "Five things",
      "items": [
        {
          "title": "Be able to report within 24 hours.",
          "text": "Reporting has applied since 11 September 2026, also to products placed on the market before December 2027 and after their support ends[^guide]. Name an owner and a deputy with EU Login accounts and MFA, and decide which CSIRT you report to[^srpfaq]."
        },
        {
          "title": "Classify each product by its core functionality.",
          "text": "Match it against Implementing Regulation (EU) 2025/2392[^ir2392]. Default products may always self-assess; important and critical ones may need a notified body[^guide]."
        },
        {
          "title": "Set a support period per product.",
          "text": "Base it on expected use, comparable products and your components' own support, and make it at least 5 years unless use is shorter[^cra]. Show the end month and year at purchase[^cra]."
        },
        {
          "title": "Write the risk assessment first.",
          "text": "It decides how each Annex I requirement applies and goes into the technical documentation[^cra]. Cover planned features too, so the updates that add them aren't substantial modifications[^guide]."
        },
        {
          "title": "Run vulnerability handling as a process.",
          "text": "Due diligence on third-party and open-source components, an SBOM per release, a disclosure policy and contact, and free security updates[^cra]. The supply chain and secure development sheets show how."
        }
      ]
    },
    {
      "type": "steps",
      "id": "scope",
      "title": "Are you in scope, and in which role?",
      "navTitle": "Scope and roles",
      "items": [
        {
          "title": "Does it connect to a device or network?",
          "text": "If so, the CRA covers it, with the remote data processing it needs to work[^cra]. Web apps used only in a browser, websites and SaaS are not products themselves[^guide]."
        },
        {
          "title": "Is it excluded?",
          "text": "Yes, if it's a medical or diagnostic device, a motor vehicle, a certified aviation product, marine equipment, an identical spare part or made only for national security or defense[^cra]."
        },
        {
          "title": "Do you supply it commercially?",
          "text": "Charging for it or for support beyond cost, monetizing it through other services or requiring personal data for more than security and compatibility counts, even if it's free[^cra]. Open source you don't monetize doesn't[^cra]."
        },
        {
          "title": "Are you an open-source steward?",
          "text": "You are if you're a foundation or company that systematically supports non-monetized open source meant for commercial use[^guide]. Stewards need a documented security policy[^cra], report from December 2027[^srpfaq] and can't be fined[^cra]."
        },
        {
          "title": "Which role do you have?",
          "text": "Manufacturers sell under their own name; importers and distributors check the CE marking and documents first[^cra]. Rebranding or substantially modifying a product makes you its manufacturer[^cra]."
        }
      ]
    },
    {
      "type": "list",
      "id": "classes",
      "title": "Product classes and conformity assessment",
      "navTitle": "Product classes",
      "items": [
        "**Default.** Anything whose core functionality isn't in Annex III or IV. Self-assessment (module A) is always allowed[^guide].",
        "**Important, class I.** 19 categories, such as identity and access management, browsers, password managers, antivirus, VPNs, operating systems, routers and smart home security products. Self-assess only by fully applying a cited harmonized standard, common specification or EU certificate at level substantial; otherwise use a notified body[^cra].",
        "**Important, class II.** Hypervisors, container runtimes, firewalls, intrusion detection and prevention systems and tamper-resistant chips. Always third party[^cra].",
        "**Critical.** Hardware security boxes, smart meter gateways and smartcards: EU certification where a delegated act requires it, otherwise as class II[^cra]. The class of the whole product counts, not that of its components[^guide].",
        "**Check which standards are cited.** Only standards cited in the Official Journal give presumption of conformity[^cra]. ETSI's approval of its 17 product-specific drafts ends between mid-September and mid-November 2026, by product[^etsi]."
      ]
    },
    {
      "type": "list",
      "id": "annex",
      "title": "Annex I in practice",
      "navTitle": "Annex I",
      "items": [
        "**No known exploitable flaws at release.** Known means in the EU vulnerability database or another prominent one, or reported to you[^guide].",
        "**Secure defaults.** A secure default configuration with a reset, access control, encryption of stored and transmitted data, minimal data and a way to delete it all[^cra].",
        "**Automatic security updates on by default, where applicable.** With an opt-out, notifications and a way to postpone. Not required for components or where users don't expect them, as in industrial networks[^cra].",
        "**An SBOM per release.** Machine-readable, covering at least top-level dependencies, and it needn't be public[^cra]. BSI TR-03183-2 asks for CycloneDX 1.6 or SPDX 3.0.1 or later, with dependencies resolved through everything you ship[^tr2].",
        "**One contact point, not just a chatbot.** A single point of contact not limited to automated tools, plus a disclosure policy[^cra]. BSI's voluntary TR-03183-3 adds a signed `security.txt`[^tr3].",
        "**Free fixes, kept available.** Keep each security update available for 10 years or the rest of the support period, if longer[^cra]. For software, fixing only the latest version is fine if upgrading costs users nothing extra[^cra].",
        "**Advisories and upstream reports.** Publish fixed flaws, in CSAF as the BSI recommends[^cra][^tr3], and send component flaws to their maintainer[^cra]."
      ]
    },
    {
      "type": "timelines",
      "id": "reporting",
      "title": "Reporting clocks since 11 September 2026",
      "navTitle": "Reporting clocks",
      "intro": "Clocks start at reasonable certainty after a prompt first check[^guide]. Report once on ENISA's platform, in Germany to CERT-Bund, and tell affected users[^cra][^bsisrp].",
      "items": [
        {
          "name": "Actively exploited vulnerability",
          "scope": "Reliable evidence of exploitation[^cra]; a public exploit isn't enough[^bsisrp].",
          "steps": [
            {
              "at": "24 hours",
              "what": "Early warning"
            },
            {
              "at": "72 hours",
              "what": "Notification"
            },
            {
              "at": "Fix + 14 days",
              "what": "Final report"
            }
          ]
        },
        {
          "name": "Severe incident",
          "scope": "It harms or could harm the product's protection of sensitive or important data or functions, or could plant malicious code in it or users' systems[^cra]. Ransomware at the maker counts only if it could affect the product, its updates or signing keys[^bsisrp].",
          "steps": [
            {
              "at": "24 hours",
              "what": "Early warning"
            },
            {
              "at": "72 hours",
              "what": "Notification"
            },
            {
              "at": "1 month later",
              "what": "Final report"
            }
          ]
        }
      ]
    },
    {
      "type": "list",
      "id": "docs",
      "title": "Documentation, CE marking and fines",
      "navTitle": "Documentation and CE",
      "items": [
        "**Technical documentation (Annex VII).** Architecture, vulnerability handling with SBOM and disclosure policy, risk assessment, support period reasons, standards, test reports and the declaration. Keep it 10 years or for the support period, if longer[^cra].",
        "**EU declaration of conformity.** Follow Annex V, ship it or a simplified version with its web address, and issue one for all EU acts that need one[^cra].",
        "**CE marking from 11 December 2027.** On the product, or the packaging and declaration; for software, on the declaration or its website[^cra].",
        "**Fines up to €15 million or 2.5% of worldwide turnover.** For breaching Annex I or Articles 13 and 14; €10 million or 2% for most other duties. Micro and small manufacturers aren't fined for a late 24-hour early warning, under Article 64(10) as corrected in July 2025[^cra][^cracorr]."
      ]
    },
    {
      "type": "list",
      "id": "skip",
      "title": "What you can skip",
      "items": [
        "**Waiting for harmonized standards.** The risk assessment, SBOM, disclosure policy and update channel don't depend on them.",
        "**Reporting every vulnerable dependency.** Flaws that aren't reachable or exploited in your product aren't reportable; tell the maintainer[^guide].",
        "**Redesigning products that already hold up.** Designs from before the CRA need no change if the risk assessment shows adequate measures[^guide].",
        "**Registering on ENISA's platform early.** ENISA advises registering only when you first need to report[^srpfaq]."
      ]
    },
    {
      "type": "list",
      "id": "mistakes",
      "title": "Mistakes that cost the most",
      "navTitle": "Mistakes",
      "items": [
        "**Counting on the transition for hardware.** Every unit placed on the market from 11 December 2027 must comply, even of an older model[^guide].",
        "**Picking the wrong CSIRT.** The notification may be invalidated and need resubmitting[^srpfaq].",
        "**Rebranding without noticing.** An importer or distributor selling under its own name becomes the manufacturer[^cra].",
        "**A 5-year support period by reflex.** The Commission says 5 years is not a default; products used longer need longer support[^guide]."
      ]
    },
    {
      "type": "list",
      "id": "changed",
      "title": "What changed in 2026",
      "navTitle": "What changed",
      "span": "full",
      "items": [
        "**Reporting went live on 11 September.** ENISA's platform is English only, has no API yet, and its 72-hour counter can show reports overdue early[^srpfaq].",
        "**Draft Commission guidance, 27 July.** It explains scope, open source, substantial modification and support periods, and isn't binding[^guide].",
        "**Germany is naming the BSI.** A bill the Bundestag passed on 15 October would make it market surveillance authority[^bthib][^brdrs].",
        "**Radio equipment moves to the CRA.** The radio equipment cybersecurity delegated act is repealed from 11 December 2027[^dr339]."
      ]
    },
    {
      "type": "columns",
      "id": "by-size",
      "title": "What this looks like at your size",
      "navTitle": "By team size",
      "span": "full",
      "columns": [
        {
          "title": "Small team, no security staff",
          "items": [
            "List every product and version you sell in the EU, with its class and support end date.",
            "Write a one-page runbook: who reports, to which CSIRT, from which EU Login accounts.",
            "Work through BSI TR-03183-1 as a checklist[^tr]."
          ]
        },
        {
          "title": "Growing, with IT or security staff",
          "items": [
            "Name a product security owner and ship an SBOM and advisories with every release.",
            "Plan for a notified body now if a product needs one; Member States aim to have enough by 11 December 2026[^cra].",
            "Document one product end to end, then reuse it for its variants[^guide]."
          ]
        },
        {
          "title": "Enterprise or regulated",
          "items": [
            "Build module H on your ISO/IEC 27001 ISMS, as BSI TR-03183-H shows[^tr].",
            "Run CRA reports in your NIS2 incident process; the EU security laws sheet has those clocks.",
            "Agree how importers and distributors pass on the vulnerabilities they must report to you[^cra]."
          ]
        }
      ]
    }
  ],
  "changes": [
    {
      "date": "2026-11-05",
      "version": "1.0",
      "text": "Published after a copy edit and a source-by-source fact check, which confirmed the small-maker fines exemption in the July 2025 corrigendum, added component due diligence, a non-public SBOM and the Bundestag's 15 October vote, and separated BSI recommendations from CRA duties."
    },
    {
      "date": "2026-11-05",
      "version": "0.1",
      "text": "First draft, based on the CRA, Implementing Regulation (EU) 2025/2392, the Commission's draft guidance of July 2026, ENISA's reporting platform FAQ and the BSI's TR-03183 and reporting pages."
    }
  ],
  "sources": [
    {
      "id": "cra",
      "title": "Regulation (EU) 2024/2847 (Cyber Resilience Act)",
      "publisher": "EUR-Lex",
      "date": "2024",
      "url": "https://eur-lex.europa.eu/eli/reg/2024/2847/oj"
    },
    {
      "id": "cracorr",
      "title": "Corrigendum to Regulation (EU) 2024/2847, Article 64(10)",
      "publisher": "EUR-Lex",
      "date": "2 Jul 2025",
      "url": "https://eur-lex.europa.eu/eli/reg/2024/2847/corrigendum/2025-07-02/oj"
    },
    {
      "id": "guide",
      "title": "Draft Commission guidance on the application of the CRA, annex to C(2026) 5252",
      "publisher": "European Commission",
      "date": "27 Jul 2026",
      "url": "https://ec.europa.eu/newsroom/dae/redirection/document/131456"
    },
    {
      "id": "ir2392",
      "title": "Implementing Regulation (EU) 2025/2392 (important and critical products)",
      "publisher": "EUR-Lex",
      "date": "28 Nov 2025",
      "url": "https://eur-lex.europa.eu/eli/reg_impl/2025/2392/oj"
    },
    {
      "id": "srpfaq",
      "title": "CRA Single Reporting Platform: FAQ",
      "publisher": "ENISA",
      "date": "updated 15 Oct 2026",
      "url": "https://www.enisa.europa.eu/topics/product-security/vulnerability-services/eu-incident-response-and-cyber-crisis-management/single-reporting-platform-srp/frequently-asked-questions"
    },
    {
      "id": "bsisrp",
      "title": "CRA Single Reporting Platform",
      "publisher": "BSI",
      "date": "checked 5 Nov 2026",
      "url": "https://www.bsi.bund.de/DE/Themen/Unternehmen-und-Organisationen/Informationen-und-Empfehlungen/Cyber_Resilience_Act/Single_Reporting_Platform-CRA/single_reporting_platform-cra_node.html"
    },
    {
      "id": "tr",
      "title": "TR-03183: Cyber Resilience Requirements",
      "publisher": "BSI",
      "date": "checked 5 Nov 2026",
      "url": "https://www.bsi.bund.de/DE/Themen/Unternehmen-und-Organisationen/Standards-und-Zertifizierung/Technische-Richtlinien/TR-nach-Thema-sortiert/tr03183/TR-03183_node.html"
    },
    {
      "id": "tr2",
      "title": "TR-03183-2: Software Bill of Materials, v2.1.0",
      "publisher": "BSI",
      "date": "20 Aug 2025",
      "url": "https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03183/BSI-TR-03183-2_v2_1_0.pdf?__blob=publicationFile"
    },
    {
      "id": "tr3",
      "title": "TR-03183-3: Vulnerability Reports and Notifications, v1.0.0",
      "publisher": "BSI",
      "date": "20 Aug 2025",
      "url": "https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03183/BSI-TR-03183-3_v1_0_0.pdf?__blob=publicationFile"
    },
    {
      "id": "etsi",
      "title": "ETSI launches approval process for 17 European Standards supporting the Cyber Resilience Act",
      "publisher": "ETSI",
      "date": "13 Aug 2026",
      "url": "https://www.etsi.org/newsroom/press-releases/etsi-launches-approval-process-for-17-european-standards-supporting-the-cyber-resilience-act/"
    },
    {
      "id": "bthib",
      "title": "Ausschuss billigt Gesetzentwurf zu Cyberresilienz-Verordnung",
      "publisher": "Deutscher Bundestag",
      "date": "14 Oct 2026",
      "url": "https://www.bundestag.de/1224738"
    },
    {
      "id": "brdrs",
      "title": "Gesetzesbeschluss zur Cyberresilienz-Verordnung, Drucksache 621/26",
      "publisher": "Bundesrat",
      "date": "30 Oct 2026",
      "url": "https://dserver.bundestag.de/brd/2026/0621-26.pdf"
    },
    {
      "id": "dr339",
      "title": "Delegated Regulation (EU) 2026/339 repealing Delegated Regulation (EU) 2022/30",
      "publisher": "EUR-Lex",
      "date": "29 Apr 2026",
      "url": "https://eur-lex.europa.eu/eli/reg_del/2026/339/oj"
    }
  ]
}