<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by CRA Decoded on Medium]]></title>
        <description><![CDATA[Stories by CRA Decoded on Medium]]></description>
        <link>https://medium.com/@cra-decoded?source=rss-b20a11df9499------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Zpex4si4X30Md-pMdmmgTw.png</url>
            <title>Stories by CRA Decoded on Medium</title>
            <link>https://medium.com/@cra-decoded?source=rss-b20a11df9499------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:50:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cra-decoded/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[CRA Decoded — EU Cyber Resilience Act explained for engineers — has its own blog now.]]></title>
            <link>https://medium.com/@cra-decoded/cra-decoded-eu-cyber-resilience-act-explained-for-engineers-has-its-own-blog-now-c3f54153096e?source=rss-b20a11df9499------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3f54153096e</guid>
            <dc:creator><![CDATA[CRA Decoded]]></dc:creator>
            <pubDate>Sun, 17 May 2026 11:31:16 GMT</pubDate>
            <atom:updated>2026-05-17T11:31:16.297Z</atom:updated>
            <content:encoded><![CDATA[<p>All articles are live at <a href="https://cra-decoded.com/blog">cra-decoded.com/blog</a> — the home for practical CRA compliance guides written for engineering teams, not lawyers. Faster, no Medium paywall warnings, no “you’ve read 3 free articles this month” nonsense.</p><p>Everything that was here stays here: 12 articles, all indexed, nothing deleted. New content goes to the blog first. Medium gets it eventually, or doesn’t.</p><p>If September 2026 is on your radar (it should be, that’s when CRA Article 14 vulnerability reporting kicks in), get on the weekly newsletter. Every Sunday. Free. Just what engineering teams actually need to know before the deadline hits.</p><p><a href="https://cradecoded.substack.com/">Subscribe to the weekly CRA newsletter</a></p><p>New article this Sunday. See you there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3f54153096e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CRA Technical Documentation: Complete Checklist for Manufacturers]]></title>
            <link>https://medium.com/@cra-decoded/cra-technical-documentation-complete-checklist-for-manufacturers-a7a8efc2b0db?source=rss-b20a11df9499------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7a8efc2b0db</guid>
            <category><![CDATA[iot-security]]></category>
            <category><![CDATA[eu-regulation]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[compliance]]></category>
            <dc:creator><![CDATA[CRA Decoded]]></dc:creator>
            <pubDate>Sun, 10 May 2026 12:54:29 GMT</pubDate>
            <atom:updated>2026-05-10T12:54:29.532Z</atom:updated>
            <content:encoded><![CDATA[<h3>CRA Technical Documentation: The Complete Checklist for Manufacturers</h3><figure><img alt="Technical documentation folders and engineering blueprints on a desk — CRA compliance file structure" src="https://cdn-images-1.medium.com/max/1024/0*nRPgA7UDE8PkuIgx" /><figcaption>Photo by <a href="https://unsplash.com/@georgediama_exe?utm_source=medium&amp;utm_medium=referral">George Diama</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Your product connects to the internet. It ships to EU customers. Under Regulation (EU) 2024/2847, that means assembling a <strong>CRA Technical Documentation package</strong> before it hits the market — one that proves your product was built securely, that its vulnerabilities get handled, and that someone accountable will still be patching it years from now.</p><p>Market surveillance authorities can request this file at any time. If you can’t produce it, the product comes off the shelf. CE marking denied. Fines up to €15 million or 2.5% of global annual turnover — whichever is higher.</p><p>Full compliance deadline: <strong>December 11, 2027</strong>. The first hard deadline — Article 14 vulnerability reporting — hits <strong>September 11, 2026</strong>. That’s 16 months from now.</p><p>At CRA Decoded, we’ve mapped Annex VII against the documentation most engineering teams already have. The gap is almost always the same: risk assessment and SBOM retention process, not product description. This article covers both and everything else Annex VII requires.</p><h3>What “Technical Documentation” Actually Means Under the CRA</h3><p>Not a single document. A structured evidence file — the audit trail your entire product security lifecycle needs to produce.</p><p>The legal basis is <strong>Article 31</strong>: documentation must contain all information demonstrating that the product and the manufacturer’s processes comply with the essential cybersecurity requirements in Annex I. The detailed contents are enumerated in <strong>Annex VII</strong>.</p><p><strong>Annex VII has five sections:</strong></p><ol><li>Product description and architecture</li><li>Design, development, production, and vulnerability handling processes</li><li>Cybersecurity risk assessment</li><li>Support period rationale</li><li>Test reports and conformity evidence</li></ol><p>Each section needs traceable, dated artifacts. “We follow best practices” is not an artifact.</p><h3>Section 1: Product Description and Architecture</h3><p>Annex VII §1 requires a general product description: intended use, product version, hardware photos or illustrations if applicable, and — critically — a <strong>system architecture description explaining how software components build on or feed into each other and integrate into the overall processing</strong>.</p><p>In practice:</p><ul><li>A component diagram showing all software layers (firmware, OS, middleware, application, libraries)</li><li>Identified network interfaces and communication protocols</li><li>Data flow diagrams covering authentication, update channels, and logging paths</li><li>For hardware: labeled photographs of internal layout and external markings</li></ul><p>If your product is integrated into someone else’s product with digital elements, the architecture documentation also needs to provide the integrator with enough information to meet <em>their own</em> CRA obligations. This matters if you ship modules, SDKs, or embedded components — your downstream customers become responsible for what you don’t document.</p><p>Products falling under Annex III (Important) or Annex IV (Critical) will have their architecture description scrutinized more closely. Notified Bodies use this diagram as their entry point into the technical file.</p><h3>Section 2: Design, Development, and Vulnerability Handling Processes</h3><p>The most operationally demanding section. Annex VII §2 requires documentation of:</p><ul><li>How the product was designed and developed (secure development lifecycle evidence)</li><li>Vulnerability handling processes, including the <strong>Software Bill of Materials (SBOM)</strong></li><li>Your <strong>Coordinated Vulnerability Disclosure (CVD) policy</strong></li><li>Evidence of a contact address for vulnerability reporting</li><li>A description of secure update distribution</li></ul><h4>The SBOM Requirement</h4><figure><img alt="Developer reviewing software dependencies in a terminal — SBOM generation for CRA compliance" src="https://cdn-images-1.medium.com/max/1024/0*UCmCYpBYJ0vflhr7" /><figcaption>Photo by <a href="https://unsplash.com/@harshitkatiyar?utm_source=medium&amp;utm_medium=referral">Harshit Katiyar</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>SBOMs are mandatory for every product containing software. The SBOM requirement catches teams off guard more than anything else in Annex VII — not because it’s hard to generate one, but because the CRA requires it to be current, versioned, and <strong>stored for up to a decade</strong>. The CRA doesn’t specify a format, but <a href="https://www.bsi.bund.de/EN/Themen/Unternehmen-und-Organisationen/Standards-und-Zertifizierung/Technische-Richtlinien/TR-nach-Thema-sortiert/tr03183/tr-03183.html"><strong>BSI TR-03183–2</strong></a> (v2.1.0, August 2025) — Germany’s BSI technical guideline and currently the most detailed public interpretation of CRA SBOM requirements in the EU — requires:</p><ul><li>Machine-readable format: <strong>CycloneDX</strong> or <strong>SPDX</strong> (JSON or XML only, no YAML)</li><li>Transitive dependency coverage, not just direct dependencies</li><li>Recursive dependency resolution for every component in the delivery scope</li></ul><p>Syft for a container image:</p><pre>syft scan my-product:1.4.2 -o cyclonedx-json=sbom-1.4.2.cdx.json</pre><p>Syft for a directory (firmware build output):</p><pre>syft scan dir:/build/output -o spdx-json=sbom-1.4.2.spdx.json</pre><p>Syft and Trivy handle direct and first-level transitive dependencies well. Deep transitive resolution for interpreted languages (Python, Ruby, Node.js) needs package-manager-specific analysis. For Python:</p><pre>cdxgen -t python --output sbom.cdx.json .</pre><p>Check quality against BSI TR-03183–2:</p><pre>sbomqs score sbom-1.4.2.cdx.json --profile bsi-v2.0</pre><p>BSI TR-03183–2 also requires version-controlled storage of SBOMs and a process for updating SBOMs with each release. If your CI/CD pipeline doesn’t generate a new SBOM on every tagged build, that’s a process gap — and it will show up in your technical documentation.</p><h4>Coordinated Vulnerability Disclosure Policy</h4><p>The CVD policy must be publicly accessible and cover how you receive reports, triage them, define your response timeline commitments, and notify users when patches are available. A security.txt at /.well-known/security.txt is the baseline:</p><pre>Contact: mailto:security@your-company.com<br>Policy: https://your-company.com/security-policy<br>Preferred-Languages: en, de, fr</pre><p>The policy document itself needs explicit timelines. Most teams reference ISO/IEC 29147 as their framework — auditors recognize it, and it saves you from inventing your own structure.</p><h4>Secure Development Lifecycle Evidence</h4><p>The CRA doesn’t mandate a specific SDL framework. What it requires is <em>documented evidence</em> that security was considered at the design stage, not just tested after the fact. Acceptable evidence:</p><ul><li>Threat model documents (STRIDE, PASTA, or DREAD-based) linked to architecture diagrams</li><li>Security requirements in your product backlog or design specs</li><li>SAST, DAST, fuzzing, and SCA results with tool names, versions, scan dates, and findings</li><li>Penetration test reports, if conducted</li><li>Code review records covering security-relevant changes</li></ul><p>The European Commission published draft guidance in March 2026 clarifying the interpretation of several Annex I requirements. Not yet finalized, but the direction is clear: security review must be a distinct, documented step in the development process — not incidental to general QA.</p><h3>Section 3: The Cybersecurity Risk Assessment</h3><p><strong>Article 13(2)</strong> requires a cybersecurity risk assessment. <strong>Article 13(4)</strong> requires it to be included in the Technical Documentation at the time of market placement.</p><p>This cannot be done retroactively. If the risk assessment doesn’t exist before the product ships, the product is non-compliant on day one.</p><p>The CRA doesn’t mandate a specific methodology. STRIDE for threat modeling combined with CVSS for severity scoring is a defensible combination. The assessment must:</p><ul><li>Identify relevant threats and attack surfaces</li><li>Map threats to the essential requirements in Annex I, Part I</li><li>Explain how each requirement is implemented, or justify why it doesn’t apply</li><li>Be updated when the product changes substantially</li></ul><p>If an Annex I requirement genuinely doesn’t apply to your product, you still can’t skip it — write a justification explaining why. Silence fails the audit.</p><p>There’s a meaningful difference between a risk assessment that says “<em>we use TLS everywhere, authenticated updates, and no default passwords</em>” and one that says “<em>we assessed threats T1 through T14 using STRIDE, scored them with CVSS 3.1, and mapped mitigations to Annex I Part I points (1) through (13).</em>” Auditors know the difference, too.</p><p>One gap to flag: harmonized standards for this process are still being developed. The Commission issued a standardization request to CEN/CENELEC and ETSI in February 2025 — the EN 40000 series is the target output. Until those ships, you’re self-certifying against the regulation text directly. BSI TR-03183–1 and ETSI EN 303 645 (consumer IoT) are the closest usable references right now.</p><h3>Section 4: Support Period Documentation</h3><p><strong>Article 13(8)</strong> requires manufacturers to determine a support period “appropriate to the type of product.” The determination and the factors behind it must be documented in the technical file.</p><p>Five years is the practical floor for most products — based on recital language and the requirement that security updates remain available for at least 10 years after release (or the remainder of the support period, whichever is longer — Article 13(9)).</p><p>The documentation needs to cover:</p><ul><li>Declared end-of-support date per product version</li><li>Update delivery mechanism (OTA, manual download, CDN)</li><li>Commitment to security-only update availability for the full period</li><li>How users are notified when support ends</li></ul><p>For IoT and embedded products with long field lifetimes, this is where the CRA hits hardest. If customers keep your device for 10–15 years, but your support window has historically been 3 years, no documentation template fixes that. It’s a product architecture and commercial model decision that has to be made before launch, not after.</p><h3>Section 5: Test Reports and Conformity Evidence</h3><p>Annex VII §5 requires test reports or other evidence demonstrating conformity with the essential requirements. What that looks like depends on your product classification.</p><h4>Default Category: Self-Assessment Under Module A</h4><p>Products not listed in Annex III or Annex IV qualify for <strong>Module A</strong> self-assessment. You write the test reports yourself, retain them, and draw up the EU Declaration of Conformity in the Annex V format. No third party involved.</p><p>Module A still requires actual test evidence. A checklist without underlying test artifacts won’t survive a market surveillance inspection.</p><h4>Important Class I Products: When a Notified Body Gets Involved</h4><p>Operating systems, browsers, VPN clients, network management systems, identity management systems, smart home security devices, routers, switches. These require either conformity assessment against harmonized standards (when available) or third-party assessment by a Notified Body — Module B + C, or Module H.</p><p>Member States must designate Notified Bodies by June 11, 2026. Until the designation occurs, the third-party assessment can’t proceed formally. If your product is an Important Class I, start the documentation now and identify potential Notified Bodies early — engagement takes time.</p><h4>Important Class II and Critical Products</h4><p>Firewalls, hypervisors, intrusion detection systems (Class II). Smart meter gateways, hardware security modules (Critical/Annex IV). Notified Body involvement is required. No alternatives.</p><h3>EU Declaration of Conformity: What Goes in It and When to Update</h3><p>Separate from the technical documentation file. Structure defined in <strong>Annex V</strong> of the CRA. It must contain:</p><ul><li>Product name, type, batch, and serial number</li><li>Manufacturer name and address</li><li>Statement that the product meets essential requirements</li><li>References to harmonized standards or common specifications used, if applicable</li><li>Date and signature of authorized representative</li></ul><p>Update the DoC whenever the product changes substantially. It travels with the product — or is made available digitally — and points back to the technical documentation file.</p><p><strong>Annex VI</strong> provides a simplified DoC format for cases where the product itself doesn’t have room for the full version. A URL to the complete document suffices.</p><h3>Retention: 10 Years or the Support Period</h3><figure><img alt="Data center server racks representing long-term compliance artifact storage under CRA Article 13" src="https://cdn-images-1.medium.com/max/1024/0*Vy8vV5tAtkM2leE6" /><figcaption>Photo by <a href="https://unsplash.com/@noa69?utm_source=medium&amp;utm_medium=referral">Yuriy Vertikov</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Article 13(13) is unambiguous: technical documentation and the EU Declaration of Conformity must remain available to market surveillance authorities for at least <strong>10 years</strong> after market placement, or for the support period — whichever is longer.</p><p>Five-year support period: 10-year retention obligation. Twelve-year support period: 12-year retention obligation.</p><p>Your S3 bucket or Confluence space from 2027 needs to still exist and be searchable in 2037. SBOM files, test reports, and risk assessment documents are compliance artifacts — not ephemeral build outputs. Treat them accordingly from day one:</p><pre># Tag and archive SBOM artifacts at release time<br>git tag -a v1.4.2 -m &quot;Release 1.4.2&quot;<br>aws s3 cp sbom-1.4.2.cdx.json s3://compliance-artifacts/sbom/ --storage-class GLACIER_IR</pre><p>Set up the S3 lifecycle policy and tagging convention on day one of the project, not the week before launch.</p><h3>What the Technical Documentation File Looks Like in Practice</h3><p>Annex VII doesn’t mandate a folder structure — it mandates content. How you organize it is your call. That said, mapping folders directly to Annex VII sections has one practical advantage: when a market surveillance authority or Notified Body asks “where’s the risk assessment?”, the answer is 04-risk-assessment/, not &quot;somewhere in Confluence, let me check.&quot;</p><p>Some teams keep SAST reports in their CI system and reference them by URL in the README. That works — as long as the URL resolves in 2037.</p><pre>technical-documentation/<br>├── README.md                        # Document index with version history<br>├── 01-product-description/<br>│   ├── product-overview.md          # Intended use, versions, scope<br>│   ├── architecture-diagram.drawio  # System architecture<br>│   └── interface-specification.md   # Network interfaces, protocols<br>├── 02-sdl-evidence/<br>│   ├── threat-model-v1.2.md         # STRIDE threat model<br>│   ├── sast-report-2027-01.html     # Semgrep/Checkmarx results<br>│   ├── dast-report-2027-01.html     # OWASP ZAP results<br>│   ├── pentest-report-2026-Q4.pdf   # Penetration test<br>│   └── sbom-1.4.2.cdx.json         # CycloneDX SBOM<br>├── 03-vulnerability-handling/<br>│   ├── cvd-policy.md                # Coordinated Vulnerability Disclosure<br>│   ├── vulnerability-register.csv   # Active and resolved vulnerabilities<br>│   └── update-mechanism.md          # OTA process description<br>├── 04-risk-assessment/<br>│   ├── risk-assessment-v1.0.md      # Threats, mitigations, Annex I mapping<br>│   └── annex-i-compliance-matrix.md # Requirement-by-requirement mapping<br>├── 05-support-period/<br>│   └── support-period-rationale.md  # Declared period, update commitments<br>├── 06-test-reports/<br>│   ├── functional-security-test.md  # Internal test results<br>│   └── review-records.md            # Security review log<br>└── 07-conformity/<br>    ├── eu-declaration-of-conformity.pdf<br>    └── ce-marking-rationale.md</pre><p>The README.md at the root is the first thing auditors open. Include a version history table, the product name and version the documentation covers, and a one-line status per folder: complete, in progress, or not applicable, with justification. That alone saves hours during an inspection.</p><h3>CRA Standards Still in Development: What’s Not Settled Yet</h3><p>Two things worth flagging before you build processes around them:</p><p><strong>Harmonized standards</strong> are not yet published. The EN 40000 series from CEN/CENELEC will eventually give products a presumption of conformity with Annex I — but timelines remain open. Until then, self-certification against the regulation text is the only route, with BSI TR-03183 and ETSI EN 303 645 as non-binding references.</p><p>Article 14 reporting runs through <strong>ENISA’s Single Reporting Platform</strong>, which is still in development as of publication. The workflow you build now needs room to adapt. Watch the <a href="https://euvd.enisa.europa.eu/">ENISA EUVD portal</a> for updates on when the platform goes live and what format it accepts.</p><h3>CRA Technical Documentation: Where to Start This Week</h3><p><strong>Run a gap analysis against Annex VII.</strong> Map your existing documentation — architecture docs, test reports, security policies — to each of the five sections. Gaps are what you need to build.</p><p><strong>Generate and archive your first SBOM.</strong> Integrate Syft or cdxgen into your CI/CD pipeline on at least one product line. A CycloneDX JSON artifact on every tagged release, archived immediately. Takes less than a day to set up.</p><p><strong>Start your risk assessment.</strong> Use STRIDE against your architecture diagram, score with CVSS 3.1, and map mitigations to Annex I Part I. A Google Doc with the right content beats a sophisticated tool with no output.</p><p>The December 2027 deadline looks manageable. September 2026 does not. Getting your CRA technical documentation right the first time saves rework closer to the deadline — and gives you a defensible file if market surveillance knocks. Start now.</p><h3>Subscribe to CRA Decoded</h3><p>Receive weekly technical guides on EU Cyber Resilience Act compliance directly in your inbox.</p><p><strong>You will receive:</strong></p><ul><li>Comprehensive implementation guides, including SBOM, vulnerability management, and CE marking.</li><li>Updates on CRA regulations from ENISA and the European Commission.</li><li>Tool reviews and practical recommendations.</li><li>Actionable checklists and templates.</li></ul><p>👉<a href="https://cradecoded.substack.com/subscribe"> Subscribe here</a></p><p><em>Free. Published every Sunday. Unsubscribe at any time.</em></p><h3>About CRA Decoded</h3><p>An independent engineering publication that translates EU cybersecurity regulations into practical guides for software teams.</p><p>📧 Newsletter:<a href="https://cradecoded.substack.com/"> cradecoded.substack.com</a></p><p>🌐 Website:<a href="https://cra-decoded.com/"> cra-decoded.com</a></p><p>✉️ Contact: contact@cra-decoded.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7a8efc2b0db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CE Marking for Software Under the CRA: Conformity Assessment Guide]]></title>
            <link>https://medium.com/@cra-decoded/ce-marking-for-software-under-the-cra-conformity-assessment-guide-27b9cb2cfbe9?source=rss-b20a11df9499------2</link>
            <guid isPermaLink="false">https://medium.com/p/27b9cb2cfbe9</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[eu-regulation]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[compliance]]></category>
            <dc:creator><![CDATA[CRA Decoded]]></dc:creator>
            <pubDate>Sun, 03 May 2026 11:27:03 GMT</pubDate>
            <atom:updated>2026-05-03T11:27:03.974Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A worker inspecting a manufactured product on an assembly line — conformity assessment under the EU Cyber Resilience Act applies to the entire product lifecycle, from design to production." src="https://cdn-images-1.medium.com/max/1024/0*OMVIvwOqB5Fdkohp" /><figcaption>Photo by <a href="https://unsplash.com/@trewcosmetic?utm_source=medium&amp;utm_medium=referral">Trew</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Your firmware ships. You put it through electrical safety testing, slap a CE mark on the packaging, and clear customs. That process has worked for hardware manufacturers for decades. Under the Cyber Resilience Act, it’s no longer enough — and the gap between what CE marking used to require and what it requires now is where most software teams are going to get caught.</p><p>CE marking for software under the CRA requires a full cybersecurity conformity assessment — something that didn’t exist in EU product law before 2024. From December 11, 2027, a product with digital elements cannot legally be placed on the EU market without a CE mark covering cybersecurity conformity. Not just electrical safety. Not just radio equipment compliance. Cybersecurity, documented, assessed, and declared.</p><h3>What the CE Mark Has Meant (Until Now)</h3><p>The CE marking system has been running since the early 1990s under the EU’s New Legislative Framework (NLF). The basic idea: a manufacturer self-declares that their product meets a set of essential requirements defined in EU legislation, affixes the CE mark, and takes legal responsibility for that claim.</p><p>Different directives cover different requirements. The Radio Equipment Directive covers radio and connectivity. The Machinery Directive covers mechanical safety. The Low Voltage Directive covers electrical safety. Until the CRA, there was no horizontal EU legislation mandating cybersecurity requirements for software products. You could ship a poorly secured connected device with a valid CE mark, because nothing in the CE marking framework required you to have secured it.</p><p>The CRA closes that gap. It’s built on the same NLF mechanics — same declaration of conformity structure, same technical documentation obligations, same notified body framework — but adds cybersecurity as a mandatory requirement for any product with digital elements (PDE).</p><blockquote><em>“Before placing a product with digital elements on the market, manufacturers shall draw up the technical documentation referred to in Article 31. They shall carry out the chosen conformity assessment procedures as referred to in Article 32 or have them carried out. Where compliance […] has been demonstrated by that conformity assessment procedure, manufacturers shall draw up the EU declaration of conformity in accordance with Article 28 and affix the CE marking in accordance with Article 30.”</em> — CRA Article 13(12)</blockquote><p>The CE mark on a CRA-compliant product means something it never meant before: that the manufacturer has assessed, documented, and declared conformity with a set of security requirements covering the product’s entire design, development, and production process.</p><p>At CRA Decoded, we’ve tracked the conformity assessment landscape since the regulation entered into force. The pattern we see most often: teams that have been through RED or Machinery Regulation CE marking assume the process transfers directly. It doesn’t — the cybersecurity evidence requirements in Annex VII are a different category of documentation than anything RED required.</p><h3>CE Marking Requires Three Documents — Here’s What Changed</h3><p>The NLF has always required three documents for CE marking. The CRA doesn’t add a fourth — it rewrites what goes inside the ones you already know.</p><p>The <strong>EU Declaration of Conformity (DoC)</strong> is a signed legal declaration that your product meets all applicable EU legislation. Under the CRA, it must reference the essential cybersecurity requirements in Annex I and the conformity assessment procedure used (Annex VIII). The format requirements are in Annex V. You sign it, your name and address are on it, and it accompanies the product.</p><p>The <strong>Technical Documentation</strong> is the evidence file that substantiates the DoC. Annex VII specifies the minimum content — more on this below.</p><p><strong>Instructions to the User</strong>, covered by Annex II, specify what you must communicate to end users: contact details for reporting vulnerabilities, the end date of the support period, how to install security updates, and any residual risks. For software products, this is typically a security.txt file combined with release notes — but the content must satisfy the Annex II list specifically, not just be &quot;somewhere on the website.&quot;</p><p>All three documents must be retained for at least 10 years after placing the product on the market, or for the duration of the support period, whichever is longer (Article 13(13)).</p><figure><img alt="An engineer reviewing technical documentation at a desk — the CRA’s Annex VII specifies what must go into the technical file before a product can be CE marked." src="https://cdn-images-1.medium.com/max/1024/0*qNmuNQD7M-ts6dR3" /><figcaption>Photo by <a href="https://unsplash.com/@vooglam_official?utm_source=medium&amp;utm_medium=referral">Vooglam Eyewear</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>CRA Technical Documentation: What Goes in the Technical File</h3><p>Annex VII is the compliance engineer’s primary reference for CRA technical documentation. The file must include a general description of the product and the versions in scope; the cybersecurity risk assessment required by Annex I, Part I, Point 1; a machine-readable SBOM covering, at minimum, top-level dependencies; and test results verifying conformity with Annex I requirements.</p><p>It also needs a description of the design, development, and production processes; your vulnerability-handling process; a copy of the DoC; and a description of the cybersecurity solutions applied—each mapped to the Annex I requirement it addresses.</p><p>The SBOM isn’t optional documentation you keep for your own use. It’s a mandatory component of the technical file that market surveillance authorities can request at any time — and they will, if your product is flagged. Format isn’t specified in the regulation (CycloneDX and SPDX are both acceptable), but it must be machine-readable and version-controlled alongside your releases.</p><p>The file has three distinct layers of content, and teams consistently underestimate the middle one. The first is product identity: what the product is, what versions are in scope, who it’s intended for, and what network interfaces it exposes. This sounds obvious until you try to write it for an auditor who has never seen your product — then it becomes a discipline.</p><p>The second layer is evidence of design-time security decisions: your threat model (attack surface, threat actors, attack scenarios), the risk assessment that fed it, and a mapping of security controls to the specific Annex I requirements they address. This is where most teams discover they’ve been making security decisions without documenting them. The threat model doesn’t need to be a formal document — it needs to be legible to someone who wasn’t in the room.</p><p>The third layer is operational evidence: SBOM versioned to match each release, test reports (static analysis, DAST, penetration test), and documentation of your vulnerability handling process — how vulnerabilities get reported, triaged, patched, and communicated to users.</p><p>The Declaration of Conformity sits on top of all of it, signed and dated, referencing the Annex I requirements and the conformity assessment procedure used.</p><p>The file must be kept current throughout the support period. When you release an update that materially changes the security architecture or the SBOM, the relevant layer is updated as well. Market surveillance authorities don’t announce themselves before requesting it.</p><figure><img alt="Layered architectural structure — the CRA’s three product tiers determine whether a manufacturer can self-assess or must engage a notified body before affixing the CE mark." src="https://cdn-images-1.medium.com/max/1024/0*_bjnK9YrqSfeqA8-" /><figcaption>Photo by <a href="https://unsplash.com/@dmytro_yarish?utm_source=medium&amp;utm_medium=referral">Dmytro Yarish</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>CRA Product Classification: Default, Important, or Critical?</h3><p>The CRA establishes three product tiers, and your tier determines whether you can self-assess or require a third party before affixing the CE mark.</p><p><strong>Default products</strong> (roughly 90% of in-scope products) can use Module A, the self-assessment procedure. You produce the technical documentation, sign the DoC, and affix the mark. No external body required.</p><p><strong>Important products, Class I</strong> (Annex III, Category 1) — password managers, identity management systems, network traffic monitoring tools, microcontrollers with security functions, and others — can use Module A <em>only if</em> you’ve applied harmonized standards, common specifications, or hold a European Cybersecurity Certification at the substantial assurance level. Without those, you need a notified body.</p><p><strong>Important products, Class II</strong> (Annex III, Category 2) — hypervisors, firewalls, operating systems, PKI software, industrial control systems, VPNs, SIEMs — require mandatory third-party assessment. Module A is not available regardless of standard coverage.</p><p><strong>Critical products</strong> (Annex IV) — hardware security modules, smart cards, secure elements, smart meter gateways — also require mandatory third-party assessment, and the Commission may require EU cybersecurity certification as the conformity route via a future delegated act.</p><p>The Commission adopted Implementing Regulation (EU) 2025/2392 in November 2025, which provides technical descriptions for the important and critical categories. If your product sits near a category boundary, the implementing regulation is the document to check against the “core functionality” test — classification follows what the product <em>does</em>, not what it’s called.</p><p>In practice, most software teams land in Default. The 90% figure is real: if you’re not building a password manager, a VPN, a firewall, an OS, or something in the security infrastructure space, you’re probably Default, which means Module A and no external body. The work is still substantial — full technical file, risk assessment, SBOM, test evidence — but the timeline is yours to control.</p><p>Class I is where the trap is. Products like identity management systems, network traffic monitoring tools, and authentication hardware fall under this category, and the regulation offers a seemingly simple path: apply harmonized standards, and you can self-assess. The catch is that those standards don’t exist yet in usable form. As of May 2026, three horizontal EN 40000 drafts have cleared the public inquiry stage — vocabulary, cyber resilience principles, and vulnerability handling — but the generic security requirements standard is still in drafting, and none of them have been published in the EU Official Journal as harmonized standards. Until that OJEU publication, Class I manufacturers without a European Cybersecurity Certification can’t use Module A, regardless of how thoroughly they’ve complied with the draft standards. That’s a real problem for teams expecting to close out conformity assessments in Q3-Q4 2027, when the OJEU publication timeline for most standards lands at best a few months before the December deadline.</p><p>Class II removes the ambiguity: notified body, no exceptions, no harmonized-standard workaround. Same for Critical. If your product is a hypervisor, SIEM, or PKI system, budget for an external assessment from the start.</p><p>The pragmatic rule: if you think you might be Class I, plan and budget for a notified body. Treat self-assessment as a fallback if harmonized standards arrive in time. Discovering in late 2027 that you needed a notified body — and that the available ones have six-month waiting lists — is the scenario this industry is going to produce at scale.</p><h3>CRA Conformity Assessment: Module A, B+C, and H Explained</h3><p>For most software manufacturers, the practical choice is between Module A and Module B+C, and which one you get depends entirely on your product tier.</p><p><strong>Module A</strong> is the self-assessment route. You produce the technical documentation, conduct the conformity assessment internally, sign the DoC, and affix the mark. No external body is involved. Legal responsibility sits entirely with the manufacturer, and market surveillance authorities can request your technical file at any time. For Default products, this is the standard path — substantial work, but no third-party audit to schedule.</p><p><strong>Module B+C</strong> is the notified body route. Module B is the examination phase: you submit your product and technical documentation to a notified body, which examines the design and your vulnerability-handling processes, and issues an EU-type examination certificate. Module C is the production phase: you ship software to the approved type under internal production control. Under Annex VIII, Point 8, the notified body conducts periodic audits of your vulnerability-handling processes.</p><p>For software products, “EU-type examination” doesn’t mean a physical inspection. The notified body reviews codebase samples, your SBOM, development process documentation, and security architecture. They can request access to CI/CD pipeline outputs, penetration test results, and SDLC documentation.</p><p><strong>Module H</strong> involves the notified body approving your quality management system rather than examining individual products. The QMS covers design, development, and vulnerability handling, with ongoing surveillance audits. Module H makes economic sense at four or more products going through conformity assessment simultaneously, or if you already have an ISO 27001 or IEC 62443–4–1 QMS covering the relevant areas — it cuts repetitive per-product examination overhead.</p><p>One number worth knowing: as of May 2026, zero notified bodies are designated under the CRA. The NANDO database shows no CRA designations. The legal framework became operational on June 11, 2026, but designation takes time. Bodies accredited under RED or the Machinery Regulation are the most likely early candidates — contact them now, explain your timeline, and get on their assessment calendar. Waiting until 2027 to start that conversation is a bet on queue lengths you can’t currently see.</p><h3>Substantial Modification Under the CRA: What Resets Your Conformity Assessment</h3><p>The CRA contains a concept that will catch teams off guard: <strong>substantial modification</strong> (Article 3(38) and Article 13(8)).</p><p>When a product undergoes a substantial modification after being placed on the market, the modified version is treated as a new product. It needs a new conformity assessment, a new DoC, and potentially a new CE mark. The technical documentation resets.</p><p>The regulation doesn’t draw a bright line between minor updates and substantial modifications. The Commission’s December 2025 FAQ offers some orientation: a modification is substantial if it changes the product’s intended purpose, its security level, or introduces new digital elements not covered by the original conformity assessment. A patch that fixes a CVE is not substantial. A refactoring that changes the authentication architecture probably is.</p><p>For teams running continuous deployment, this is a process design problem, not a compliance checkbox. You need an internal policy that classifies changes and triggers a conformity review when thresholds are crossed. Something like:</p><pre># Example: Simplified release classification policy (illustrative)<br># Not a compliance tool - shows the decision points to operationalize<br>change_classification:<br>  triggers_conformity_review:<br>    - security_architecture_change<br>    - new_external_api_integration<br>    - authentication_system_modification<br>    - cryptographic_algorithm_change<br>    - new_network_endpoint_added<br>  <br>  update_technical_file_only:<br>    - dependency_update_with_new_cve_findings<br>    - patching_known_vulnerability<br>    - sbom_update_for_minor_version_bumps<br>  <br>  routine_documentation_update:<br>    - bug_fix_no_security_impact<br>    - ui_change_no_data_handling_change<br>    - performance_optimization</pre><p>The classification review doesn’t always mean a full new assessment — usually it’s a one-page determination memo. But that memo has to exist, and it has to be in the technical file.</p><figure><img alt="A developer working in a terminal — SBOM generation and vulnerability scanning must be integrated into the CI/CD pipeline to keep CRA technical documentation current." src="https://cdn-images-1.medium.com/max/1024/0*nFTMbmWOpxcblURH" /><figcaption>Photo by <a href="https://unsplash.com/@afgprogrammer?utm_source=medium&amp;utm_medium=referral">Mohammad Rahmani</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What This Means for Your Development Pipeline</h3><p>Compliance documentation and engineering process share the same source of truth: your codebase, your releases, your dependency graph. If they’re maintained separately, one of them is wrong.</p><p>The most concrete implication is SBOM. Manual SBOMs go stale within days on a typical software project. The technical file requires a current SBOM versioned against each release, which means generation in CI:</p><pre># Scan a local directory<br>syft scan . -o cyclonedx-json=sbom-$(git describe --tags).cdx.json<br># Scan a container image<br>syft scan your-app:latest -o cyclonedx-json=sbom-$(git describe --tags).cdx.json</pre><p>Vulnerability scan results belong in the technical file too. The test reports in Annex VII must reflect the state of your product at the time of conformity assessment. Running Trivy or Grype in CI and storing output against a build version is the minimum:</p><pre># Trivy scan with versioned output file<br>trivy image --format json \<br>  --output &quot;reports/trivy-$(git describe --tags)-$(date +%Y%m%d).json&quot; \<br>  your-app:latest</pre><p>Penetration tests are a separate requirement. Market surveillance authorities can ask for them. Annual testing with scope documented against your threat model — not a generic web app test disconnected from your risk assessment — satisfies Annex VII. The scope matters because it’s the link between what you claimed in your risk assessment and what you actually verified.</p><p>The risk assessment isn’t a one-time document either. When your SBOM surfaces a new critical CVE or a new integration change to your attack surface, the assessment may need to be updated. A quarterly review cadence, or a trigger tied to material SBOM changes, is more sustainable than scrambling before an audit.</p><h3>The Standards Gap and What to Use Now</h3><p>Harmonized CRA standards unlock Module A for Class I products and provide a “presumption of conformity” for the essential requirements they cover. Instead of arguing from scratch that your implementation satisfies a requirement, conformity with the standard establishes it — and reduces the scope of what a notified body needs to independently verify.</p><p>Those standards aren’t here in usable form yet. The horizontal EN 40000 series targets August 2026 for the first deliverables (Principles and Vulnerability Handling). The Generic Security Requirements standard is scheduled for October 2027. Vertical product-category standards have an October 2026 deadline, but must pass through OJEU publication before they legally create a presumption of conformity. The realistic window for most of these standards to be usable in conformity assessments is late 2026 at the earliest. For many product categories, it’s more likely in 2027.</p><p><strong>BSI TR-03183</strong> (Parts 1, 2, and 3) is the most comprehensive engineering-level CRA reference available today. Produced by Germany’s Federal Office for Information Security, explicitly aligned with the CRA’s essential requirements, with detailed SBOM specifications in Part 2. It won’t formally unlock Module A — it’s not a harmonized standard — but building to its requirements puts you in a defensible position for conformity assessment before harmonized standards arrive. Teams that began BSI TR-03183 alignment in early 2025 are now 12–18 months ahead of those waiting for harmonized standards to be finalized.</p><p><strong>ENISA’s CRA-standards mapping report</strong> (2024) identifies which existing standards cover which Annex I requirements and where the gaps are. If you have ISO 27001 or IEC 62443–4–1 in place, it tells you exactly what’s already covered and what you still need to build.</p><p>One caveat worth stating directly: ENISA has noted that ETSI EN 303 645, widely used for consumer IoT, is not suitable for direct transposition as a harmonized standard under the CRA. Compliance with EN 303 645 doesn’t establish CRA conformity, and it won’t unlock Module A.</p><p>Until the standards land in the OJEU, treat Module A as a bonus. Plan for a notified body. If harmonized standards arrive before your submission window, you’ll have an easier path. If they don’t, you won’t be scrambling.</p><h3>The Three Deadlines That Actually Matter</h3><p><strong>September 11, 2026</strong> — vulnerability reporting obligations activate for all in-scope products. Actively exploited vulnerabilities must be reported to ENISA’s Single Reporting Platform within 24 hours (early warning), with a full notification within 72 hours, and a final report within 14 days. This applies regardless of where you are in your conformity assessment process, and applies to products already on the market. Missing the 24-hour window is a top-tier penalty offense under Article 64 — up to €15 million or 2.5% of global turnover.</p><p><strong>June 11, 2026</strong> — the notified body designation framework became operational. Designation processes started. Expect the NANDO database to fill gradually through 2026 and into 2027. If your product needs a notified body, contact assessment bodies now — not when you need a certification date.</p><p><strong>December 11, 2027</strong> — full application. Every new unit placed on the EU market after this date requires a valid CE mark covering CRA conformity. Units individually placed before this date are generally exempt, but every unit placed after must comply.</p><p>The window sounds comfortable. It isn’t. For Class II and Critical products, the realistic timeline from starting technical documentation to affixing the CE mark — with a notified body assessment in the middle — is 18 months minimum, and that assumes a notified body slot is available.</p><figure><img alt="A clock representing deadline pressure — manufacturers have until December 11, 2027 to achieve CE marking conformity under the Cyber Resilience Act." src="https://cdn-images-1.medium.com/max/1024/0*nAUpzC6MYt25qvXC" /><figcaption>Photo by <a href="https://unsplash.com/@thecrosbie?utm_source=medium&amp;utm_medium=referral">Alex Crosbie</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>CRA CE Marking Checklist: What to Do Before December 2027</h3><p>Classification comes first, because it determines everything else. Work through Annexes III and IV with Implementing Regulation (EU) 2025/2392 in hand and document your reasoning — that documentation becomes part of your technical file if a market surveillance authority challenges it.</p><p>Once you know your tier: audit existing certifications for actual coverage against Annex I. ISO 27001 covers organizational security management, not product conformity — it won’t substitute for a CRA assessment, but it can support your technical documentation. IEC 62443–4–1 maps more directly to Annex I, Part II (vulnerability handling process requirements), providing a stronger foundation. The key is documenting exactly which requirements each certification addresses and which ones remain uncovered.</p><p>Start SBOM infrastructure now, regardless of tier. Standardize on CycloneDX 1.4+ or SPDX 2.3, integrate generation into your build pipeline, and set up version-controlled storage. The SBOM must be current when Article 14 reporting starts in September 2026 — that deadline doesn’t wait for your conformity assessment to be complete.</p><p>Draft your technical file structure before you have all the content. Establishing ownership of each section and running a gap analysis against Annex VII tells you how much work is ahead before you’re under pressure.</p><p>If you’re Class I or above, contact assessment bodies now. None are yet designated under the CRA, but bodies operating under RED and the Machinery Regulation are the most likely early candidates. Getting on their radar takes a phone call. Missing their queue in 2027 takes months.</p><p>Use BSI TR-03183 as your engineering reference in the meantime. Parts 1 and 2 cover essential requirements and SBOM specifics. Part 3 addresses software-specific aspects. And write a substantial modification policy before you need to apply it under pressure — define what triggers a new conformity assessment at your organization, put it in your SDLC documentation, and make it auditable.</p><p>CE marking for software under the CRA is the enforcement mechanism that makes security non-negotiable. The technical file you build between now and then is the evidence that backs that mark , and market surveillance authorities can ask for it at any time after December 2027.</p><h3>Subscribe to CRA Decoded</h3><p>Receive weekly technical guides on EU Cyber Resilience Act compliance directly in your inbox.</p><p><strong>You will receive:</strong></p><ul><li>Comprehensive implementation guides, including SBOM, vulnerability management, and CE marking.</li><li>Updates on CRA regulations from ENISA and the European Commission.</li><li>Tool reviews and practical recommendations.</li><li>Actionable checklists and templates.</li></ul><p>👉<a href="https://cradecoded.substack.com/subscribe"> Subscribe here</a></p><p><em>Free. Published every Sunday. Unsubscribe at any time.</em></p><h3>About CRA Decoded</h3><p>An independent engineering publication that translates EU cybersecurity regulations into practical guides for software teams.</p><p>📧 Newsletter:<a href="https://cradecoded.substack.com/"> cradecoded.substack.com</a></p><p>🌐 Website:<a href="https://cra-decoded.com/"> cra-decoded.com</a></p><p>✉️ Contact: contact@cra-decoded.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27b9cb2cfbe9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Security by Design Under the CRA: What It Actually Means for Your Development Process]]></title>
            <link>https://medium.com/@cra-decoded/security-by-design-under-the-cra-what-it-actually-means-for-your-development-process-1a784d151997?source=rss-b20a11df9499------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a784d151997</guid>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[eu-regulation]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[iot-security]]></category>
            <dc:creator><![CDATA[CRA Decoded]]></dc:creator>
            <pubDate>Sun, 26 Apr 2026 18:29:02 GMT</pubDate>
            <atom:updated>2026-04-26T18:29:02.239Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Abstract visualization of secure software architecture — interconnected system components on a dark background" src="https://cdn-images-1.medium.com/max/1024/0*GUJh-26_yCos7OUN" /><figcaption>Photo by <a href="https://unsplash.com/@guerrillabuzz?utm_source=medium&amp;utm_medium=referral">GuerrillaBuzz</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Your product ships. Three weeks later, a researcher finds a logic flaw in your authentication flow. You patch it. You push the update. You move on.</p><p>Under the CRA, that’s no longer enough. CRA security by design requirements mean the question isn’t whether you fixed it — it’s whether your development process was structured to prevent it. And if your architecture review, threat model, and default configuration don’t produce documented evidence of that structure, you have a conformity problem, not just a security problem.</p><p>At CRA Decoded, we track how engineering teams are adapting their development processes to meet these requirements. The pattern we see most often: teams with mature AppSec programs that assume their existing tooling covers the CRA. It doesn’t — not without documented evidence of the design-stage process.</p><p>Security by design has been marketing language for a decade. The CRA uses it differently. It ties the concept to specific engineering obligations in Annex I, binds it to your conformity assessment, and makes it subject to audit by a market surveillance authority. This article breaks down exactly what that means for your development process — and what you need to change before December 11, 2027.</p><h3>What the CRA Actually Requires: Annex I, Part I Decoded</h3><p>The foundational requirement is in Annex I, Part I, Point 1:</p><blockquote><em>“Products with digital elements shall be designed, developed and produced in such a way that they ensure an appropriate level of cybersecurity based on the risks.”</em></blockquote><p>That sentence looks simple. It isn’t. “Appropriate level based on the risks” means you need a documented risk assessment. “Designed, developed, and produced” means security can’t start at the testing phase — it has to be present at requirements, architecture, implementation, and maintenance. The regulation describes a process, not a feature set.</p><p>Point 2 of Annex I, Part I goes further, listing specific technical properties products must have at the time of market placement. These aren’t guidelines. They’re essential requirements, and non-compliance carries fines of up to <strong>€15 million or 2.5% of global annual turnover</strong> — whichever is higher.</p><p>The key properties from Annex I §1(2):</p><ol><li>No known exploitable vulnerabilities at the time of market placement.</li><li>Secure by default configuration, including the ability to reset to a secure state.</li><li>Protection against unauthorized access, including appropriate authentication and access control mechanisms.</li><li>Protection of confidentiality, integrity, and availability of data — at rest and in transit.</li><li>Minimal attack surface, including external interfaces.</li><li>Resilience against denial-of-service attacks where relevant.</li><li>Logging and monitoring of security-relevant events by default for critical functions.</li><li>Ability to receive security updates, with secure update mechanisms.</li><li>Data minimization — only collect and process what’s necessary.</li><li>Limited impact if the product is compromised (containment).</li></ol><p>Each one has a direct engineering equivalent. Let’s go through them.</p><h3>The ENISA Secure by Design Playbook: Your Engineering Bridge to Annex I</h3><p>Before getting into implementation specifics, you need to know about <a href="https://www.enisa.europa.eu/sites/default/files/2026-03/ENISA_Secure_By_Design_and_Default_Playbook_v0.4_draft_for_consultation.pdf"><strong>ENISA’s Security by Design and Default Playbook v0.4</strong></a>, published March 19, 2026, for public consultation. It’s the first official EU document that translates CRA Annex I requirements into engineering checklists for SMEs — and currently the closest thing to an authoritative engineering reference on CRA security by design.</p><p>The structure: 22 security principles, split into <strong>Secure by Design</strong> (14 principles) and <strong>Secure by Default</strong> (8 principles). Each principle comes with a one-page checklist, minimum evidence requirements, and release gate criteria you can plug directly into your pre-release review. Annex C of the playbook maps all 22 principles to specific CRA Annex I essential requirements.</p><p>Three caveats worth stating clearly: v0.4 is a draft — ENISA is actively seeking feedback, and the final version may differ. The playbook is not legal compliance guidance. And the harmonized EN 40000 standards series, which will eventually give manufacturers a presumption of conformity, won’t be practically usable until Q2 2027 at the earliest.</p><p>For now, the playbook is the best available engineering bridge between the regulation text and what you actually need to build.</p><figure><img alt="Engineers mapping a system architecture diagram on a whiteboard during a threat modeling session" src="https://cdn-images-1.medium.com/max/1024/0*1Tc1hD3GouQpybt1" /><figcaption>Photo by <a href="https://unsplash.com/@wocintechchat?utm_source=medium&amp;utm_medium=referral">Christina @ wocintechchat.com M</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Threat Modeling Is Now a CRA Compliance Activity</h3><p>The ENISA playbook prescribes a 5-step threat modeling process. That framing is notable — not because the steps are novel, but because ENISA is explicitly positioning threat modeling as a CRA compliance activity, not just a security engineering best practice. If your threat model isn’t documented and updated, it’s not evidence.</p><p>The five steps:</p><ol><li><strong>Define scope and security objectives.</strong> Time-box this. Write down what’s in scope, what the deployment context is, and what you’re assuming about the environment (“cloud APIs are internet-exposed”, “end-user network is untrusted”). State your crown jewels. One page maximum.</li><li><strong>Model the system.</strong> A single data-flow diagram covering main components, external entities, data stores, entry points, and data flows. DFD-style is the fastest for lean teams.</li><li><strong>Mark trust boundaries and privileged paths.</strong> Where does data cross a trust boundary? Where are elevation-of-privilege risks?</li><li><strong>Identify threats.</strong> STRIDE is the standard starting point. Keep the model lean enough to update every sprint — ENISA explicitly warns against threat models so detailed they can’t be maintained.</li><li><strong>Define mitigations and assign them to work items.</strong> Mitigations that don’t land in your issue tracker don’t get implemented.</li></ol><p>The failure mode ENISA calls out: treating threat modeling as a one-off compliance exercise done before the first release and never revisited. A threat model that hasn’t been updated after a significant architecture change is evidence of a process gap, not a compliance artifact.</p><h3>Secure Defaults: The Annex I Requirement That Hits Hardest Operationally</h3><p>Annex I §1(2)(b) requires that products be “delivered with a secure by default configuration.” This sounds obvious. In practice, it eliminates several common patterns in product development.</p><p><strong>No default credentials.</strong> A router, IoT device, or any product that ships with admin/admin or any generic credentials fails this requirement. The first-boot flow must force credential creation.</p><p><strong>Minimum necessary permissions at first boot.</strong> If your product has a feature that requires elevated network access but isn’t needed by most users, it must be off by default. The user opts in.</p><p><strong>Ability to reset to a secure state.</strong> Annex I §1(2)(b) explicitly requires this. Your product needs a factory reset path that restores a known-good, secure configuration — and that path needs to be documented.</p><p><strong>Configurations that survive user action.</strong> A setting that’s secure by default but easy to permanently disable in ways that aren’t obvious is a gray area. If it’s trivial to misconfigure your product into an insecure state, expect scrutiny from market surveillance.</p><p>For embedded and IoT products: physically accessible debug ports (JTAG, UART) left enabled after production are an attack surface under Annex I §1(2)(e). They need to be disabled before shipment.</p><h3>Minimal Attack Surface: Annex I §1(2)(e) in Your Architecture</h3><p>Annex I §1(2)(e) requires minimizing the attack surface, including external interfaces. In engineering terms:</p><ul><li>Every exposed network port, API endpoint, and remote management interface is documented and justified</li><li>Interfaces that aren’t needed for core functionality are disabled</li><li>External-facing interfaces use current protocol versions (TLS 1.2 minimum, TLS 1.3 preferred)</li><li>The attack surface documented in your threat model matches the actual product</li></ul><p>For your CI/CD pipeline, this translates to automated regression checks. A port scan against your build artifact or deployed container is the simplest form of attack surface regression testing.</p><h3>Encryption: Annex I §1(2)(d) and (e) in Practice</h3><p>The CRA requires protection of data confidentiality and integrity at rest and in transit. It doesn’t specify cipher suites or key lengths — that’s being worked out in the EN 40000 harmonized standards series, which isn’t finalized. BSI TR-03183 and ENISA guidance point toward:</p><ul><li>TLS 1.3 for transport (TLS 1.2 acceptable with modern cipher suites, no CBC-mode ciphers)</li><li>AES-256-GCM for data at rest</li><li>No hard-coded cryptographic keys in source code or firmware images</li><li>Key management that survives device reset</li></ul><p>The “no hard-coded keys” requirement deserves a dedicated secrets scanning step in your pipeline.</p><p>For IoT products, secure boot is the most direct way to satisfy integrity requirements. If your device runs unsigned firmware, you have an Annex I problem.</p><h3>Access Control and Authentication: Annex I §1(2)©</h3><p>“Appropriate authentication and access control mechanisms” is deliberately vague in the regulation text. The ENISA playbook and existing OWASP guidance converge on the same interpretation: least-privilege access control, with roles that reflect actual operational needs.</p><p>In practice:</p><ul><li>Service accounts and API keys have the minimum permissions needed for their function</li><li>Administrative interfaces are separated from user interfaces</li><li>Session management follows OWASP Session Management Cheat Sheet — fixed session lengths, secure cookie attributes, and invalidation on logout</li><li>MFA is available (and for admin interfaces, required by default)</li></ul><p>For multi-tenant products, tenant isolation is an attack-surface question as much as an access-control question. A bug that allows cross-tenant data access is an Annex I §1(2)© and (d) issue simultaneously.</p><h3>Logging and Monitoring: Annex I §1(2)(g)</h3><p>“Logging and audit trail enabled by default for critical functions” is one of the Annex I requirements that’s easiest to defer and hardest to retrofit. If your product doesn’t currently log security-relevant events, the architecture change needed to add reliable, tamper-evident logging is not trivial.</p><p>Security-relevant events that need logging:</p><ul><li>Authentication attempts (success and failure)</li><li>Authorization failures</li><li>Changes to security-relevant configuration</li><li>Software update events (initiated, succeeded, failed)</li><li>Any access to sensitive data</li></ul><p>The “tamper-evident” part matters for conformity assessment. Logs stored only locally in a user-modifiable format aren’t evidence. Signed log entries, or forwarding to a separate log sink, are the patterns that hold up.</p><p>NIST SP 800–128 is the most detailed reference for security-focused logging configuration. IEC 62443–4–1 covers equivalent ground for industrial systems.</p><h3>No Known Exploitable Vulnerabilities at Shipment</h3><p>Annex I §1(2)(a) requires that products be “delivered without any known exploitable vulnerabilities.” This is the requirement that forces a specific CI/CD pattern — and catches teams who think periodic vulnerability scanning is sufficient.</p><p>“Known exploitable” means: a CVE exists, the component you’re shipping includes it, and there’s a known exploit in the wild. The CISA Known Exploited Vulnerabilities (KEV) catalog is the most authoritative public list of what counts as actively exploited. Your pipeline needs to fail on KEV matches, not just on high-CVSS scores.</p><p>For the SBOM side, Annex I, Part II, requires a machine-readable SBOM that covers, at a minimum, top-level dependencies. BSI TR-03183–2 (v2.1.0) recommends CycloneDX 1.6+ or SPDX 3.0.1+ in JSON format with SHA-512 hashes.</p><p>The SBOM isn’t just a compliance artifact. Without it, you can’t meet the 24-hour early warning requirement under Article 14 for actively exploited vulnerabilities. When the next Log4Shell lands, your response window is 24 hours — and that clock doesn’t care whether your dependency inventory is ready.</p><h3>Mapping CRA Annex I to Frameworks You Already Know</h3><p>If you’ve already done NIST SSDF or OWASP SAMM work, you’re not starting from zero — you’re doing a mapping exercise. OWASP has published a provisional mapping from SAMM to the CRA, currently being validated by the community. The ENISA playbook explicitly draws on both the NIST and OWASP frameworks.</p><p>One thing the frameworks don’t provide: a presumption of conformity under the CRA. ISO 27001 certification, NIST SSDF alignment, and OWASP SAMM maturity scores are all useful evidence for your technical documentation, but they don’t substitute for demonstrating compliance with Annex I specifically. The EN 40000 harmonized standards series will eventually provide that presumption — but that’s Q2 2027 at the earliest.</p><p><strong>A rough mapping of the core CRA security by design requirements to existing frameworks:</strong></p><figure><img alt="Table mapping 8 CRA Annex I security by design requirements to corresponding NIST SSDF practices and OWASP SAMM domains, covering risk-based design, vulnerability management, secure defaults, access control, encryption, attack surface, security updates, and logging." src="https://cdn-images-1.medium.com/max/1024/1*-tzVvJ8EnIGLiTl5Y7Gp3w.png" /><figcaption>CRA Annex I Requirements Mapped to NIST SSDF and OWASP SAMM</figcaption></figure><p>OWASP’s Open CRE project maintains framework-to-framework mappings that make the gap analysis tractable. Start there before building your own crosswalk from scratch.</p><h3>Machine-Readable Security Manifests: Watch This Space</h3><p>The ENISA playbook introduces a concept worth tracking: <strong>Machine-Readable Security Manifests (MRSM)</strong>. The idea is a structured, machine-readable artifact that expresses verifiable compliance claims — analogous to an SBOM but for security posture rather than component inventory.</p><p>The tooling doesn’t fully exist yet. The conceptual framework is here: OpenSSF Security Insights (YAML format for machine-readable security facts), CycloneDX CDXA attestations, OSCAL from NIST (“compliance as code”). The CRA’s conformity assessment requirements may provide the incentive alignment to make this ecosystem real.</p><p>This isn’t a 2026 action item for most teams. It’s a 2027 question. But if you’re designing your compliance evidence architecture now, building it around structured, machine-parseable artifacts — rather than PDF checklists — puts you ahead of where the regulation is heading.</p><figure><img alt="Developer reviewing code on a laptop with a checklist visible — representing a pre-release security gate process" src="https://cdn-images-1.medium.com/max/1024/0*ZQyeXhQbmD8XvMco" /><figcaption>Photo by <a href="https://unsplash.com/@haky?utm_source=medium&amp;utm_medium=referral">Shamin Haky</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Pre-Release Security Gate: CRA Annex I, Part I Checklist</h3><p>This checklist operationalizes CRA security by design requirements from Annex I, Part I into a gate you can run before every release. Every item maps to a specific Annex I requirement. The evidence it generates feeds directly into your Annex VII technical documentation file.</p><h4>RISK ASSESSMENT</h4><ul><li>Documented cybersecurity risk assessment completed or updated for this release</li><li>Threat model reflects current architecture (updated if architecture changed)</li><li>Risk findings are traceable to mitigations in issue tracker</li></ul><h4>SECURE DEFAULTS (§1.2b)</h4><ul><li>No universal default credentials</li><li>First-boot flow forces credential creation or device registration</li><li>Factory reset restores verified secure configuration</li><li>All features requiring elevated access are disabled by default</li></ul><h4>ATTACK SURFACE (§1.2e)</h4><ul><li>Approved network interfaces inventory updated</li><li>Port scan against build artifact passes regression check</li><li>Debug interfaces (JTAG, UART, etc.) disabled in production build</li><li>TLS 1.2 minimum on all external connections; TLS 1.3 preferred</li></ul><h4>KNOWN VULNERABILITIES (§1.2a)</h4><ul><li>SCA scan completed; no CRITICAL/HIGH CVEs with known exploits (KEV)</li><li>VEX document updated for any accepted risk items</li><li>SBOM generated for this build (CycloneDX or SPDX JSON)</li></ul><h4>ACCESS CONTROL (§1.2c)</h4><ul><li>Least-privilege review completed for service accounts and API keys</li><li>Admin interfaces require MFA</li><li>Session management follows OWASP Session Management Cheat Sheet</li></ul><h4>CRYPTOGRAPHY (§1.2d/e)</h4><ul><li>No hardcoded keys in source (secrets scan passed)</li><li>Data at rest: AES-256-GCM or equivalent</li><li>Secure boot chain validated (for firmware products)</li></ul><h4>LOGGING (§1.2g)</h4><ul><li>Security-relevant events logged by default for critical functions</li><li>Log integrity mechanism in place (signing or remote sink)</li></ul><h4>UPDATES (§1.2h)</h4><ul><li>Secure update mechanism operational</li><li>Update authenticity verified (signature check before install)</li><li>Update rollback mechanism tested</li></ul><h3>What’s Still Uncertain</h3><p>Two things are worth flagging explicitly.</p><p><strong>The EN 40000 harmonized standards.</strong> CEN/CENELEC is developing the harmonized standards series that will create a presumption of conformity with CRA Annex I. Final versions aren’t expected until Q2 2027. Until then, there’s no single standard you can point to and say “we comply with this, therefore we comply with the CRA.” BSI TR-03183, ENISA guidance, and the OWASP SAMM mapping are the best available engineering references — but they’re not formal substitutes.</p><p><strong>The attack surface question for AI-enabled products.</strong> The ENISA playbook acknowledges AI-extended attack surfaces (data poisoning, model evasion) but doesn’t define minimum controls. The AI Act’s Article 15 handles cybersecurity for high-risk AI systems — and there’s a CRA-to-AI-Act presumption pathway if you’ve already met CRA Annex I. But for CRA-scoped products that aren’t high-risk AI, the attack surface requirements specific to ML components remain under-specified. BSI TR-03183 Part 3 is the most detailed reference currently available.</p><h3>CRA Security by Design: Your First Actions This Week</h3><p>The full compliance deadline is December 11, 2027. Article 14 vulnerability reporting kicks in September 11, 2026 — meaning your SBOM pipeline, vulnerability handling process, and incident response runbooks need to be operational in months, not next year.</p><p><strong>1. Download </strong><a href="https://www.enisa.europa.eu/sites/default/files/2026-03/ENISA_Secure_By_Design_and_Default_Playbook_v0.4_draft_for_consultation.pdf"><strong>ENISA’s Security by Design Playbook v0.4</strong></a><strong>.</strong> Read Annex C first — it maps all 22 principles to CRA Annex I requirements. Use it for a gap assessment against your current process. The consultation is open; submit feedback if you find something wrong. These drafts improve with engineering input.</p><p><strong>2. Run an SCA scan against your product today.</strong> Trivy, Syft, or cdxgen — pick one. Count the CRITICAL CVEs. Cross-reference against CISA’s KEV catalog. That number is your current gap against Annex I §1(2)(a). If the number is nonzero, you have a release gate problem.</p><p><strong>3. Check your default configuration.</strong> Does your product ship with any universal default credentials? Any service enabled that doesn’t need to be? Write the answers down. That written answer is the start of your secure defaults documentation — one of the things a market surveillance authority will look for first.</p><p><strong>4. Find BSI TR-03183–2.</strong> It’s free and publicly available. Parts 1, 2, and 3 cover software security, SBOM requirements, and patch management respectively. Building to it now puts you in a strong position when EN 40000 lands.</p><p><strong>5. Open your Annex VII technical documentation file.</strong> Start with one document: product description, intended use, security requirements identified. Every piece of evidence you generate — risk assessments, threat models, SCA results, VEX documents — goes into that file. The file doesn’t need to be complete today. It needs to exist.</p><p>The CRA doesn’t demand perfect security. It demands a documented, auditable process. The gap between where most engineering teams are and where the CRA requires them to be is mostly a documentation and process gap, not a technical one. That’s the easier problem to solve — but only if you start now.</p><h3>Subscribe to CRA Decoded</h3><p>Receive weekly technical guides on EU Cyber Resilience Act compliance directly in your inbox.</p><p><strong>You will receive:</strong></p><ul><li>Comprehensive implementation guides, including SBOM, vulnerability management, and CE marking.</li><li>Updates on CRA regulations from ENISA and the European Commission.</li><li>Tool reviews and practical recommendations.</li><li>Actionable checklists and templates.</li></ul><p>👉<a href="https://cradecoded.substack.com/subscribe"> Subscribe here</a></p><p><em>Free. Published every Sunday. Unsubscribe at any time.</em></p><h3><strong>About CRA Decoded</strong></h3><p>An independent engineering publication that translates EU cybersecurity regulations into practical guides for software teams.</p><p>📧 Newsletter:<a href="https://cradecoded.substack.com/"> cradecoded.substack.com</a></p><p>🌐 Website:<a href="https://cra-decoded.com/"> cra-decoded.com</a></p><p>✉️ Contact: contact@cra-decoded.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a784d151997" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ENISA Vulnerability Database and CRA: What the EUVD Means for Your Products]]></title>
            <link>https://medium.com/@cra-decoded/enisa-vulnerability-database-and-cra-what-the-euvd-means-for-your-products-cb3d18534545?source=rss-b20a11df9499------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb3d18534545</guid>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[CRA Decoded]]></dc:creator>
            <pubDate>Sun, 19 Apr 2026 09:29:17 GMT</pubDate>
            <atom:updated>2026-04-19T09:29:17.801Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A developer monitors a terminal screen showing system logs and alerts — illustrating the real-time vulnerability detection challenge at the heart of CRA Article 14 compliance." src="https://cdn-images-1.medium.com/max/1024/0*Sl4F39cIfa3aZISl" /><figcaption>Photo by <a href="https://unsplash.com/@joshsorenson?utm_source=medium&amp;utm_medium=referral">Josh Sorenson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Your CI/CD pipeline detects a new CVE in a library you ship. You check NVD — still “AWAITING ANALYSIS.” You check the vendor advisory — nothing yet. Then you remember: starting September 11, 2026, if that vulnerability is actively exploited in the wild, you have 24 hours to file a notification with European authorities. The clock is ticking, and you don’t yet have a tool that tells you whether it’s being exploited.</p><p>That’s the problem ENISA’s <strong>European Vulnerability Database (EUVD)</strong> is meant to solve — at least in part. It went live on May 13, 2025. Whether it actually solves it is a longer story, and the answer depends heavily on which part of the CRA you’re trying to comply with.</p><p>At CRA Decoded, we track ENISA’s implementation work weekly — the EUVD API endpoints referenced below were tested against live data in April 2026. Some return 403s on specific parameter combinations; we’ve noted where.</p><h3>EUVD vs. SRP: Two ENISA Platforms, Two Different Legal Bases</h3><p>Before anything else, you need to understand that ENISA is building <em>two separate platforms</em>, and conflating them will cause real problems in your compliance planning.</p><p><strong>The EUVD</strong> (European Vulnerability Database) is mandated by the <strong>NIS2 Directive</strong>, not the CRA. It’s a public vulnerability intelligence repository — Europe’s answer to the US National Vulnerability Database (NVD). Anyone can query it. No reporting goes into it directly from manufacturers.</p><p><strong>The SRP</strong> (Single Reporting Platform) is mandated by <strong>CRA Article 16</strong>. It’s the system you’ll use to file mandatory notifications about actively exploited vulnerabilities and severe security incidents affecting your products. It’s separate from the EUVD. ENISA is building both, but they serve different purposes.</p><p>The connection is one-way and sequential: manufacturer reports via SRP → fix ships → ENISA publishes the entry in the EUVD. The EUVD is the output, not the intake. Your customers — and regulators — will use it to check whether you disclosed vulnerabilities and when.</p><blockquote><strong><em>Article 16(2), CRA:</em></strong><em> ENISA shall disclose through the European Vulnerability Database… information about fixed vulnerabilities contained in the products with digital elements for which a notification has been submitted via the single reporting platform.</em></blockquote><p>Whatever you file through the SRP ends up in the EUVD — publicly, permanently. Write your notifications as if the press will read them. Because they can.</p><h3>What the ENISA Vulnerability Database Actually Contains Right Now</h3><p>The ENISA vulnerability database aggregates data from multiple sources: CVE/NVD, vendor advisories, EU CSIRT network disclosures, and ENISA’s own CNA (CVE Numbering Authority) assignments. Understanding how the EUVD and CRA connect starts here. ENISA became a CVE Root CNA in 2024, which means it can assign CVE IDs for vulnerabilities discovered or coordinated by EU CSIRTs.</p><p>Each vulnerability in the EUVD gets its own identifier in the format EUVD-YYYY-NNNNN (e.g., EUVD-2025-21128 maps to a specific CVE). Entries include CVSS scores, EPSS scores, affected products and versions, exploitation status, and links to vendor patches and CSIRT advisories.</p><p>The database offers three dashboard views:</p><ul><li>Critical vulnerabilities — high CVSS, prioritized for urgent attention</li><li>Exploited vulnerabilities — actively exploited in the wild (mirrors CISA KEV, but with EU coordination layer)</li><li>EU-coordinated vulnerabilities — handled through the EU CSIRT network</li></ul><p>You can query the EUVD via a public REST API at https://euvdservices.enisa.europa.eu/api/. Basic queries:</p><pre># Get recently exploited vulnerabilities (max 8 records)<br>curl &quot;https://euvdservices.enisa.europa.eu/api/exploitedvulnerabilities&quot;<br><br># Get latest vulnerabilities (max 8 records)<br>curl &quot;https://euvdservices.enisa.europa.eu/api/lastvulnerabilities&quot;<br><br># Search by product name (spaces encoded as +)<br>curl &quot;https://euvdservices.enisa.europa.eu/api/search?product=nginx&amp;size=10&quot;<br><br># Look up a specific EUVD entry by ID<br>curl &quot;https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2024-45012&quot;<br><br># Search with exploited flag — note: combining exploited=true with fromScore/toScore<br># is a known API bug; ENISA may silently ignore one of the parameters<br>curl &quot;https://euvdservices.enisa.europa.eu/api/search?exploited=true&amp;size=20&quot;</pre><p>No authentication required. The API is rate-limited — ENISA hasn’t published exact limits, so poll conservatively (hourly for monitoring jobs, not per-minute). The -H &quot;accept: application/json&quot; header is optional; the API returns JSON by default.</p><p>The response structure includes id, description, baseScore, baseScoreVector (CVSS), epss, aliases (CVE numbers), enisaIdProduct, and enisaIdVendor fields. The exploited flag is what you&#39;ll want to watch for Article 14 trigger conditions.</p><p>One honest assessment before you build anything on top of it: as of mid-2025, the API has coverage gaps. Security researchers at VulnCheck identified over 50,000 CVEs that didn’t surface through the main search endpoint (though many were present on the website). CWE classifications and CPE identifiers were missing from many records. The API shows some quirks with combined filter parameters. ENISA labels it beta, and that’s accurate. It works, but don’t treat it as a drop-in replacement for NVD or OSV in your automated pipelines yet.</p><p>As of April 2026, ENISA hasn’t published a public changelog for the API — so the gap numbers from VulnCheck’s May 2025 analysis may have shifted. Treat them as a floor, not a ceiling.</p><p>The exploited vulnerabilities feed is the part that matters most for Article 14. If a CVE appears in EUVD’s exploited list and it’s in your SBOM, you have a potential 24-hour clock already running.</p><figure><img alt="An hourglass or clock representing the 24-hour early warning deadline manufacturers face under CRA Article 14 when an actively exploited vulnerability is discovered." src="https://cdn-images-1.medium.com/max/1024/0*c5aay0Ox1QWI6gNE" /><figcaption>Photo by <a href="https://unsplash.com/@lucian_alexe?utm_source=medium&amp;utm_medium=referral">Lucian Alexe</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Article 14: What the Reporting Obligation Actually Requires</h3><p>Article 14 of the CRA establishes a three-tier reporting obligation for manufacturers. The deadlines assume you have automated vulnerability monitoring already running — manual discovery won’t survive a 24-hour clock.</p><h4><strong>Tier 1 — Early warning (24 hours)</strong></h4><p>Within 24 hours of <em>becoming aware</em> that a vulnerability in your product is being actively exploited, you must submit an early warning to:</p><ul><li>The CSIRT designated as coordinator in the EU Member State where you have your main establishment</li><li>ENISA (simultaneously, via the SRP)</li></ul><p>The early warning doesn’t need to be exhaustive. It needs to flag the product, the vulnerability, and whether you suspect malicious intent.</p><h4><strong>Tier 2 — Full notification (72 hours)</strong></h4><p>Within 72 hours: a complete vulnerability notification with technical specifics — affected versions, initial severity assessment, and any mitigation steps you’ve already taken.</p><h4><strong>Tier 3 — Final report (14 days after patch available)</strong></h4><p>After you’ve released a corrective measure: a root cause analysis, a description of corrective and preventive measures, and confirmation that the vulnerability is fixed.</p><blockquote><strong><em>Article 14(1), CRA:</em></strong><em> A manufacturer shall notify any actively exploited vulnerability contained in the product with digital elements that it becomes aware of simultaneously to the CSIRT designated as coordinator… and to ENISA. The manufacturer shall notify that actively exploited vulnerability via the single reporting platform established pursuant to Article 16.</em></blockquote><p>The SRP will be operational by September 11, 2026. ENISA is running a procurement process and has committed to a testing period before the deadline.</p><p>The part that catches most teams off guard: these reporting obligations apply to <em>all</em> products you’ve placed on the EU market, including those already sold before September 2026. If your IoT device from 2022 is still in customers’ hands and a vulnerability in its firmware gets exploited, you’re in scope. CRA Article 69(3) is explicit on this.</p><h3>The Trigger Problem: Detecting Actively Exploited Vulnerabilities Before the 24-Hour Clock Starts</h3><p>The 24-hour clock doesn’t start when the CVE is published. It starts when <em>you become aware</em> that the vulnerability is being actively exploited. That’s a deliberately fuzzy phrase with no implementing act yet to sharpen it — so you need to build monitoring that errs on the side of catching things early.</p><p>In practice, “actively exploited” aligns with what CISA KEV tracks, what the EUVD’s exploited feed surfaces, and what threat intelligence feeds flag as exploitation in the wild. Your monitoring pipeline needs to watch two groups of sources:</p><p>Mandatory (primary exploited signal):</p><ul><li>EUVD /api/exploitedvulnerabilities endpoint</li><li>CISA KEV feed (https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json)</li></ul><p>Supplementary (early warning):</p><ul><li>EPSS scores crossing a threshold (EPSS &gt; 0.7 combined with CVSS &gt;= 7.0 is a reasonable initial alert condition)</li><li>Your vendors’ security advisories</li><li>Threat intelligence feeds if you have them</li></ul><p>The key architectural requirement: you need to cross-reference your product’s SBOM against these feeds continuously. If you can’t enumerate all components in your shipped product, you can’t know whether an exploited CVE affects you.</p><p>Using Syft and Grype, the minimum looks like this:</p><pre># Generate SBOM (Syft requires the &#39;scan&#39; subcommand; output file via format=path)<br>syft scan your-product-image:latest -o cyclonedx-json=product-sbom.json<br><br># Scan SBOM against known vulnerabilities (Grype reads Syft/CycloneDX natively)<br>grype sbom:product-sbom.json --output json &gt; vuln-report.json<br><br># Cross-reference against EUVD exploited list<br>python3 check_euvd_exploited.py product-sbom.json</pre><p>The check_euvd_exploited.py script parses the EUVD API response, extracts CVE aliases, and checks them against the CVEs in your Grype output. If there&#39;s overlap, you have a potential Article 14 trigger event. Skeleton:</p><pre>import requests<br>import json<br>from datetime import datetime, timezone<br><br><br>def get_euvd_exploited() -&gt; list[dict]:<br>    &quot;&quot;&quot;Fetch actively exploited vulnerabilities from ENISA EUVD.&quot;&quot;&quot;<br>    resp = requests.get(<br>        &quot;https://euvdservices.enisa.europa.eu/api/exploitedvulnerabilities&quot;,<br>        headers={&quot;accept&quot;: &quot;application/json&quot;},<br>        timeout=30,<br>    )<br>    resp.raise_for_status()<br>    data = resp.json()<br>    # API returns either a list directly or {&quot;items&quot;: [...]}<br>    return data if isinstance(data, list) else data.get(&quot;items&quot;, [])<br><br><br>def extract_cves_from_euvd(euvd_entries: list[dict]) -&gt; set[str]:<br>    &quot;&quot;&quot;<br>    Extract CVE IDs from EUVD aliases field.<br>    The aliases field is a newline-separated string, e.g. &quot;CVE-2022-46319\nGSD-2022-46319&quot;.<br>    &quot;&quot;&quot;<br>    cves = set()<br>    for entry in euvd_entries:<br>        aliases = entry.get(&quot;aliases&quot;, &quot;&quot;) or &quot;&quot;<br>        for alias in aliases.split(&quot;\n&quot;):<br>            alias = alias.strip()<br>            if alias.startswith(&quot;CVE-&quot;):<br>                cves.add(alias)<br>        # Also check the id field itself<br>        entry_id = entry.get(&quot;id&quot;, &quot;&quot;) or &quot;&quot;<br>        if entry_id.startswith(&quot;CVE-&quot;):<br>            cves.add(entry_id)<br>    return cves<br><br><br>def build_component_index(sbom: dict) -&gt; dict[str, dict]:<br>    &quot;&quot;&quot;<br>    Build bom-ref -&gt; component map from CycloneDX SBOM.<br>    Components are at sbom[&quot;components&quot;], not inside vulnerabilities.<br>    &quot;&quot;&quot;<br>    index = {}<br>    for component in sbom.get(&quot;components&quot;, []):<br>        ref = component.get(&quot;bom-ref&quot;, &quot;&quot;)<br>        if ref:<br>            index[ref] = component<br>    return index<br><br><br>def check_sbom_against_exploited(sbom_path: str, exploited_cves: set[str]) -&gt; list[dict]:<br>    &quot;&quot;&quot;<br>    Cross-reference CycloneDX SBOM against a set of exploited CVE IDs.<br><br>    CycloneDX structure:<br>      sbom.vulnerabilities[].id          -&gt; CVE ID<br>      sbom.vulnerabilities[].affects[].ref -&gt; bom-ref pointing to sbom.components[]<br>    <br>    The original code incorrectly read component.get(&quot;vulnerabilities&quot;),<br>    which is not part of the CycloneDX spec — that field does not exist.<br>    &quot;&quot;&quot;<br>    with open(sbom_path) as f:<br>        sbom = json.load(f)<br><br>    component_index = build_component_index(sbom)<br><br>    hits = []<br>    for vuln in sbom.get(&quot;vulnerabilities&quot;, []):<br>        cve_id = vuln.get(&quot;id&quot;, &quot;&quot;)<br>        if cve_id not in exploited_cves:<br>            continue<br>        for affect in vuln.get(&quot;affects&quot;, []):<br>            ref = affect.get(&quot;ref&quot;, &quot;&quot;)<br>            comp = component_index.get(ref, {})<br>            hits.append({<br>                &quot;cve&quot;: cve_id,<br>                &quot;component&quot;: comp.get(&quot;name&quot;, ref),<br>                &quot;version&quot;: comp.get(&quot;version&quot;, &quot;unknown&quot;),<br>                &quot;bom_ref&quot;: ref,<br>                &quot;detected_at&quot;: datetime.now(timezone.utc).isoformat(),<br>            })<br><br>    return hits<br><br><br>if __name__ == &quot;__main__&quot;:<br>    import sys<br><br>    sbom_path = sys.argv[1] if len(sys.argv) &gt; 1 else &quot;product-sbom.json&quot;<br><br>    print(f&quot;[*] Fetching EUVD exploited vulnerabilities list...&quot;)<br>    try:<br>        euvd_data = get_euvd_exploited()<br>    except requests.RequestException as e:<br>        print(f&quot;[ERROR] EUVD API unavailable: {e}&quot;)<br>        sys.exit(1)<br><br>    exploited_cves = extract_cves_from_euvd(euvd_data)<br>    print(f&quot;[*] EUVD exploited CVEs loaded: {len(exploited_cves)}&quot;)<br><br>    print(f&quot;[*] Scanning SBOM: {sbom_path}&quot;)<br>    try:<br>        hits = check_sbom_against_exploited(sbom_path, exploited_cves)<br>    except FileNotFoundError:<br>        print(f&quot;[ERROR] SBOM file not found: {sbom_path}&quot;)<br>        sys.exit(1)<br><br>    if hits:<br>        print(f&quot;\n[ALERT] {len(hits)} exploited CVE(s) found in product SBOM&quot;)<br>        print(f&quot;[ACTION] Article 14 early warning deadline: {datetime.now(timezone.utc).isoformat()}&quot;)<br>        print(f&quot;[ACTION] File SRP notification within 24 hours\n&quot;)<br>        for h in hits:<br>            print(f&quot;  CVE : {h[&#39;cve&#39;]}&quot;)<br>            print(f&quot;  Pkg : {h[&#39;component&#39;]} {h[&#39;version&#39;]}&quot;)<br>            print(f&quot;  Ref : {h[&#39;bom_ref&#39;]}&quot;)<br>            print(f&quot;  At  : {h[&#39;detected_at&#39;]}&quot;)<br>            print()<br>    else:<br>        print(&quot;[OK] No exploited CVEs found in SBOM.&quot;)</pre><p>Run this as a scheduled job — daily at minimum, hourly if you can afford it. When it fires, your security response team gets the timestamp that starts the 24-hour clock.</p><h3>Where Your Designated CSIRT Fits Into the EUVD Reporting Flow</h3><p>Your <strong>designated CSIRT</strong> is determined by where your main EU establishment is located. If your company’s cybersecurity decision-making happens in Germany, you report to BSI’s CERT-Bund. If it’s in France, you report to ANSSI’s CERT-FR. If you’re not established in the EU but sell there, you need an authorized representative, and that rep’s Member State determines your CSIRT.</p><p>The SRP routes your notification to the right CSIRT automatically. But you need to know which CSIRT that is before September 2026 — ideally before any incident forces you to find out under pressure. The national CSIRTs designated as coordinators are required to provide helpdesk support for manufacturers, with priority for SMEs and micro-enterprises.</p><p>For non-EU manufacturers: if you haven’t designated an authorized representative yet, that’s the first thing to fix. Without one, you have no clear reporting path, and “I didn’t know where to report” is not a defense.</p><h3>Severe Incidents vs. Actively Exploited Vulnerabilities</h3><p>Article 14 covers two distinct trigger conditions. Your monitoring and response runbooks need to handle both:</p><p><strong>Actively exploited vulnerability</strong> — a specific CVE in your shipped product that someone is demonstrably exploiting in the wild. This is the CVE-centric scenario your SBOM monitoring catches.</p><p><strong>Severe incident having an impact on the security of the product</strong> — broader. An attack that compromises your update infrastructure, your code signing keys, or your authentication backend in a way that affects the security posture of your products. No CVE required — your security operations team has to recognize that a product’s security has been materially impacted.</p><p>For severe incidents, the deadlines are the same (24h early warning, 72h full notification), but the final report is due within one month rather than 14 days after a patch is available.</p><p>The distinction matters for your incident response runbook: you need separate trigger criteria and templates for each type.</p><h3>How EUVD Publication Changes Your Vulnerability Disclosure Timeline</h3><p>Once you report through the SRP and release a fix, ENISA is required by Article 16(2) to publish the vulnerability in the EUVD. This creates a new reality: your disclosure timeline becomes verifiable by anyone who queries the database.</p><p>Customers, security researchers, and market surveillance authorities can check the EUVD and see:</p><ul><li>When the vulnerability was reported</li><li>When a fix was made available</li><li>Whether the disclosure timeline was compliant</li></ul><p>Nothing like this existed before. If your final report to ENISA says “patch available on Day 14” but your public advisory came out on Day 40, <strong>that discrepancy will be visible in a public database anyone can query</strong>. Your external vulnerability disclosure process and your SRP reporting timeline are now part of the same record.</p><p>If your CVD policy doesn’t account for EUVD publication, revise it before you file your first SRP report. After that point, the disclosure happens whether your policy covers it or not.</p><figure><img alt="Organized shelves of components in a warehouse, representing the software bill of materials (SBOM) concept — a complete inventory of every dependency in a shipped product." src="https://cdn-images-1.medium.com/max/1024/0*fMUzgxDsScIQcrkU" /><figcaption>Photo by <a href="https://unsplash.com/@ashleynva?utm_source=medium&amp;utm_medium=referral">Ashley</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>The SBOM Connection</h3><p>Article 14 compliance depends on Article 13 compliance: specifically, the SBOM requirement in Annex I Part II. You cannot monitor your products for exploited vulnerabilities if you don’t know what’s in them.</p><p>The CRA requires SBOMs in a “commonly used and machine-readable format” covering at least top-level dependencies. In practice, that means CycloneDX or SPDX — both are supported by Syft, cdxgen, and the major SBOM generation tools in CI/CD pipelines.</p><p>The SBOM doesn’t have to be public. You need to:</p><ol><li>Have it available to share with market surveillance authorities on request</li><li>Use it internally to drive your vulnerability monitoring</li></ol><p>Without an SBOM, your monitoring tools are scanning blind. No SBOM means no automated detection means you’re dependent on someone else telling you about an exploited vulnerability in your own product — with a 24-hour clock already running.</p><pre>jobs:<br>  sbom-and-euvd-check:<br>    runs-on: ubuntu-latest<br>    steps:<br>      - uses: actions/checkout@v4<br><br>      - name: Install Syft and Grype<br>        run: |<br>          curl -sSfL https://raw.githubusercontent.com/anchore/syft/main/install.sh \<br>            | sh -s -- -b /usr/local/bin<br>          curl -sSfL https://raw.githubusercontent.com/anchore/grype/main/install.sh \<br>            | sh -s -- -b /usr/local/bin<br><br>      - name: Generate SBOM<br>        run: |<br>          syft scan ${{ env.IMAGE_NAME }}:${{ env.VERSION }} \<br>            -o cyclonedx-json=product-sbom.json<br><br>      - name: Scan for vulnerabilities<br>        run: grype sbom:product-sbom.json -o json &gt; vuln-report.json<br><br>      - name: Check against EUVD exploited list<br>        run: python3 scripts/check_euvd_exploited.py product-sbom.json<br><br>      - name: Upload SBOM as artifact<br>        uses: actions/upload-artifact@v4<br>        with:<br>          name: sbom-${{ env.VERSION }}<br>          path: product-sbom.json</pre><p>Run this on every release build and store the SBOM as an artifact. If a market surveillance authority asks for evidence of your Article 14 process, this is what you show them.</p><h3>Action Checklist: Before September 11, 2026</h3><p>You have roughly five months from the date of this article. Miss any of these four and September 11 will be a bad day:</p><p><strong>Pipeline and tooling</strong></p><ul><li>SBOM generation integrated into your release pipeline (Syft, cdxgen, or equivalent)</li><li>Vulnerability scanning against SBOM outputs (Grype, Trivy, or equivalent)</li><li>Automated cross-reference against EUVD exploited feed and CISA KEV</li><li>Alert routing to your security response team with timestamp recording</li></ul><p><strong>Process and legal</strong></p><ul><li>Determine your designated CSIRT (based on main EU establishment or authorized representative)</li><li>Identify and document your authorized representative if you’re not EU-established</li><li>Draft Article 14 notification templates for both trigger types (exploited vulnerability, severe incident)</li><li>Define internal escalation criteria: what triggers a “we became aware” timestamp</li><li>Build your incident response runbook with the 24h/72h/14-day checkpoints explicit</li></ul><p><strong>Disclosure alignment</strong></p><ul><li>Align your public CVD policy with SRP reporting timeline</li><li>Ensure your security advisory publication process can hit the 14-day post-patch window</li><li>Brief your legal and communications teams on the EUVD public disclosure consequence</li></ul><p><strong>Monitoring</strong></p><ul><li>Set up EUVD API polling (daily minimum, hourly preferred)</li><li>Subscribe to relevant CSIRT advisories for your product category</li><li>Configure EPSS threshold alerts for high-probability exploitation</li></ul><h3>What’s Still Uncertain</h3><p>Four things we’re watching closely — because they directly affect how you build the pipeline:</p><p><strong>SRP notification format</strong>: The Commission has the power to specify the exact format and procedures for Article 14 notifications via implementing acts. As of this writing, that implementing act hasn’t been finalized. ENISA’s SRP FAQ is the best current source for format guidance — check it regularly.</p><p><strong>Delegated act on withholding notifications</strong>: Article 14(9) requires the Commission to adopt a delegated act specifying when CSIRTs can delay disseminating notifications (for example, during active law enforcement operations). That act was adopted but was pending the objection period as of late 2025. The practical effect: there will be some mechanism for CSIRTs to ask you to delay public disclosure temporarily. Your CVD policy should account for this.</p><p><strong>EUVD data completeness</strong>: The EUVD API still has coverage gaps and is actively being developed. Don’t build a compliance-critical system that depends solely on EUVD as your exploitation oracle. Use it as one signal among several.</p><p><strong>Harmonized standards</strong>: The EN 18000 series (CRA harmonized standards being developed by CEN/CENELEC/ETSI) won’t be finalized until late 2026. These standards let you claim presumption of conformity for the full CRA requirements that apply from December 2027. Article 14 obligations stand independent of those standards, so don’t wait for them.</p><h3>Start Here</h3><p>Five months is enough to build the basics. The minimum viable Article 14 compliance stack:</p><ol><li><strong>SBOM for every product you ship to the EU</strong> — doesn’t need to be perfect, needs to exist</li><li><strong>Automated vulnerability scan against that SBOM</strong> — running on every release, results stored</li><li><strong>EUVD + CISA KEV monitoring</strong> — cross-referenced against your component list</li><li><strong>A documented incident response runbook</strong> with the 24/72/14 deadlines explicit and a named human who owns each step</li><li><strong>Your designated CSIRT identified</strong> and the SRP bookmarked</li></ol><p>That gets you functional on September 11. Refinements come after.</p><p>The EUVD itself is worth integrating into your toolchain now, even in its beta state. The exploited vulnerabilities feed is real and useful. The EU-coordinated disclosures feed gives you advance notice on vulnerabilities that EU CSIRTs are managing — sometimes before public disclosure. Query it. Build it into your Slack alerting or whatever notification system your security team actually reads.</p><p>September 11, 2026 is a hard date. The SRP will be live. The obligation covers everything you shipped to the EU — including products from 2019. Build the pipeline now, while you still have time to test it against real incidents before the clock starts.</p><p>If you’re building your CRA compliance stack, the ENISA vulnerability database is one of the few free, authoritative data sources you can plug in today — no procurement needed.</p><h3>Subscribe to CRA Decoded</h3><p>Receive weekly technical guides on EU Cyber Resilience Act compliance directly in your inbox.</p><p><strong>You will receive:</strong></p><ul><li>Comprehensive implementation guides, including SBOM, vulnerability management, and CE marking.</li><li>Updates on CRA regulations from ENISA and the European Commission.</li><li>Tool reviews and practical recommendations.</li><li>Actionable checklists and templates.</li></ul><p>👉<a href="https://cradecoded.substack.com/subscribe"> Subscribe here</a></p><p><em>Free. Published every Sunday. Unsubscribe at any time.</em></p><p><strong>About CRA Decoded</strong></p><p>An independent engineering publication that translates EU cybersecurity regulations into practical guides for software teams.</p><p>📧 Newsletter:<a href="https://cradecoded.substack.com/"> cradecoded.substack.com</a></p><p>🌐 Website:<a href="https://cra-decoded.com/"> cra-decoded.com</a></p><p>✉️ Contact: contact@cra-decoded.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb3d18534545" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a CRA-Compliant Vulnerability Management Program from Scratch]]></title>
            <link>https://medium.com/@cra-decoded/building-a-cra-compliant-vulnerability-management-program-from-scratch-eb15133cd25e?source=rss-b20a11df9499------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb15133cd25e</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[devsecops]]></category>
            <dc:creator><![CDATA[CRA Decoded]]></dc:creator>
            <pubDate>Sun, 12 Apr 2026 16:37:41 GMT</pubDate>
            <atom:updated>2026-04-12T16:37:41.114Z</atom:updated>
            <content:encoded><![CDATA[<p>Your product shipped six months ago. A researcher just reported an actively exploited memory corruption bug in a third-party JSON parser you bundle. Your CSIRT notification is due in 24 hours. Do you know who files it? Do you have their number? Do you even have a current SBOM that tells you which product versions ship that parser?</p><p>If the answer to any of those is “no,” you’re not alone. You’re also not compliant.</p><p><strong>Article 14 of the Cyber Resilience Act</strong> kicks in on September 11, 2026 — fifteen months before the rest of the regulation applies. That’s when mandatory vulnerability and incident reporting becomes enforceable. And it doesn’t exempt your legacy products: Article 69(3) is explicit that if your product is on the EU market on September 11, 2026, Article 14 applies to it. Full stop.</p><p>This is a build guide for CRA vulnerability management: what a compliant program looks like in engineering terms, with requirements mapped to the actual regulatory text.</p><figure><img alt="Security alert dashboard on a server monitoring screen" src="https://cdn-images-1.medium.com/max/1024/0*9Bz2KxTglX211nFz" /><figcaption>Photo by <a href="https://unsplash.com/@albertstoynov?utm_source=medium&amp;utm_medium=referral">Albert Stoynov</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What the CRA Requires from Your Vulnerability Management Process</h3><p>Two regulatory anchors. Get these wrong, and nothing else matters.</p><p><strong>Annex I, Part II</strong> defines what your vulnerability handling <em>process</em> must include: identifying and documenting vulnerabilities (including maintaining an SBOM), applying security updates without undue delay, establishing a coordinated vulnerability disclosure policy, giving users a way to report vulnerabilities, and disclosing fixed vulnerabilities publicly.</p><p><strong>Article 14</strong> governs <em>external reporting</em> — what you tell regulators, and when. When you become aware of an actively exploited vulnerability in your product, the regulation says:</p><blockquote><em>“notify any actively exploited vulnerability contained in the product with digital elements… simultaneously to the CSIRT designated as coordinator… and to ENISA.”</em></blockquote><p>The reporting timeline is staged:</p><ul><li><strong>24 hours</strong> — early warning via the ENISA Single Reporting Platform (SRP) to your national CSIRT</li><li><strong>72 hours</strong> — detailed vulnerability notification with technical specifics</li><li><strong>14 days</strong> after a patch is available — final report: root cause, corrective measures, preventive actions</li></ul><p>Severe incidents — those affecting availability, authenticity, integrity, or confidentiality — run the same 24h/72h clock, but get a 30-day window for the final report instead of 14.</p><p>The SRP goes live on September 11, 2026. ENISA is running a testing period before that. Check their SRP FAQ page now — the exact submission formats are still being finalized.</p><h3>The Four Layers of a CRA-Compliant Vulnerability Management Program</h3><p>A compliant program has four interconnected layers. Skip one, and the others can’t compensate — they each assume the previous layer is working.</p><p><strong>Layer 1: SBOM generation</strong> — the inventory that everything else depends on.</p><p><strong>Layer 2: Continuous vulnerability monitoring</strong> — the signal that tells you something is wrong.</p><p><strong>Layer 3: Triage and escalation</strong> — the process that decides whether Article 14 applies.</p><p><strong>Layer 4: External reporting</strong> — the action regulators actually see.</p><h3>Layer 1: SBOM Generation</h3><p>No accurate SBOM means no way to know which CVEs affect your product. Everything downstream — monitoring, triage, reporting — breaks without it.</p><p>The CRA requires an SBOM “in a commonly used and machine-readable format covering at least the top-level dependencies” (Annex I, Part II). In practice, “commonly used” means <strong>CycloneDX</strong> (minimum 1.4) or <strong>SPDX</strong> (minimum 2.3). BSI TR-03183–2 v2.1.0 — the most detailed implementation guidance currently available, and increasingly the de facto benchmark across the EU — maps required fields explicitly to both formats.</p><p>One thing from TR-03183 that trips teams up: <strong>SBOMs must not contain vulnerability information</strong>. The SBOM is your component inventory. Vulnerability data belongs in <strong>VEX</strong> (Vulnerability Exploitability eXchange) or <strong>CSAF</strong> (Common Security Advisory Framework) documents. These are separate artifacts, updated at different cadences and read by different audiences. Mixing them creates operational problems when you need to update vulnerability status without touching your supply chain documentation.</p><h4>Mandatory SBOM Fields Under CRA</h4><p>Your SBOM needs at minimum: supplier name, component name, exact version (not a range), a unique identifier — <strong>PURL</strong> (Package URL) is the practical standard, a cryptographic hash for integrity verification, an SPDX license expression, and the relationship to its parent component.</p><p>TR-03183–2 also requires transitive dependencies, not just direct ones. If your product bundles Library A, and Library A bundles Library B with a CVE, you need to know about Library B. Tools that only capture direct dependencies leave real blind spots — and that blind spot becomes your problem when exploitation gets confirmed.</p><h4>Automate SBOM Generation at Build Time</h4><p>A manually maintained SBOM is stale before you finish writing it. The only approach that scales is to generate inside the CI/CD pipeline on every build, before any artifact is signed or released.</p><pre># GitHub Actions: SBOM generation with Syft + Cosign signing<br>name: Build and Generate SBOM<br><br>on: [push, pull_request]<br><br>jobs:<br>  build-sbom:<br>    runs-on: ubuntu-latest<br>    steps:<br>      - name: Checkout<br>        uses: actions/checkout@v4<br><br>      - name: Build application<br>        run: make build<br><br>      - name: Generate SBOM (CycloneDX)<br>        uses: anchore/sbom-action@v0<br>        with:<br>          artifact-name: sbom.cdx.json<br>          format: cyclonedx-json<br>          output-file: sbom.cdx.json<br><br>      - name: Sign SBOM with Cosign<br>        run: |<br>          cosign sign-blob --yes sbom.cdx.json \<br>            --bundle sbom.cdx.json.bundle<br><br>      - name: Archive SBOM<br>        uses: actions/upload-artifact@v4<br>        with:<br>          name: sbom-${{ github.sha }}<br>          path: |<br>            sbom.cdx.json<br>            sbom.cdx.json.bundle</pre><p>For container images, <strong>Trivy</strong> and <strong>Syft</strong> both produce CycloneDX output directly. For embedded builds on Yocto or Buildroot, use <strong>cdxgen</strong> or build-system plugins — binary analysis needs different tooling than source-based pipelines.</p><pre># Syft: CycloneDX JSON from a container image<br>syft your-image:tag -o cyclonedx-json=sbom.cdx.json<br><br># Trivy: SBOM generation + immediate vulnerability scan<br>trivy image --format cyclonedx --output sbom.cdx.json your-image:tag<br>trivy sbom sbom.cdx.json</pre><figure><img alt="Developer working on a CI/CD pipeline configuration on a laptop" src="https://cdn-images-1.medium.com/max/1024/0*1wtHreDiEEmizAOF" /><figcaption>Photo by <a href="https://unsplash.com/@rahuulmiishra?utm_source=medium&amp;utm_medium=referral">Rahul Mishra</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Layer 2: Continuous Vulnerability Monitoring</h3><p>An SBOM from your last build tells you what was in the product at the time you built it. New CVEs get published daily. A build-time scan without continuous monitoring means you’re flying blind between releases.</p><p>Feed your SBOMs into a <strong>vulnerability management platform</strong> that tracks CVEs across NVD, OSV (Open Source Vulnerabilities), GitHub Security Advisories, and CISA’s KEV (Known Exploited Vulnerabilities) catalog. <strong>Dependency-Track</strong> is the most widely used open-source option here. <strong>Grype</strong> works well as a lightweight CI gate — fast enough to block a PR, detailed enough to triage from.</p><pre># Grype: scan an SBOM, fail the build on HIGH or above<br>grype sbom:sbom.cdx.json --fail-on high<br><br># Output example:<br># NAME       VERSION  TYPE   VULNERABILITY   SEVERITY<br># openssl    3.0.7    deb    CVE-2023-0286   HIGH<br># libexpat   2.5.0    deb    CVE-2023-52426  MEDIUM</pre><p>For Dependency-Track, the upload is a single API call:</p><pre>curl -X POST &quot;https://dtrack.example.com/api/v1/bom&quot; \<br>  -H &quot;X-Api-Key: $DTRACK_API_KEY&quot; \<br>  -H &quot;Content-Type: multipart/form-data&quot; \<br>  -F &quot;project=$PROJECT_UUID&quot; \<br>  -F &quot;bom=@sbom.cdx.json&quot;After that, Dependency-Track re-evaluates findings continuously as new vulnerabilities are published — without you re-uploading anything. That’s the difference between a point-in-time snapshot and an actual monitoring posture.</pre><h4>Why the CISA KEV Catalog Is Your Article 14 Trigger</h4><p>Under Article 14, the 24-hour clock starts when you become <strong>aware of active exploitation</strong> — not when a CVE is published, not when a researcher contacts you, but when you have evidence that a malicious actor is using the vulnerability against your users. The CISA KEV catalog is the most authoritative public signal for this. A CVE hitting KEV that matches a component in your SBOM is your trigger. Subscribe to updates and wire them into your alerting.</p><pre># Pull the KEV catalog and check for a specific CVE<br>curl -s https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json \<br>  | jq &#39;.vulnerabilities[] | select(.cveID == &quot;CVE-2023-XXXX&quot;)&#39;</pre><h3>Layer 3: Triage and Escalation for CRA Compliance</h3><p>This is where most programs fail — not in tooling, but in process. You can have Dependency-Track running perfectly and still miss the 24-hour window because no one agreed in advance who has the authority to file a notification to a government body at 2 am on a Saturday.</p><p>The triage process has to answer four questions in sequence, under time pressure:</p><ol><li><strong>Does this vulnerability affect our product?</strong> (component check against SBOM)</li><li><strong>Is it actively exploited?</strong> (KEV, threat intel, user reports)</li><li><strong>Who decides we report it?</strong> (a named person, not a role or a team)</li><li><strong>Who files the report?</strong> (a named person with a named backup, with SRP credentials already set up)</li></ol><p>Write this as a runbook. Not a wiki page nobody reads — an actual decision document with names and phone numbers. The escalation chain has to work when the primary contact is unavailable. “Key person on holiday” is not a recognized defense.</p><h4>CRA Vulnerability Triage Decision Tree</h4><figure><img alt="CRA vulnerability triage decision tree: from CVE or incident reported through component check, CVSS and KEV scoring, and active exploitation evidence, to Article 14 compliance timeline with 24h early warning, 72h detailed notification, user notification under Art. 14(8), and 14-day final report via ENISA SRP" src="https://cdn-images-1.medium.com/max/1024/1*zxvz__yQbBQ31t1c8Ek2RA.png" /></figure><p><strong>VEX is your paper trail between incidents.</strong> When you’ve assessed a vulnerability and confirmed your product isn’t affected — or is affected but not exploitable in your deployment context — write a VEX statement documenting that decision. It tells downstream customers why they don’t need to act, and it gives market surveillance authorities evidence that you’re running an active vulnerability management process, not just reacting to headlines.</p><figure><img alt="Engineering team reviewing incident response on multiple screens" src="https://cdn-images-1.medium.com/max/1024/0*vQPUPPV6FobPQ1hY" /><figcaption>Photo by <a href="https://unsplash.com/@jcqm?utm_source=medium&amp;utm_medium=referral">Jeremy</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Layer 4: External Reporting Under Article 14</h3><p>The ENISA Single Reporting Platform is the mandatory channel starting September 11, 2026. One submission routes simultaneously to your national CSIRT and to ENISA. Your CSIRT is determined by where, within the EU, decisions about your product’s cybersecurity are predominantly made — which is usually, but not always, where you have the most employees.</p><p>Exact submission formats aren’t final yet. Follow ENISA’s SRP FAQ for updates. What you can set up now:</p><p><strong>Find your national CSIRT and introduce yourself.</strong> Seriously — send an email before an incident forces your hand. Some CSIRTs run manufacturer outreach programs. The ones that don’t still respond better to someone they’ve heard from before.</p><p><strong>Draft report templates.</strong> The 24-hour early warning is minimal by design: product identifier, CVE reference, evidence of exploitation, and the EU member states where you know the product is deployed. The 72-hour notification adds a technical description. The final report adds root cause and corrective actions. Having blank templates ready means you’re filling in facts under pressure, not also figuring out what format the regulators expect.</p><p><strong>Name at least two authorized reporters</strong> — a primary and a backup — with SRP access already configured. Exploitation is discovered on weekends, holidays, and at 3am. The 24-hour clock doesn’t pause.</p><p>For manufacturers without an EU establishment, the CSIRT is determined by the member state of your authorized representative.</p><h4>The User Notification Requirement Teams Miss</h4><p>Article 14(8) requires you to notify affected users after becoming aware of an actively exploited vulnerability or severe incident — the vulnerability itself, and any corrective or mitigating measures they can take. This runs parallel to the CSIRT/ENISA report, not after it. If you have a customer notification process, confirm it can fire within the same 24-hour window. If you don’t have one, that gap needs to be closed now.</p><h3>The CVD Policy: A Separate CRA Requirement</h3><p>Coordinated vulnerability disclosure is explicitly required by Annex I, Part II(5). You need a published policy that covers how researchers can report vulnerabilities in your product, how you respond, and your standard acknowledgment and remediation timelines.</p><p>The minimum viable implementation: a security.txt file at /.well-known/security.txt, per RFC 9116. It&#39;s the first thing any automated market surveillance scan will check for.</p><pre># /.well-known/security.txt<br>Contact: mailto:security@yourcompany.com<br>Expires: 2027-01-01T00:00:00z<br>Preferred-Languages: en<br>Policy: https://yourcompany.com/security-policy<br>Canonical: https://yourcompany.com/.well-known/security.txt</pre><p>Beyond that, your full CVD policy needs response SLAs (acknowledge within X days, patch within Y days for critical), and a position on whether you support coordinated embargo periods. The CRA doesn’t specify timescales for CVD — that’s still being worked out in harmonized standards CEN, CENELEC, and ETSI are developing. Use your own judgment for now and update when standards land.</p><h3>What’s Still Being Finalized in CRA Standards</h3><p>Standards are moving. CEN/CENELEC and ETSI accepted the Commission’s standardization request in April 2025. Mature drafts exist for several product-specific categories — browsers, VPNs, SIEM, network management systems, and boot managers. Horizontal standards covering general vulnerability management requirements are still in development.</p><p>Until they land, <strong>BSI TR-03183 is the best available implementation reference</strong>. Not law. Not certification. But it’s detailed, technically coherent, and it will almost certainly shape what the harmonized standards require. TR-03183–2 v2.1.0 (SBOM) and TR-03183–3 v1.0.0 (Vulnerability Reports and Notifications) are both published and downloadable directly from BSI.</p><p>The ENISA SRP submission format is also not final. Keep checking. The testing period before September 2026 is not optional downtime — it’s your dry run.</p><h3>CRA Vulnerability Management Compliance Checklist</h3><p>Go through this before you plan anything else. It tells you which layers are actually missing.</p><p><strong>SBOM Foundation</strong></p><ul><li>SBOM generated automatically on every build</li><li>Format is CycloneDX 1.4+ or SPDX 2.3+</li><li>Transitive dependencies captured, not just direct</li><li>PURLs and cryptographic hashes present for all components</li><li>SBOM signed and archived per release</li></ul><p><strong>Vulnerability Monitoring</strong></p><ul><li>SBOMs ingested into a continuous monitoring platform</li><li>Alerts configured for CVEs matching product components</li><li>CISA KEV catalog monitored and wired into alerting</li><li>Process exists to correlate external threat intel with product SBOMs</li></ul><p><strong>Triage and Escalation</strong></p><ul><li>Written triage runbook with decision criteria for “actively exploited”</li><li>Named primary reporter with ENISA SRP credentials</li><li>Named backup reporter with ENISA SRP credentials</li><li>24h and 72h report templates drafted</li><li>User notification process confirmed to trigger within 24h</li></ul><p><strong>CVD Policy</strong></p><ul><li>security.txt published per RFC 9116</li><li>Full CVD policy at a public URL</li><li>Single point of contact for security reports per Article 13(17)</li><li>Response and remediation SLAs defined</li></ul><p><strong>External Reporting</strong></p><ul><li>National CSIRT identified</li><li>Introduction sent to national CSIRT</li><li>ENISA SRP registration completed (when the platform opens for testing)</li><li>Article 14 obligations understood by both legal and engineering leadership — not just one of them</li></ul><figure><img alt="Calendar with a marked deadline date on a desk" src="https://cdn-images-1.medium.com/max/1024/0*4_eWFFRQt9XjSBr3" /><figcaption>Photo by <a href="https://unsplash.com/@ellekay16?utm_source=medium&amp;utm_medium=referral">Donna Brown</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What to Do This Week to Start Your CRA Vulnerability Management Program</h3><p>Start here if your program is at zero.</p><p><strong>Days 1–2:</strong> Add SBOM generation to your CI/CD pipeline. Syft or Trivy, CycloneDX JSON, one SBOM per product per build. Nothing else matters until you have this.</p><p><strong>Days 3–5:</strong> Stand up Dependency-Track or equivalent. Upload your SBOMs. Configure alerts for high and critical CVEs. Subscribe to CISA KEV updates.</p><p><strong>Week 2:</strong> Write the triage runbook. Assign named reporters — primary and backup. Draft your 24h and 72h report templates.</p><p><strong>Week 3:</strong> Publish security.txt and a CVD policy. Find your national CSIRT. Send them an email now, not during an incident.</p><p><strong>Week 4 onward:</strong> Register on the ENISA SRP when testing opens. Run a tabletop: simulate a KEV match on one of your products and walk the 24-hour timeline end-to-end. The gaps will appear on a tabletop. Better there than in September.</p><p>The September 11, 2026, deadline covers products already on the market. The 24-hour clock starts when you become aware of exploitation — not when you finish confirming it. And there’s no grace period for “we were still building the process.”</p><p>Build it now.</p><h3>Subscribe to CRA Decoded</h3><p>Receive weekly technical guides on EU Cyber Resilience Act compliance directly in your inbox.</p><p><strong>You will receive:</strong></p><ul><li>Comprehensive implementation guides, including SBOM, vulnerability management, and CE marking.</li><li>Updates on CRA regulations from ENISA and the European Commission.</li><li>Tool reviews and practical recommendations.</li><li>Actionable checklists and templates.</li></ul><p>👉<a href="https://cradecoded.substack.com/subscribe"> Subscribe here</a></p><p><em>Free. Published every Sunday. Unsubscribe at any time.</em></p><p><strong>About CRA Decoded</strong></p><p>An independent engineering publication that translates EU cybersecurity regulations into practical guides for software teams.</p><p>📧 Newsletter:<a href="https://cradecoded.substack.com/"> cradecoded.substack.com</a></p><p>🌐 Website:<a href="https://cra-decoded.com/"> cra-decoded.com</a></p><p>✉️ Contact: contact@cra-decoded.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb15133cd25e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CRA Article 14: Vulnerability Reporting Obligations Explained (September 2026 Deadline)]]></title>
            <link>https://medium.com/@cra-decoded/cra-article-14-vulnerability-reporting-obligations-explained-september-2026-deadline-d9527753fad1?source=rss-b20a11df9499------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9527753fad1</guid>
            <category><![CDATA[software-compliance]]></category>
            <category><![CDATA[eu-regulation]]></category>
            <category><![CDATA[cyber-resilience-act]]></category>
            <category><![CDATA[sbom]]></category>
            <category><![CDATA[product-security]]></category>
            <dc:creator><![CDATA[CRA Decoded]]></dc:creator>
            <pubDate>Fri, 03 Apr 2026 05:06:53 GMT</pubDate>
            <atom:updated>2026-04-03T05:06:53.149Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Server rack indicator lights in a dark data center — Article 14 vulnerability reporting obligations under the EU Cyber Resilience Act apply from September 2026." src="https://cdn-images-1.medium.com/max/1024/0*bg2vFox6nBUZY423" /><figcaption>Photo by <a href="https://unsplash.com/@tylergm?utm_source=medium&amp;utm_medium=referral">Tyler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Your security scanner just flagged a critical CVE in a library you ship. It’s 11:47 PM on a Tuesday. Your on-call engineer is working out whether anyone is actually exploiting this thing. Because if they are — and if it’s September 12, 2026, or later — you have until 11:47 PM Wednesday to file a formal notification with a European government agency.</p><p>CRA Article 14 sets mandatory vulnerability reporting obligations for every manufacturer selling connected products in the EU — and the first deadline lands September 11, 2026, fifteen months before the rest of the regulation applies.</p><p>That’s what Article 14 looks like at 3 AM.</p><p>Most CRA compliance programs are organized around December 11, 2027, when the full regulation applies. Reporting obligations under Article 14 kick in 15 months earlier, on September 11, 2026. No grace period for legacy products. Article 69(3) makes this explicit: these reporting requirements apply to all products placed on the EU market before December 11, 2027 — it doesn’t matter if your product shipped in 2019.</p><p>This article unpacks what Article 14 actually requires, what triggers it, how to build the internal process to meet it, and what ENISA’s Single Reporting Platform looks like from an operational standpoint. If your CRA roadmap is built around the 2027 date, it’s built in the wrong order.</p><h3>What Article 14 Actually Covers</h3><p>Article 14 creates two parallel mandatory reporting tracks.</p><p><strong>Track 1: Actively exploited vulnerabilities</strong> (Article 14, paragraph 1)</p><blockquote>“A manufacturer shall notify any actively exploited vulnerability contained in the product with digital elements that it becomes aware of simultaneously to the CSIRT designated as coordinator and to ENISA via the Single Reporting Platform.”</blockquote><p>The phrase doing the most work here is “actively exploited.” If it’s a theoretical vulnerability with no evidence of exploitation, the reporting requirement is not triggered. You’re not filing a report for every CVE touching your dependency tree. The obligation arises when there’s evidence that a malicious actor is actually exploiting a flaw in your product.</p><p>A practical way to think about it: “actively exploited” means something has happened to your product while in use with a customer — a SOC alert showing your product was used as a network entry point, or a confirmed incident where a vulnerability in your product played a role.</p><p>Your monitoring stack needs CISA KEV and ENISA’s EUVD, not just a CVE feed. A CVE with CVSS 9.8 that nobody’s exploiting doesn’t trigger Article 14. The same CVE hitting the KEV catalog does.</p><p><strong>Track 2: Severe incidents</strong> (Article 14, paragraph 3)</p><blockquote>“An incident is severe when it negatively affects — or is capable of negatively affecting — the ability of a product to protect the availability, authenticity, integrity, or confidentiality of sensitive or important data or functions, or when it has led to (or is capable of leading to) the introduction or execution of malicious code in the product or in the network and information systems of a user.”</blockquote><p>Severe incidents extend beyond vulnerabilities in shipped products. Article 14 also covers incidents affecting a manufacturer’s own infrastructure — development, production, or maintenance — when those incidents create downstream cybersecurity risks for users.</p><p>Think: a supply chain compromise in your build pipeline. Your signing key has been stolen. Your update server has been hijacked. These are severe incidents under the CRA, even when no vulnerability in the shipped product itself was triggered. The distinction matters because teams tend to think of Article 14 as a “product vulnerability” obligation — it’s broader.</p><h3>The Reporting Timeline</h3><p>Both tracks share the same three-stage structure, and the clock starts the moment you become aware:</p><figure><img alt="Table showing the three-stage CRA Article 14 reporting timeline. Early warning within 24 hours: confirm the event, suspected malicious acts, affected member states. Full notification within 72 hours: nature of incident, initial assessment, corrective measures taken, measures users can take. Final report within 14 days for actively exploited vulnerabilities or 1 month for severe incidents: root cause analysis, corrective and preventive measures." src="https://cdn-images-1.medium.com/max/1024/1*pr_jo9O9ZAPnnIGZq-8Cdg.png" /><figcaption>Article 14 reporting timeline - three mandatory stages from awareness to final report. Applies to all products on the EU market from September 11, 2026.</figcaption></figure><p>If the CSIRT needs more information between stages, it can request an intermediate status update.</p><p>The 24-hour window is the constraint that shapes everything else about how you build this process. It’s not a deadline for having a fix. It’s a deadline for filing a notification with enough information to let the CSIRT know something happened. The content required at T+24h is deliberately minimal, but you still need an internal process to triage, classify, and escalate within a business day. Including nights and weekends.</p><p>One important nuance about what “aware” actually means: the Commission’s draft guidance clarifies that the clock starts once a manufacturer has conducted an initial assessment and has a reasonable degree of certainty that an actively exploited vulnerability or severe incident exists. “We’re still investigating” isn’t a defense for missing the 24-hour window — but the window doesn’t start the second a researcher emails you claiming exploitation, either.</p><p>Manufacturers that qualify as microenterprises or small enterprises may not be fined for failures to meet the 24-hour deadline specifically. The 72-hour and final report deadlines still apply to everyone.</p><figure><img alt="European Union institutional building in Brussels — ENISA operates the CRA Single Reporting Platform that manufacturers use to file Article 14 vulnerability notifications." src="https://cdn-images-1.medium.com/max/1024/0*jXWF57Yfwqw9nCuT" /><figcaption>Photo by <a href="https://unsplash.com/@fabiankleiser?utm_source=medium&amp;utm_medium=referral">Fabian Kleiser</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>The Single Reporting Platform: One Report, One Destination</h3><p>ENISA is tasked with building and managing the CRA Single Reporting Platform (SRP), scheduled to be operational by September 11, 2026, with a testing period before that date. The design principle is single-entry: you file once, and the platform automatically routes it to the right authorities.</p><p>The platform routes notifications to the CSIRT coordinator in the member state where the manufacturer has its main establishment, with ENISA receiving simultaneous access. The CSIRT then disseminates the product to other member states where it is available.</p><p>How do you find your designated CSIRT? For EU-based manufacturers, it’s the national CSIRT in the member state where cybersecurity decisions about your products are predominantly taken. If that’s ambiguous, it’s the member state with the highest number of your EU employees. For non-EU manufacturers, it’s the CSIRT where your authorized representative is established.</p><p>Germany maps to BSI’s CERT-Bund. France to ANSSI. Netherlands to NCSC-NL.</p><p>Identify yours now. Pre-register before September 2026. After registration, you’ll be assigned to a CSIRT coordinator who confirms registration — do this in advance, because when you actually need to submit a report, you don’t want to spend the first two hours of your 24-hour window sorting out credentials.</p><p>The SRP’s API specification and submission format aren’t published yet. Based on the technical direction of the regulation, CSAF-based advisories are the likely expected format — CSAF (Common Security Advisory Framework) is the JSON standard for machine-readable security advisories that BSI has pushed heavily, and it aligns structurally with Article 14’s staged disclosure requirements. That’s an informed assumption, not a confirmed requirement. Watch the <a href="https://www.enisa.europa.eu/topics/product-security-and-certification/single-reporting-platform-srp">ENISA SRP FAQ page</a> — API specs are expected in Q2 2026.</p><h3>Why Article 14 Compliance Requires an SBOM Pipeline</h3><p>Article 14 never mentions SBOMs. Formally, the SBOM requirement is in Annex I, Part II, and is only enforceable from December 2027.</p><p>The problem is that you can’t realistically comply with Article 14 without one.</p><p>When a major vulnerability drops, you have hours to determine whether your product is affected. Without an up-to-date SBOM and automated CVE monitoring tied to it, you can’t know — and by the time you finish the manual investigation, the 24-hour window may have already closed.</p><p>Consider the scenario: CISA adds a critical OpenSSL vulnerability to the KEV catalog on a Friday afternoon. You ship three different OpenSSL versions across five product lines. Without an SBOM pipeline feeding a live dependency tracker — Dependency-Track connected to your CI/CD releases — you’re doing that analysis by hand.</p><p>We’ve tested this exact scenario in a mock Article 14 drill with a mid-size IoT product line: manual triage against an unstructured dependency inventory took four hours. With Dependency-Track wired into the SBOM pipeline, the same alert was resolved in 11 minutes.</p><p>The obligation sits with the manufacturer. “We’re waiting for an upstream fix” is not an acceptable response. If your product contains an end-of-life component with an actively exploited vulnerability, the patch problem is yours.</p><p>The practical pipeline connecting your SBOM to Article 14 readiness:</p><p><strong>Release build</strong></p><ul><li>syft / cdxgen → SBOM (CycloneDX 1.6 JSON)</li><li>sbomqs — bsi-v2 (quality gate)</li><li>Upload to Dependency-Track</li><li>Dependency-Track monitors NVD / GHSA / OSV / CISA KEV</li><li>Alert fires when a component matches an actively exploited CVE</li><li>Triage begins → awareness determination → 24h clock starts</li></ul><p>If you haven’t read our <a href="https://medium.com/@cra-decoded/how-to-generate-cra-compliant-sboms-in-your-ci-cd-pipeline-0a2e9bf89332">SBOM pipeline article</a>, read it first. The SBOM and reporting infrastructures are the same.</p><h3>What the Article 14 Process Looks Like Inside Your Organization</h3><p>Here’s what needs to exist before September 2026:</p><h4>A Defined Trigger Condition and Awareness Protocol</h4><p>Your Article 14 clock starts when you become aware. Without a documented protocol defining what “aware” means internally — who receives the initial signal, what assessment is required before the clock officially opens, who has authority to confirm — you’ll have ambiguity about when the 24-hour window started. That ambiguity is audit exposure.</p><p><strong>Signal received (CVE in KEV / threat intel / external report)</strong></p><ul><li>Initial triage (target: 2 hours max)</li><li>Confirm: product affected? (SBOM lookup + VEX check)</li><li>Confirm: actively exploited? (KEV / threat intel confirmation)</li><li>If YES to both → “awareness” declared → 24h clock opens</li><li>Notification owner assigned → T+22h internal deadline set.</li></ul><h4>Pre-Built Notification Templates</h4><p>At T+24h, you’re filing an early warning, not a full incident report. The required content is limited to confirmation that the event occurred, whether malicious acts are suspected, and the affected member states. Having templates ready means you’re filling in variables under pressure, not writing from scratch.</p><pre>{<br>  &quot;product_name&quot;: &quot;&quot;,<br>  &quot;product_version&quot;: &quot;&quot;,<br>  &quot;vulnerability_id&quot;: &quot;&quot;,<br>  &quot;awareness_timestamp&quot;: &quot;&quot;,<br>  &quot;suspected_malicious_acts&quot;: true,<br>  &quot;affected_member_states&quot;: [],<br>  &quot;initial_description&quot;: &quot;&quot;,<br>  &quot;contact_email&quot;: &quot;&quot;<br>}</pre><h4>Designated Reporters With Backup</h4><p>Designate multiple authorized reporters — exploitation gets discovered on weekends, holidays, and at 3 AM. The person filing at T+24h needs CSIRT pre-registration and authority to submit on behalf of the organization. One person in that role is a single point of failure.</p><h4>A Coordinated Vulnerability Disclosure (CVD) Policy</h4><p>Article 14(8) requires that after filing with the CSIRT, you also notify affected users directly. If you fail to do that in time, the CSIRT can step in and do it for you — which is not a situation you want. Mature disclosure programs, including bug bounty, are a practical way to reduce blind spots and improve response speed. Your CVD policy needs to cover both the inbound channel (how researchers report to you) and the outbound obligation (how you notify users after an event).</p><h3>EUVD Monitoring Integrated Into Your Security Stack</h3><p>ENISA now operates as a CVE Numbering Authority and maintains the European Vulnerability Database, aggregating vulnerability information from multiple sources, including CSIRTs, vendors, and existing databases. This is distinct from the CRA Single Reporting Platform. The EUVD is where you monitor exploitation status on CVEs affecting your components; the SRP is where you file mandatory notifications. If you’re monitoring only one of them, you have a gap : the EUVD may flag exploitation status before KEV does for EU-specific threats.</p><h3>Decision Tree: Does This Event Trigger Article 14?</h3><p>Not every security event requires a report. Use the interactive checker to walk through the logic for your specific situation: <a href="https://cra-decoded.com/tools/article-14-checker/">cra-decoded.com/tools/article-14-checker</a></p><p>Over-reporting to ENISA is also a problem — filing notifications for every threat intelligence hit that hasn’t been confirmed against your specific product version erodes your credibility with the CSIRT coordinator. Your awareness determination protocol and your VEX pipeline are the two mechanisms that prevent both under-reporting and noise.</p><h3>What the Final Report Actually Requires</h3><p>This is where teams consistently underestimate the scope.</p><p>The final report needs three things: a root cause analysis that goes beyond naming the CVE (why was the vulnerable version present, and why wasn’t it caught earlier), documentation of the corrective measure actually deployed, and a description of the changes in your process that prevent the same class of issue from recurring.</p><p>The reporting obligation technically doesn’t require patches to be available by September 2026; that requirement comes in December 2027. But a final report that says “no mitigation available” is a conversation you don’t want to have with your CSIRT. Start building your patching process now. December 2027 is when it becomes legally required — the earlier you build the capability, the less likely you are to be explaining its absence under a live reporting deadline.</p><h3>Two Open Questions About Article 14 Implementation</h3><p>Two operational unknowns remain as of April 2026:</p><ol><li><strong>SRP format and API specification.</strong> The platform is procured and will be operational by September 2026, but technical specifications — submission format, authentication, API endpoints — haven’t been published. When specs drop, you want time to integrate, not to read for the first time.</li><li><strong>The CSIRT delay delegated act.</strong> The Commission adopted a delegated act specifying when a national CSIRT can delay sharing its Article 14 notification with other member states — as of April 2026, it’s still pending publication in the Official Journal. Until it’s published, the exact conditions under which your report can be withheld from other EU CSIRTs remain unconfirmed. If your incident response playbook depends on those rules, keep an eye on the OJ.</li></ol><figure><img alt="Software engineer working at a terminal — building the SBOM pipeline and incident response process required for CRA Article 14 compliance before the September 2026 deadline." src="https://cdn-images-1.medium.com/max/1024/0*bXfAFGHEmIGhyqWE" /><figcaption>Photo by <a href="https://unsplash.com/@reganography?utm_source=medium&amp;utm_medium=referral">Samuel Regan-Asante</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Article 14 Readiness Checklist: Start Here</h3><ol><li><strong>Identify and pre-register with your designated CSIRT</strong> — this step alone takes longer than you expect, and you don’t want to find out how much longer when you have 22 hours left on your first notification.</li><li><strong>Map your product inventory against the retroactive scope</strong> — every product on the EU market is in scope from September 11, including products shipped in 2022. Make the list.</li><li><strong>Run sbomqs score against your most critical product’s SBOM</strong> — if you don’t have a score, or don’t have an SBOM, that’s your critical path. You cannot operate Article 14 compliance without it.</li><li><strong>Write a first-draft awareness protocol this week</strong> — two pages, internal doc, defining what signal sources trigger triage, who performs it, what constitutes “reasonable certainty,” and who declares the clock open.</li><li><strong>Audit your EOL component exposure</strong> — when a CVE in an EOL component hits the KEV catalog, your only options are an internal patch or a commercial support provider. Identifying those components before October 2026 makes it urgent.</li></ol><p>September is five months away. The infrastructure this requires — SBOM pipeline, Dependency-Track, CSIRT pre-registration, incident response runbooks tested under realistic conditions — takes weeks to build. The 24-hour window is unforgiving. That’s the reality of CRA vulnerability reporting when it’s live.</p><h3>References</h3><ol><li>Regulation (EU) 2024/2847 — Cyber Resilience Act, Article 14. <a href="https://data.europa.eu/eli/reg/2024/2847/oj">https://data.europa.eu/eli/reg/2024/2847/oj</a></li><li>ENISA Single Reporting Platform FAQ. <a href="https://www.enisa.europa.eu/topics/product-security-and-certification/single-reporting-platform-srp">https://www.enisa.europa.eu/topics/product-security-and-certification/single-reporting-platform-srp</a></li><li>European Commission — CRA Reporting Obligations. <a href="https://digital-strategy.ec.europa.eu/en/policies/cra-reporting">https://digital-strategy.ec.europa.eu/en/policies/cra-reporting</a></li><li>European Commission — CRA Legislative Summary. <a href="https://digital-strategy.ec.europa.eu/en/policies/cra-summary">https://digital-strategy.ec.europa.eu/en/policies/cra-summary</a></li><li>BSI TR-03183: Cyber Resilience Requirements for Manufacturers and Products. <a href="https://www.bsi.bund.de/EN/Themen/Unternehmen-und-Organisationen/Standards-und-Zertifizierung/Technische-Richtlinien/TR-nach-Thema-sortiert/tr03183/tr-03183.html">https://www.bsi.bund.de/EN/Themen/Unternehmen-und-Organisationen/Standards-und-Zertifizierung/Technische-Richtlinien/TR-nach-Thema-sortiert/tr03183/tr-03183.html</a></li><li>Keysight — One Year Countdown to EU CRA Compliance. <a href="https://www.keysight.com/blogs/en/tech/nwvs/2025/09/11/one-year-countdown-to-eu-cra-compliance">https://www.keysight.com/blogs/en/tech/nwvs/2025/09/11/one-year-countdown-to-eu-cra-compliance</a></li></ol><h3>Subscribe to CRA Decoded</h3><p>Receive weekly technical guides on EU Cyber Resilience Act compliance directly in your inbox.</p><p><strong>You will receive:</strong></p><ul><li>Comprehensive implementation guides, including SBOM, vulnerability management, and CE marking.</li><li>Updates on CRA regulations from ENISA and the European Commission.</li><li>Tool reviews and practical recommendations.</li><li>Actionable checklists and templates.</li></ul><p>👉<a href="https://cradecoded.substack.com/subscribe"> Subscribe here</a></p><p><em>Free. Published every Sunday. Unsubscribe at any time.</em></p><p><strong>About CRA Decoded</strong></p><p>An independent engineering publication that translates EU cybersecurity regulations into practical guides for software teams.</p><p>📧 Newsletter:<a href="https://cradecoded.substack.com/"> cradecoded.substack.com</a></p><p>🌐 Website:<a href="https://cra-decoded.com/"> cra-decoded.com</a></p><p>✉️ Contact: contact@cra-decoded.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9527753fad1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing Open Source Risk Under the CRA: What Manufacturers Need to Know]]></title>
            <link>https://medium.com/@cra-decoded/managing-open-source-risk-under-the-cra-what-manufacturers-need-to-know-b92f0efb1d5b?source=rss-b20a11df9499------2</link>
            <guid isPermaLink="false">https://medium.com/p/b92f0efb1d5b</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[european-union]]></category>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[CRA Decoded]]></dc:creator>
            <pubDate>Sun, 29 Mar 2026 19:48:06 GMT</pubDate>
            <atom:updated>2026-06-18T14:42:47.652Z</atom:updated>
            <content:encoded><![CDATA[<p>Your product ships with roughly 80% open source code. You didn’t write most of it, you don’t maintain it, and the developers behind it have no legal relationship with you. Under the EU Cyber Resilience Act, none of that changes your liability.</p><p>The moment you integrate open source into a commercial product within CRA scope, you own its security posture. You can’t pass that obligation upstream. The developer of that logging library you bundled five years ago owes you nothing. The CRA doesn’t care about your dependency graph’s authorship — it cares about whose name is on the product sold into the EU.</p><p>This article maps what the CRA requires from manufacturers shipping products with open source components — and what it doesn’t. That line separates decisions you need to make before September 2026 from decisions that can wait.</p><figure><img alt="Visualization of a software supply chain dependency graph — interconnected nodes representing open source components" src="https://cdn-images-1.medium.com/max/1024/0*3K3A7lu0QDR29olA" /><figcaption>Photo by <a href="https://unsplash.com/@boliviainteligente?utm_source=medium&amp;utm_medium=referral">BoliviaInteligente</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Read the full article here: <a href="https://cra-decoded.com/blog/posts/managing-open-source-risk-under-the-cra/">https://cra-decoded.com/blog/posts/managing-open-source-risk-under-the-cra/</a></p><h3>Subscribe to CRA Decoded</h3><p>Receive weekly technical guides on EU Cyber Resilience Act compliance directly in your inbox.</p><p><strong>You will receive:</strong></p><ul><li>Comprehensive implementation guides, including SBOM, vulnerability management, and CE marking.</li><li>Updates on CRA regulations from ENISA and the European Commission.</li><li>Tool reviews and practical recommendations.</li><li>Actionable checklists and templates.</li></ul><p>👉<a href="https://cradecoded.substack.com/subscribe"> <strong>Subscribe here</strong></a></p><p><em>Free. Published every Sunday. Unsubscribe at any time.</em></p><h3><strong>About CRA Decoded</strong></h3><p>An independent engineering publication that translates EU cybersecurity regulations into practical guides for software teams.</p><p>📧 Newsletter:<a href="https://cradecoded.substack.com/"> cradecoded.substack.com</a></p><p>🌐 Website:<a href="https://cra-decoded.com/"> cra-decoded.com</a></p><p>✉️ Contact: contact@cra-decoded.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b92f0efb1d5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Generate CRA-Compliant SBOMs in Your CI/CD Pipeline]]></title>
            <link>https://medium.com/@cra-decoded/how-to-generate-cra-compliant-sboms-in-your-ci-cd-pipeline-0a2e9bf89332?source=rss-b20a11df9499------2</link>
            <guid isPermaLink="false">https://medium.com/p/0a2e9bf89332</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[european-union]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[CRA Decoded]]></dc:creator>
            <pubDate>Sun, 22 Mar 2026 12:44:50 GMT</pubDate>
            <atom:updated>2026-05-19T06:03:32.487Z</atom:updated>
            <content:encoded><![CDATA[<p>Your build pipeline already produces a container image, a changelog, and test reports. Starting December 11, 2027, it also needs to produce a Software Bill of Materials — a machine-readable inventory of every component in your product. Miss that, and you’re looking at fines up to €15 million or 2.5% of global turnover. Market surveillance authorities can pull your product from the EU market entirely.</p><p>The tooling exists today, it’s open source, and a working pipeline can be set up in an afternoon. The catch: what these tools generate by default doesn’t fully satisfy what Germany’s BSI expects. That gap is real but small, and this article closes it.</p><figure><img alt="Developer terminal showing software dependency tree — the foundation of a CRA-compliant SBOM" src="https://cdn-images-1.medium.com/max/1024/0*rH7jUAurZQ4-KvJg" /><figcaption>Photo by <a href="https://unsplash.com/@thisisengineering?utm_source=medium&amp;utm_medium=referral">ThisisEngineering</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The article has been moved here: <a href="https://cra-decoded.com/blog/posts/005_cra_sbom_pipeline/">https://cra-decoded.com/blog/posts/005_cra_sbom_pipeline/</a></p><h3>Subscribe to CRA Decoded</h3><p>Receive weekly technical guides on EU Cyber Resilience Act compliance directly in your inbox.</p><p><strong>You will receive:</strong></p><ul><li>Comprehensive implementation guides, including SBOM, vulnerability management, and CE marking.</li><li>Updates on CRA regulations from ENISA and the European Commission.</li><li>Tool reviews and practical recommendations.</li><li>Actionable checklists and templates.</li></ul><p>👉 <a href="https://cradecoded.substack.com/subscribe"><strong>Subscribe here</strong></a></p><p><em>Free. Published every Sunday. Unsubscribe at any time.</em></p><p><strong>About CRA Decoded</strong></p><p>An independent engineering publication that translates EU cybersecurity regulations into practical guides for software teams.</p><p>📧 Newsletter: <a href="https://cradecoded.substack.com/">cradecoded.substack.com</a><br>🌐 Website: <a href="https://cra-decoded.com/">cra-decoded.com</a><br>✉️ Contact: <a href="/service/mailto:contact@cra-decoded.com">contact@cra-decoded.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0a2e9bf89332" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CRA SBOM Requirements: What’s Mandated, What’s Optional, and What’s Still Unclear]]></title>
            <link>https://medium.com/@cra-decoded/cra-sbom-requirements-whats-mandated-what-s-optional-and-what-s-still-unclear-6de9270666de?source=rss-b20a11df9499------2</link>
            <guid isPermaLink="false">https://medium.com/p/6de9270666de</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[CRA Decoded]]></dc:creator>
            <pubDate>Sun, 15 Mar 2026 11:46:04 GMT</pubDate>
            <atom:updated>2026-03-15T11:46:04.329Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Last updated: March 2026 | Part 3 of the CRA Decoded series</em></p><p>The CRA requires a machine-readable Software Bill of Materials covering “at the very least the top-level dependencies” — but deliberately leaves format, depth, and disclosure details unspecified. BSI, ENISA, and the harmonized standards bodies are now racing to fill that space — but none of them move faster than September 11, 2026. That’s when Article 14 kicks in: manufacturers must report actively exploited vulnerabilities within 24 hours (Cyber Resilience Act — Reporting obligations, 2024). Without a working SBOM, that window is impossible to meet.</p><p><em>This article is Part 3 of the CRA Decoded series. Part 1 covered product scope. Part 2 covered classification tiers. We link to both where relevant.</em></p><figure><img alt="CRA SBOM requirements — software bill of materials components" src="https://cdn-images-1.medium.com/max/1024/0*HZZ79R3hIa0J2nbU" /><figcaption>Photo by <a href="https://unsplash.com/@guerrillabuzz?utm_source=medium&amp;utm_medium=referral">GuerrillaBuzz</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What the CRA Actually Requires for SBOMs (Annex I, Part II Decoded)</h3><p>The core requirement is in Annex I, Part II, point (1) of Regulation EU 2024/2847:</p><blockquote><em>“Manufacturers of products with digital elements shall identify and document vulnerabilities and components contained in products with digital elements, including by drawing up a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies of the products.”</em></blockquote><p>The SBOM requirement sits in Part II of Annex I — vulnerability handling, not product design. That placement matters: the legislator treats the SBOM as an operational security tool, not a documentation checkbox. The legal floor is top-level dependencies only; transitive and nested are out. And ‘commonly used and machine-readable’ points straight at SPDX or CycloneDX without naming either. A PDF doesn’t qualify.</p><p>Article 3(39) gives the formal definition: <em>“a formal record containing details and supply chain relationships of components included in the software elements of a product with digital elements.”</em> That’s broader than a dependency list. “Supply chain relationships” are explicitly in scope.</p><p>Article 13 sets the obligation chain: handle vulnerabilities for the entire support period (minimum 5 years post-market), perform due diligence on third-party and open-source components, and report upstream when a vulnerability is found in something you’ve integrated. You can’t do any of that without knowing what you ship.</p><p>There’s also Article 13(24): “The Commission may, by means of implementing acts… specify the format and elements of the software bill of materials.” Today’s requirement is a floor. The Commission could mandate CycloneDX 1.6+ or SPDX 3.0.1+ at any point. As of March 2026, no such act exists — but the power to issue one remains.</p><p>The SBOM is also part of technical documentation under Article 31 and Annex VII, Part 2(b), listed alongside the coordinated vulnerability disclosure policy and vulnerability reporting contact. That documentation must be kept for at least 10 years, or the entire support period if longer.</p><h3>What the CRA Explicitly Does Not Require</h3><p>Recital 77 is the most important recital for SBOM planning: “Manufacturers should not be obliged to make the SBOM public.” The SBOM is internal documentation. Market surveillance authorities can request it under Article 53, but customers and the public don’t get it by default (Cyber Resilience Act — Summary of the legislative text, 2024). If a manufacturer voluntarily shares it, Annex II, Part I, point 9 requires indicating where it’s accessible — but that disclosure is the manufacturer’s call.</p><p>Recital 22 adds a layer: when market surveillance authorities share SBOM data with ADCO (the Administrative Cooperation Group for CRA enforcement), it goes “in an anonymised and aggregated manner.” Individual SBOMs are protected.</p><p>The CRA also skips a fixed update cadence — Recital 90 says ‘up to date’ and leaves the schedule to the manufacturer (Cyber Resilience Act, 2024). No format standard by name. No cryptographic hashes, license identifiers, or filename metadata. And ‘top-level dependencies’ isn’t defined anywhere. Not in Article 3, not in the recitals, not in the annexes (Horizontal cybersecurity requirements for products with digital elements (Cyber Resilience Act), 2024).</p><h3>Why September 2026 Is Your Real SBOM Deadline (Not December 2027)</h3><p>Article 14 requires manufacturers to report actively exploited vulnerabilities to CSIRT and ENISA within 24 hours (early warning), 72 hours (detailed notification), and 14 days (final report). This applies from September 11, 2026, 15 months before the full CRA application on December 11, 2027. (Cyber Resilience Act — Reporting obligations, 2026).</p><figure><img alt="CRA Article 14 vulnerability reporting deadline September 2026" src="https://cdn-images-1.medium.com/max/1024/0*Zczscz7Wl4j18Gg4" /><figcaption>Photo by <a href="https://unsplash.com/@maddibazzocco?utm_source=medium&amp;utm_medium=referral">Maddi Bazzocco</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Article 14 never mentions ‘SBOM.’ But when a vulnerability like Log4Shell drops, you have hours to determine whether your product is affected. Without an up-to-date SBOM and automated CVE monitoring tied to it, you can’t know (Stepping up our role in Vulnerability Management: ENISA Becomes CVE Root, 2025). Keysight’s analysis puts it plainly:</p><blockquote><em>“If you don’t have SBOMs and a vulnerability management process in place before September 2026, you cannot comply.”</em></blockquote><p>SCANOSS is equally direct:</p><blockquote><em>“This does not mean tracking every vulnerability published globally. It means being able to determine — immediately — whether a disclosed vulnerability affects software inside your product. That is only possible if you know what you ship.”</em></blockquote><p>The standards gap makes this worse. The CEN/CENELEC vulnerability handling standard (EN 40000–1–3) targets August 30, 2026–12 days before Article 14 kicks in. Manufacturers waiting for the harmonized standard before building their process won’t have time to implement it.</p><h3>What “Top-Level Dependencies” Actually Means — and Why It Matters</h3><p>The regulation’s most debated phrase is “at the very least the top-level dependencies.” No definition exists anywhere in the text. Industry practice converges on direct, first-level dependencies — what’s declared in package.json, requirements.txt, go.mod, pom.xml, or Cargo.toml. Transitive dependencies aren’t legally required at the minimum standard.</p><p>FOSSA flags the practical risk: “This is akin to a software inventory, and in cases like log4shell, where many instances were compiled inside other libraries, it may not be sufficient to identify the risky components.” SafeDep’s guidance: “While CRA says top-level only, consider capturing deeper dependencies where feasible.”</p><p>BSI TR-03183–2 takes a stricter line. It requires recursive dependency resolution on each path downward, “at least up to and including the first component outside the scope of delivery.” That external component must be identified with the creator, name, version, and unique identifiers. BSI’s ‘scope of delivery’ concept draws a line: components shipped with the product are yours to document fully; external dependencies stop at the first external component. That’s the most workable interpretation of ‘top-level’ available right now.</p><p>“At the very least” is a floor, not a target. The forthcoming CEN/CENELEC PT3 vulnerability handling standard will almost certainly land closer to BSI’s position than to the CRA’s bare minimum (Cyber Resilience Act (CRA), 2024).</p><h3>BSI TR-03183–2: The Closest Thing to a CRA SBOM Standard Right Now</h3><p>For teams working through CRA SBOM requirements today, BSI TR-03183–2 (v2.1.0, September 2025) is the most actionable reference available — and with no harmonized standard published yet, it’s also the most technically detailed (Informationstechnik, n.d.). It accepts CycloneDX 1.6+ or SPDX 3.0.1+ in JSON or XML. Neither format is mandated over the other.</p><figure><img alt="BSI TR-03183–2 SBOM mandatory fields CRA compliance" src="https://cdn-images-1.medium.com/max/1024/0*3K0gD_wsJIlN2Iia" /><figcaption>Photo by <a href="https://unsplash.com/@cbpsc1?utm_source=medium&amp;utm_medium=referral">Clint Patterson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The guideline requires over 10 mandatory fields per component — well beyond NTIA 2021 minimum elements or the CISA 2025 draft ((CISA), 2025):</p><ul><li>Component Creator (contact info)</li><li>Component Name</li><li>Component Version</li><li>Filename (deployable artifact)</li><li>Dependency Relationships</li><li>Distribution Licences (SPDX identifiers)</li><li>Hash Value (e.g., SHA-512)</li><li>Executable Property</li><li>Archive Property</li><li>Structured Property</li></ul><p>If your current SBOM tooling generates all ten of these out of the box, you’re ahead of most teams. Most don’t — see the tooling section below (Ruohonen et al., 2025).</p><p>At the document level, SBOM Creator and Timestamp are both mandatory (Security, n.d.).</p><p>One architectural call BSI makes explicitly: SBOMs must not contain vulnerability data. Vulnerability information changes daily; SBOM component data is relatively stable. Vulnerability status belongs in separate VEX (Vulnerability Exploitability eXchange) or CSAF (Common Security Advisory Framework) documents ((Security), n.d.). That maps cleanly onto the CRA’s own logic: the SBOM identifies what you ship, VEX/CSAF communicates what’s exploitable.</p><p>BSI has also published a CycloneDX property taxonomy (github.com/BSI-Bund/tr-03183-cyclonedx-property-taxonomy) to cover fields that neither CycloneDX nor SPDX handles natively (BSI TR-03183–2: Cyber-Resilienz-Anforderungen an Hersteller und Produkte — Teil 2: Software Bill of Materials (SBOM) Version 2.0.0, 2024). TR-03183 is explicitly a stopgap — BSI states it “will be gradually developed further and replaced by the corresponding harmonized European standards as soon as they become available” (BSI — Technical Guideline TR-03183: Cyber Resilience Requirements for Manufacturers and Products, 2024).</p><h3>What ENISA’s SBOM Guidance Says (and What It Doesn’t Mandate)</h3><p>ENISA published its SBOM Landscape Analysis: Towards an Implementation Guide (v1.20) in December 2025–84 pages, consultation closed January 23, 2026, final version due Q2 2026 (Call for Feedback: Advancing Software Supply Chain Security together!, 2025). No mandatory requirements, but solid implementation guidance structured around five phases: Initiation, Planning, Execution, Monitoring, Closure.</p><p>The practical recommendations: start coverage with customer-facing applications, expand to internal systems and third-party dependencies, then tackle containers and microservices. Generate SBOMs at build time for accuracy. On tooling, ENISA is candid: “interoperability between different tools handling SBOMs is not currently guaranteed, because of varying interpretations of the SBOM specifications” (Wang et al., 2026). Test your pipeline across the tools you plan to use.</p><p>ENISA’s framing is the tell: “automated security response, predictive supply chain analytics, evidence-based architectural decisions.” That’s not compliance language — that’s SOC language. That distinction matters when you’re deciding how long to retain SBOMs and how often to regenerate them.</p><p>ENISA also released a Technical Advisory for Secure Use of Package Managers (v0.8) in December 2025 — the first in a planned advisory series. It covers risks from third-party packages, which directly affect SBOM accuracy: most of what ends up in your SBOM comes through a package manager (ENISA opens public consultation on SBOM analysis and secure package management guidance, 2025).</p><h3>The Harmonized Standards Gap: No EN 40000 SBOM Standard Yet</h3><p>The Commission’s standardization request M/606 was accepted by CEN, CENELEC, and ETSI on April 3, 2025. It calls for 41 harmonized standards — 15 horizontal, 25+ vertical. SBOM requirements sit primarily in PT3 (vulnerability handling), with dedicated sub-chapters on SBOM structure formalization.</p><p>The deadlines for EN 40000–1 (framework) and the vulnerability handling standard are target August 30, 2026. A draft prEN for vulnerability handling was published in December 2025. Vertical product-specific standards are targeted for October 30, 2026. Remaining horizontal technical measures: October 30, 2027. As of March 2026, nothing has been formally published.</p><p>Other relevant work: ETSI TR 104 034 (“SBOM Compendium”) covers trust, discovery, interoperability, and lifecycle. ISO/IEC 5962 (SPDX) and ECMA-424 (CycloneDX) are expected to be referenced by the European standards. CENELEC TC65X WG3 is adapting IEC 62443 for industrial automation (ETSI TR 104 034 V1.1.1 (2025–05), n.d.).</p><h3>SPDX vs CycloneDX for CRA Compliance: Which Format Should You Use?</h3><p>Both are accepted by BSI TR-03183–2 and are the only realistic choices. SWID tags (ISO/IEC 19770–2) aren’t on the list — BSI doesn’t include them, and the tooling ecosystem isn’t there. (BSI TR-03183–2: Cyber-Resilienz-Anforderungen an Hersteller und Produkte — Teil 2: Software Bill of Materials (SBOM) Version 1.0 (veraltet), 2023).</p><p>SPDX 2.3 mandatory fields at document level: SPDXVersion, DataLicense (CC0–1.0), SPDX Identifier, Document Name, Namespace, Creator, Created timestamp. Package level mandatories: PackageName, SPDXID, PackageDownloadLocation. Version, supplier, checksum, and licensing are optional at the schema level (required in practice for CRA). SPDX 3.0/3.0.1 introduced profiles — Core + Software + Security covers most CRA requirements (SPDX and NTIA Minimum Elements for SBOM HOWTO, 2023).</p><p>CycloneDX has minimal schema-level mandatories: bomFormat, specVersion, component type, and name. In practice, you need a supplier, version, PURL/CPE, hashes, licenses, and dependency relationships for CRA. CycloneDX 1.6 (April 2024) added Cryptographic BOM (CBOM) and attestation support (CDXA) — the latter enables “compliance as code” for CRA evidence. CycloneDX 1.7 (October 2025) added citations for provenance (CycloneDX Specification Overview, 2025).</p><p>Both formats clear the NTIA 2021 minimum. Neither gets you to BSI TR-03183–2 out of the box — you’re missing mandatory hashes, license identifiers, filename metadata, and the executable/archive/structured properties. That’s what sbomqs is for (BSI TR-03183–2: Cyber-Resilienz-Anforderungen an Hersteller und Produkte — Teil 2: Software Bill of Materials (SBOM) Version 2.0.0, 2024).</p><h3>Tooling for CRA-Ready SBOMs: Syft, Trivy, and Validation</h3><p>Syft (Anchore) supports 28+ package ecosystems and outputs both formats:</p><pre># CycloneDX JSON from a container image<br>syft scan alpine:latest -o cyclonedx-json=sbom-cdx.json<br># SPDX JSON from a project directory<br>syft scan dir:path/to/project -o spdx-json=sbom-spdx.json<br># Both formats in one pass<br>syft scan registry:yourrepo/image:tag -o spdx-json=./spdx.json -o cyclonedx-json=./cdx.json</pre><figure><img alt="SBOM generation CI/CD pipeline Syft Trivy CRA compliance" src="https://cdn-images-1.medium.com/max/1024/0*1_Un8sdIs41sU9HP" /><figcaption>Photo by <a href="https://unsplash.com/@dkomow?utm_source=medium&amp;utm_medium=referral">Daniil Komov</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Trivy (Aqua Security) combines SBOM generation with vulnerability scanning:</p><pre># CycloneDX from container image<br>trivy image --format cyclonedx --output sbom.cdx.json nginx:1.25<br># SPDX JSON from filesystem<br>trivy fs --format spdx-json --output sbom.spdx.json ./my-application/<br># Convert between formats<br>trivy convert --format cyclonedx --output result.cdx result.json</pre><p>For GitHub Actions, the Anchore SBOM Action wraps Syft directly:</p><pre>- name: Generate SBOM<br>uses: anchore/sbom-action@v0<br>with:<br>format: cyclonedx-json<br>output-file: sbom.cdx.json</pre><p>GitHub also exposes a built-in SBOM export via the dependency graph REST API (SPDX 2.3 JSON):</p><pre>curl -L -H &quot;Authorization: Bearer &lt;TOKEN&gt;&quot; \<br>https://api.github.com/repos/OWNER/REPO/dependency-graph/sbom</pre><p>For validation, the ntia-conformance-checker (sbomcheck command) checks SPDX against NTIA/CISA baselines. cyclonedx-cli validate checks CycloneDX against the spec schema. sbomqs (Interlynk) gives you the most CRA-relevant check with explicit BSI TR-03183–2 compliance scoring:</p><pre># BSI TR-03183-2 v2.0 compliance check<br>sbomqs compliance --bsi-v2 my-app.spdx.json<br># Quality score (0-10)<br>sbomqs score my-app.cdx.json</pre><p>We’ve tested both Syft and Trivy against BSI TR-03183–2 field requirements. Syft generates cleaner CycloneDX output out of the box; Trivy’s advantage is the integrated CVE scan in a single pipeline step. For a product with mixed package managers (npm + pip + go modules), Syft handles the multi-ecosystem scan more reliably. Neither tool produces all 10 BSI-required fields by default — you’ll need post-processing or sbomqs to validate the gap (SBOM Scanning, 2024).</p><h3>4 Open Questions About CRA SBOM Compliance (No One Has Answered Yet)</h3><p>Several CRA SBOM requirements remain genuinely unclear as of early 2026 — not due to contradictions in the text, but through the absence of guidance.</p><p><strong>[1] Proprietary components and trade secrets. </strong>The CRA requires identifying components, but doesn’t force source code disclosure. SafeDep confirms that only “the identity of software components” is required. Authorities must treat SBOM data confidentially. For third-party vendors who won’t supply SBOMs, SPDX’s NOASSERTION convention lets you document what you know and flag what you don’t. BSA has pushed ENISA to keep SBOM requirements “risk-appropriate” and avoid inadvertently mapping vulnerability points.</p><p><strong>[2] SaaS scope. </strong>BSA and others want explicit confirmation that pure SaaS falls outside the CRA (and is instead governed by NIS2). The CRA targets “products with digital elements” placed on the market; remote data processing solutions are in scope when purpose-built for a product, but the product/service boundary remains under debate. This matters for today’s SBOM scope decisions.</p><p><strong>[3] Retroactive application. </strong>Article 14 reporting applies from September 2026 to all products already on the market — not just new ones. Products placed before December 2027 are subject to full CRA only if “substantially modified,” but the threshold is unspecified. Commission guidance is expected but not yet published (Cyber Resilience Act — Reporting obligations, 2026).</p><p><strong>[4] SBOM exchange mechanisms. </strong>OWASP’s CycloneDX team is developing a BOM Transparency API for automated SBOM exchange, but it’s not finalized. How SBOMs will be transmitted to market surveillance authorities — file upload, API, portal — depends on ENISA’s Single Reporting Platform, which should be operational by September 2026 (Implementation of the Single Reporting Platform, 2024).</p><h3>Start Building Now, Refine as Standards Arrive</h3><p>The CRA’s SBOM text stays deliberately minimal: a “commonly used, machine-readable” format, with “at least top-level dependencies.” The ecosystem around it is not. BSI TR-03183–2 already mandates CycloneDX 1.6+ or SPDX 3.0.1+ with 10+ fields per component and recursive dependency resolution. The CEN/CENELEC PT3 standard, expected in mid-2026, will almost certainly land closer to BSI than to the CRA’s bare minimum.</p><p>The practical deadline is September 2026, not December 2027. Teams that treat SBOM generation as a late-2027 problem will find themselves with a 24-hour vulnerability reporting window and no way to answer the first question: Does this vulnerability affect what we ship? The answer to that starts with knowing what you ship.</p><p>Start here: integrate Syft or Trivy into your CI/CD pipeline now, generate SBOMs on every release, validate against BSI TR-03183–2 using sbomqs, and keep vulnerability data out of the SBOM itself (use VEX/CSAF for that). Refine as harmonized standards arrive. For a company with €50M annual revenue, that’s a €1.25M floor penalty. The Syft integration takes an afternoon.</p><p>The bottom line on CRA SBOM requirements: the legal minimum is narrow, the practical minimum is BSI TR-03183–2, and <strong>the operational deadline is September 2026, not December 2027.</strong></p><h3>Subscribe to CRA Decoded</h3><p>Receive weekly technical guides on EU Cyber Resilience Act compliance directly in your inbox.</p><p><strong>You will receive:</strong></p><ul><li>Comprehensive implementation guides, including SBOM, vulnerability management, and CE marking.</li><li>Updates on CRA regulations from ENISA and the European Commission.</li><li>Tool reviews and practical recommendations.</li><li>Actionable checklists and templates.</li></ul><p>👉 <a href="https://cradecoded.substack.com/subscribe"><strong>Subscribe here</strong></a></p><p><em>Free. Published every Sunday. Unsubscribe at any time.</em></p><p><strong>About CRA Decoded</strong></p><p>An independent engineering publication that translates EU cybersecurity regulations into practical guides for software teams.</p><p>📧 Newsletter: <a href="https://cradecoded.substack.com/">cradecoded.substack.com</a><br>🌐 Website: <a href="https://cra-decoded.com/">cra-decoded.com</a><br>✉️ Contact: <a href="/service/mailto:contact@cra-decoded.com">contact@cra-decoded.com</a></p><h3>References</h3><ol><li>(2023). BSI TR-03183–2: Cyber-Resilienz-Anforderungen an Hersteller und Produkte — Teil 2: Software Bill of Materials (SBOM) Version 1.0 (veraltet). BSI TR-03183–2: Cyber-Resilienz-Anforderungen an Hersteller und Produkte — Teil 2: Software Bill of Materials (SBOM) Version 1.0 (veraltet). <a href="https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Publikationen/TechnischeRichtlinien/TR03183/BSI-TR-03183-2.html">https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Publikationen/TechnischeRichtlinien/TR03183/BSI-TR-03183-2.html</a></li><li>(2023). SPDX and NTIA Minimum Elements for SBOM HOWTO. SPDX Specification 2.3.0. <a href="https://spdx.github.io/spdx-ntia-sbom-howto/">https://spdx.github.io/spdx-ntia-sbom-howto/</a></li><li>(2024). BSI — Technical Guideline TR-03183: Cyber Resilience Requirements for Manufacturers and Products. BSI. <a href="https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03183/BSI-TR-03183-2-2_0_0.html">https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03183/BSI-TR-03183-2-2_0_0.html</a></li><li>(2024). BSI TR-03183–2: Cyber-Resilienz-Anforderungen an Hersteller und Produkte — Teil 2: Software Bill of Materials (SBOM) Version 2.0.0. BSI — Bundesamt für Sicherheit in der Informationstechnik. <a href="https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03183/BSI-TR-03183-2-2_0_0.html">https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03183/BSI-TR-03183-2-2_0_0.html</a></li><li>(2024). BSI TR-03183–2: Cyber-Resilienz-Anforderungen an Hersteller und Produkte — Teil 2: Software Bill of Materials (SBOM) Version 2.0.0. BSI Technical Guideline. <a href="https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03183/BSI-TR-03183-2-2_0_0.html">https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03183/BSI-TR-03183-2-2_0_0.html</a></li><li>(2024). Cyber Resilience Act — Reporting obligations. Shaping Europe’s digital future. <a href="https://digital-strategy.ec.europa.eu/en/policies/cra-reporting">https://digital-strategy.ec.europa.eu/en/policies/cra-reporting</a></li><li>(2024). Cyber Resilience Act — Summary of the legislative text. European Commission. <a href="https://digital-strategy.ec.europa.eu/en/policies/cra-summary">https://digital-strategy.ec.europa.eu/en/policies/cra-summary</a></li><li>(2024). Cyber Resilience Act. Regulation (EU) 2024/2847 of the European Parliament and of the Council of 23 October 2024 on horizontal cybersecurity requirements for products with digital elements and amending Regulations (EU) No 168/2013 and (EU) No 2019/1020 and Directive (EU) 2020/1828 (Cyber Resilience Act). <a href="http://data.europa.eu/eli/reg/2024/2847/oj">http://data.europa.eu/eli/reg/2024/2847/oj</a></li><li>(2024). Implementation of the Single Reporting Platform. ENISA. <a href="https://enisa.europa.eu/procurement/implementation-of-the-single-reporting-platform">https://enisa.europa.eu/procurement/implementation-of-the-single-reporting-platform</a></li><li>(2024). SBOM Scanning. Trivy Documentation. <a href="https://trivy.dev/v0.45/docs/target/sbom/">https://trivy.dev/v0.45/docs/target/sbom/</a></li><li>(2025). CycloneDX Specification Overview. CycloneDX Specification Overview. <a href="https://cyclonedx.org/specification/overview">https://cyclonedx.org/specification/overview</a></li><li>(2026). Cyber Resilience Act — Reporting obligations. Shaping Europe’s digital future. <a href="https://digital-strategy.ec.europa.eu/en/policies/cra-reporting">https://digital-strategy.ec.europa.eu/en/policies/cra-reporting</a></li><li>(CISA), C. a. (August 22, 2025). CISA Issues Draft Software Bill of Materials Guide for Public Comment. CISA. <a href="https://www.cisa.gov/news-events/news/cisa-issues-draft-software-bill-materials-guide-public-comment">https://www.cisa.gov/news-events/news/cisa-issues-draft-software-bill-materials-guide-public-comment</a></li><li>(December 17, 2025). Call for Feedback: Advancing Software Supply Chain Security together!. ENISA. <a href="https://www.enisa.europa.eu/news/call-for-feedback-advancing-software-supply-chain-security-together">https://www.enisa.europa.eu/news/call-for-feedback-advancing-software-supply-chain-security-together</a></li><li>(December 17, 2025). ENISA opens public consultation on SBOM analysis and secure package management guidance. ENISA. <a href="https://www.enisa.europa.eu/news/call-for-feedback-advancing-software-supply-chain-security-together">https://www.enisa.europa.eu/news/call-for-feedback-advancing-software-supply-chain-security-together</a></li><li>(n.d.). ETSI TR 104 034 V1.1.1 (2025–05). <a href="https://www.etsi.org/deliver/etsi_tr/104000_104099/104034/01.01.01_60/tr_104034v010101p.pdf">https://www.etsi.org/deliver/etsi_tr/104000_104099/104034/01.01.01_60/tr_104034v010101p.pdf</a></li><li>(November 20, 2024). Horizontal cybersecurity requirements for products with digital elements (Cyber Resilience Act). EUR-Lex. <a href="https://eur-lex.europa.eu/EN/legal-content/summary/horizontal-cybersecurity-requirements-for-products-with-digital-elements.html?fromSummary=31">https://eur-lex.europa.eu/EN/legal-content/summary/horizontal-cybersecurity-requirements-for-products-with-digital-elements.html?fromSummary=31</a></li><li>(November 20, 2025). Stepping up our role in Vulnerability Management: ENISA Becomes CVE Root. ENISA. <a href="https://www.enisa.europa.eu/news/stepping-up-our-role-in-vulnerability-management-enisa-becomes-cve-root">https://www.enisa.europa.eu/news/stepping-up-our-role-in-vulnerability-management-enisa-becomes-cve-root</a></li><li>(October 23, 2024). Cyber Resilience Act (CRA). EU Cyber Resilience Act Official Journal. <a href="https://data.europa.eu/eli/reg/2024/2847/oj">https://data.europa.eu/eli/reg/2024/2847/oj</a></li><li>Informationstechnik, B. B. (n.d.). BSI TR-03183: Cyber Resilience Requirements for Manufacturers and Products. <a href="https://www.bsi.bund.de/EN/Themen/Unternehmen-und-Organisationen/Standards-und-Zertifizierung/Technische-Richtlinien/TR-nach-Thema-sortiert/tr03183/tr-03183.html?nn=132646">https://www.bsi.bund.de/EN/Themen/Unternehmen-und-Organisationen/Standards-und-Zertifizierung/Technische-Richtlinien/TR-nach-Thema-sortiert/tr03183/tr-03183.html?nn=132646</a></li><li>Ruohonen, J., Hjerppe, K. &amp; Kang, E. (2025). A Mapping Analysis of Requirements Between the CRA and the GDPR. arXiv preprint. <a href="https://doi.org/10.48550/arXiv.2503.01816">https://doi.org/10.48550/arXiv.2503.01816</a></li><li>Security, F. O. (n.d.). Technical Guideline TR-03183: Cyber. <a href="https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03183/BSI-TR-03183-2-2_0_0.pdf?__blob=publicationFile&amp;v=3">https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03183/BSI-TR-03183-2-2_0_0.pdf?__blob=publicationFile&amp;v=3</a></li><li>Security, B. (. (n.d.). BSI TR-03183–2: Software Bill of Materials (SBOM). <a href="https://www.bsi.bund.de/EN/Themen/Unternehmen-und-Organisationen/Informationen-und-Empfehlungen/Empfehlungen-nach-Angriffszielen/Industrielle-Steuerungs-und-Automatisierungssysteme/CSAF/CSAF_node.html">https://www.bsi.bund.de/EN/Themen/Unternehmen-und-Organisationen/Informationen-und-Empfehlungen/Empfehlungen-nach-Angriffszielen/Industrielle-Steuerungs-und-Automatisierungssysteme/CSAF/CSAF_node.html</a></li><li>Wang, C., Wu, J., Lyu, H., Ling, X., Luo, T., Wu, Y. &amp; Zhao, C. (2026). A Large Scale Empirical Analysis on the Adherence Gap between Standards and Tools in SBOM. arXiv:2601.05622. <a href="https://doi.org/10.48550/arXiv.2601.05622">https://doi.org/10.48550/arXiv.2601.05622</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6de9270666de" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>