{"product_id":"cra-komponentleverantor-sbom-sarbarhetsavisering","title":"CRA component supplier – SBOM basis, vulnerability notification and security control | Word\/PDF\/Excel","description":"\u003cp\u003e\u003cstrong\u003eReview security documentation from third-party component suppliers before incorporating hardware or software into a connected product.\u003c\/strong\u003e This Swedish CRA specialist package helps manufacturers document component identification, supplier requests, SBOM evidence, vulnerability notification, and manual release testing. It is a working document for actual security work – not a finished SBOM format, CE certificate, or CRA certification.\u003c\/p\u003e\n\u003cp\u003e\u003cstrong\u003eQuick facts:\u003c\/strong\u003e EU Cyber Resilience Act (CRA), with Swedish business use · 5 Swedish working documents + Swedish user guide + separate English User Guide · 7 editable Word files (DOCX), 7 corresponding searchable PDF files, and an Excel register (XLSX) with nine tabs · 15 files in a future digital ZIP delivery. The PDF files are not interactive forms.\u003c\/p\u003e\n\u003cdiv style=\"border:2px solid #5d89ac;border-radius:9px;padding:14px 16px;margin:16px 0;background:#f3f8fc\"\u003e\n\n\u003ch2 style=\"font-size:1.1em;margin:0 0 6px\"\u003e01 · Package contents\u003c\/h2\u003e\n\n\u003cp\u003eFive standalone Swedish working templates, a Swedish user guide, and separate English instructions. All seven documents are available in DOCX and corresponding printable, searchable PDF (14 files). A Swedish Excel tool is also included: \u003cstrong\u003e15 actual customer files, seven independent documents plus Excel\u003c\/strong\u003e. The English guide is not an English version of the Swedish working templates.\u003c\/p\u003e\n\n\n\u003c\/div\u003e\n\u003cdiv style=\"border:2px solid #5d89ac;border-radius:9px;padding:14px 16px;margin:16px 0;background:#f3f8fc\"\u003e\n\n\u003ch2 style=\"font-size:1.1em;margin:0 0 6px\"\u003e02 · What the files contain\u003c\/h2\u003e\n\n\u003cp\u003eDefine the manufacturer and component role; request component and version evidence from the supplier; review dependencies, security updates, and known vulnerabilities; distinguish internal security notification from mandatory regulatory reporting; document retesting and a traceable manual release decision. Excel keeps requested, received, registered, remediated, and verified items separate.\u003c\/p\u003e\n\n\n\u003c\/div\u003e\n\u003ch2\u003eWho is the document package for – and when is another package better?\u003c\/h2\u003e\n\u003cp\u003e\u003cstrong\u003eExample 1:\u003c\/strong\u003e A Swedish IoT company is building a connected sensor and needs to check which software library and which version evidence the component supplier can provide, including which risks may need to be addressed before integration.\u003c\/p\u003e\n\u003cp\u003e\u003cstrong\u003eExample 2:\u003c\/strong\u003e A machinery manufacturer receives a new firmware version from a supplier and needs to document security notification, changed dependencies, regression testing, residual risk, and decisions before the next release.\u003c\/p\u003e\n\u003cp\u003e\u003cstrong\u003eNot the right package:\u003c\/strong\u003e When the business needs to perform the actual CRA regulatory reporting, establish complete technical CE documentation, perform automated CVE searches, or generate a real SPDX\/CycloneDX SBOM. In that case, use dedicated security tools and, if necessary, other document packages.\u003c\/p\u003e\n\u003ch2\u003eExactly what you get in the ZIP file\u003c\/h2\u003e\n\u003cdiv style=\"max-width:100%;overflow-x:auto\"\u003e\u003ctable style=\"width:100%;min-width:680px;border-collapse:collapse;font-size:.9em\"\u003e\n\n\u003cthead\u003e\u003ctr style=\"background:#dceaf4\"\u003e\n\n\u003cth scope=\"col\" style=\"text-align:left;padding:8px\"\u003eDocument\u003c\/th\u003e\n\n\u003cth scope=\"col\" style=\"text-align:left;padding:8px\"\u003eFunction\u003c\/th\u003e\n\n\u003cth scope=\"col\" style=\"text-align:left;padding:8px\"\u003eLanguage\u003c\/th\u003e\n\n\u003cth scope=\"col\" style=\"text-align:left;padding:8px\"\u003eFormat\u003c\/th\u003e\n\n\n\u003c\/tr\u003e\u003c\/thead\u003e\n\n\u003ctbody\u003e\n\n\u003ctr style=\"background:#fff\"\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003e01 · Applicability and component role\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eManufacturer responsibility, component use, CRA scope, and timeline\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eSV\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eDOCX + PDF\u003c\/td\u003e\n\n\n\u003c\/tr\u003e\n\n\u003ctr style=\"background:#f5f9fd\"\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003e02 · Supplier request and SBOM basis\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eRequest version details, security contact, dependencies, and evidence, with confidentiality boundaries\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eSV\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eDOCX + PDF\u003c\/td\u003e\n\n\n\u003c\/tr\u003e\n\n\u003ctr style=\"background:#fff\"\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003e03 · Receipt check and risk assessment\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eCheck the component version, known vulnerabilities, test evidence, and integration risk\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eSV\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eDOCX + PDF\u003c\/td\u003e\n\n\n\u003c\/tr\u003e\n\n\u003ctr style=\"background:#f5f9fd\"\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003e04 · Vulnerability notification and escalation\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eSeparate supplier notification, manufacturer reporting review, and actual remediation\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eSV\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eDOCX + PDF\u003c\/td\u003e\n\n\n\u003c\/tr\u003e\n\n\u003ctr style=\"background:#fff\"\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003e05 · Component change and release decision\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eCompare versions, perform retesting, and make a separate manual Go\/No-Go decision\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eSV\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eDOCX + PDF\u003c\/td\u003e\n\n\n\u003c\/tr\u003e\n\n\u003ctr style=\"background:#f5f9fd\"\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003e06 · Swedish user guide\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eWorkflow, sources, responsibility, exceptions, and four test scenarios\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eSV\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eDOCX + PDF\u003c\/td\u003e\n\n\n\u003c\/tr\u003e\n\n\u003ctr style=\"background:#fff\"\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003e07 · English User Guide\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eInstructions for the Swedish operational templates; not translated Swedish legal forms\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eEN\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eDOCX + PDF\u003c\/td\u003e\n\n\n\u003c\/tr\u003e\n\n\u003ctr style=\"background:#f5f9fd\"\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003e08 · Excel – component check\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eNine tabs for components, suppliers, SBOM evidence, vulnerabilities, and remediations\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eSV\u003c\/td\u003e\n\n\u003ctd style=\"border:1px solid #ccdae5;padding:8px;vertical-align:top\"\u003eXLSX\u003c\/td\u003e\n\n\n\u003c\/tr\u003e\n\n\n\u003c\/tbody\u003e\n\n\n\u003c\/table\u003e\u003c\/div\u003e\n\u003cp\u003eThe Word files are editable, the PDF files are searchable and suitable for printing but lack interactive form fields. Excel is intended to be opened in a spreadsheet program that supports XLSX formulas; no automatic external integration is included.\u003c\/p\u003e\n\u003ch2\u003eExcel in practice: nine working tabs\u003c\/h2\u003e\n\u003cp\u003e\u003cstrong\u003eOverview, Products, Components, Suppliers, SBOM evidence, Vulnerabilities, Changes, Remediations, and Read me.\u003c\/strong\u003e The overview counts registered products, components without a specified basis reference, open vulnerability issues, changes without a decision ID, and remediations that still lack separate verification. Example: a component with an ID but without a basis ID is marked \u003cem\u003eMISSING BASIS\u003c\/em\u003e; with a basis ID it is marked \u003cem\u003eBASIS PROVIDED – REVIEW\u003c\/em\u003e. This does not mean that the component is secure or approved according to the law.\u003c\/p\u003e\n\u003cp\u003eExcel does not create a machine-readable SBOM, fetch CVE data, assess the law's reporting exemptions, or calculate reporting deadlines. Actual file evidence, e.g., SPDX\/CycloneDX, is stored separately and referenced via an evidence ID.\u003c\/p\u003e\n\u003ch2\u003eHow you use the documents\u003c\/h2\u003e\u003col\u003e\n\n\u003cli\u003eAssess the product's and company's actual CRA applicability as well as responsibility for the final product and component.\u003c\/li\u003e\n\n\u003cli\u003eIdentify the supplier, version, administrator, and agreed security contact.\u003c\/li\u003e\n\n\u003cli\u003eRequest relevant information and protect any confidential security information.\u003c\/li\u003e\n\n\u003cli\u003ePerform actual vulnerability and security testing of the component and document the results.\u003c\/li\u003e\n\n\u003cli\u003eAssess separately whether a known vulnerability also triggers the manufacturer's reporting under Article 14.\u003c\/li\u003e\n\n\u003cli\u003eUpon version change: compare basis, perform tests, and obtain authorized manual release approval.\u003c\/li\u003e\n\n\u003cli\u003eArchive actual evidence IDs and follow up on open remediations without confusing registration with verification.\u003c\/li\u003e\n\n\n\u003c\/ol\u003e\n\u003ch2\u003eImportant legal prerequisites and limitations\u003c\/h2\u003e\n\u003cp\u003e\u003cstrong\u003eArticles 13.5–6:\u003c\/strong\u003e For manufacturers covered by the CRA, the provisions require due diligence when integrating third-party components and when handling identified component vulnerabilities. The main part of Article 13 will begin to apply \u003cstrong\u003eDecember 11, 2027\u003c\/strong\u003e. \u003ca href=\"https:\/\/eur-lex.europa.eu\/legal-content\/EN\/TXT\/?uri=CELEX:32024R2847\"\u003eOfficial Regulation (EU) 2024\/2847\u003c\/a\u003e.\u003c\/p\u003e\n\u003cp\u003e\u003cstrong\u003eAnnex I Part II Point 1:\u003c\/strong\u003e The manufacturer's documentation of components and dependencies includes a machine-readable SBOM with at least top-level dependencies for relevant products. A common Excel register is not this. The CRA does not in itself mean that every sub-supplier must unconditionally disclose or deliver its entire internal SBOM to every customer. \u003ca href=\"https:\/\/eur-lex.europa.eu\/legal-content\/EN\/TXT\/?uri=CELEX:32024R2847\"\u003eCRA Annex I and VII\u003c\/a\u003e.\u003c\/p\u003e\n\u003cp\u003e\u003cstrong\u003eArticle 14:\u003c\/strong\u003e Obligations to report actively exploited vulnerabilities and serious security incidents for affected manufacturers began to apply on \u003cstrong\u003eSeptember 11, 2026\u003c\/strong\u003e. Only an actual responsible manufacturer after separate classification can determine if, when, and how it should report; the forms here do not perform a regulatory filing. \u003ca href=\"https:\/\/digital-strategy.ec.europa.eu\/en\/policies\/cra-reporting\"\u003eEU Commission reporting guidance\u003c\/a\u003e.\u003c\/p\u003e\n\u003ch2\u003eCompare with related documents\u003c\/h2\u003e\u003cp\u003eDo you primarily need to handle actual CRA incident and regulatory reporting? See \u003ca href=\"\/en\/products\/cra-psirt-sarbarhetsrapportering-artikel14\"\u003eCRA PSIRT – vulnerability reception and reporting\u003c\/a\u003e. For security updates over the product's lifecycle, see \u003ca href=\"\/en\/products\/cra-supportperiod-2027-sakerhetsuppdateringar-livscykelregister\"\u003eCRA support period – updates and lifecycle register\u003c\/a\u003e. For a broad CRA inventory, see the \u003ca href=\"\/en\/products\/cyber-resilience-act-cra-compliance-2026-2027-svenska-english-riskbedomning-sbom-incidentrapportering-word-pdf-excel\"\u003eCRA Compliance Package\u003c\/a\u003e.\u003c\/p\u003e\n\u003ch2\u003eFrequently asked questions\u003c\/h2\u003e\n\u003ch3\u003eMust all component suppliers provide a complete SBOM to the customer?\u003c\/h3\u003e\u003cp\u003eNo, no general requirement for such disclosure to every customer automatically follows from the CRA. A manufacturer may need appropriate component information for its own control; actual delivery and confidentiality depend on applicable law and agreements.\u003c\/p\u003e\n\u003ch3\u003eIs the Excel file sufficient to meet the CRA SBOM requirements?\u003c\/h3\u003e\u003cp\u003eNo. Excel helps the user register basis references and deficiencies. It does not generate a standardized, machine-readable SBOM for the product.\u003c\/p\u003e\n\u003ch3\u003eCan I submit an Article 14 report with the Word template?\u003c\/h3\u003e\u003cp\u003eNo. The Word template is an internal notification and decision basis. Applicable regulatory reports are submitted via the CRA's official reporting process.\u003c\/p\u003e\n\u003ch3\u003eDoes completed component testing mean the product can be CE marked?\u003c\/h3\u003e\u003cp\u003eNo. CE conformity and applicable assessment of the final product must be done separately.\u003c\/p\u003e\n\u003ch3\u003eAre all seven main templates in Swedish and English?\u003c\/h3\u003e\u003cp\u003eNo. The five working templates and Excel are in Swedish, as is the Swedish user guide. English User Guide is a separate English instruction for exactly the Swedish templates.\u003c\/p\u003e\n\u003ch3\u003eAre the documents ready to use in 2026?\u003c\/h3\u003e\u003cp\u003eYes, as preparation and internal working basis. The articles on the manufacturer's general component testing normally begin to apply in 2027, while some reporting requirements already apply in 2026. Applicability and transitional provisions must be checked.\u003c\/p\u003e\n\u003ch2\u003eSources and transparency\u003c\/h2\u003e\u003cp\u003e\u003cstrong\u003eVersion 1.0 · AI-assisted legal source check on November 15, 2026.\u003c\/strong\u003e Official sources: \u003ca href=\"https:\/\/eur-lex.europa.eu\/legal-content\/EN\/TXT\/?uri=CELEX:32024R2847\"\u003eCRA (EU) 2024\/2847\u003c\/a\u003e, \u003ca href=\"https:\/\/digital-strategy.ec.europa.eu\/en\/factpages\/cyber-resilience-act-implementation\"\u003eEU Commission implementation timeline\u003c\/a\u003e, and \u003ca href=\"https:\/\/digital-strategy.ec.europa.eu\/en\/policies\/cra-reporting\"\u003ereporting guidance\u003c\/a\u003e. No external legal review, regulatory certification, or guarantee of legal compliance has been performed. Security and legal decisions must be adapted to each actual product.\u003c\/p\u003e","brand":"Svenska Dokumentmallar","offers":[{"title":"Default Title","offer_id":56628460355926,"sku":"MB-CRA-KOMP-SBOM-20261115-V1","price":79.0,"currency_code":"SEK","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0827\/2373\/3846\/files\/01_CRA_komponent_huvudbild_1600.png?v=1794740905","url":"https:\/\/mallbutiken.se\/en\/products\/cra-komponentleverantor-sbom-sarbarhetsavisering","provider":"Mallbutiken","version":"1.0","type":"link"}