Skip to product information
1 of 3

Svenska Dokumentmallar

CRA component supplier – SBOM basis, vulnerability notification and security control | Word/PDF/Excel

CRA component supplier – SBOM basis, vulnerability notification and security control | Word/PDF/Excel

File format
DOCX, PDF, XLSX
Document language
5 Swedish work templates + Swedish user guide; separate English User Guide with instructions only; Swedish XLSX.
Number of files
7

Digital download. No physical product is shipped.

Regular price 79 SEK
Regular price Sale price 79 SEK
Sale Sold out
Taxes included.
View full details

About this template

Review security documentation from third-party component suppliers before incorporating hardware or software into a connected product. 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.

Quick facts: 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.

01 · Package contents

Five 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: 15 actual customer files, seven independent documents plus Excel. The English guide is not an English version of the Swedish working templates.

02 · What the files contain

Define 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.

Who is the document package for – and when is another package better?

Example 1: 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.

Example 2: 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.

Not the right package: 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.

Exactly what you get in the ZIP file

Document Function Language Format
01 · Applicability and component role Manufacturer responsibility, component use, CRA scope, and timeline SV DOCX + PDF
02 · Supplier request and SBOM basis Request version details, security contact, dependencies, and evidence, with confidentiality boundaries SV DOCX + PDF
03 · Receipt check and risk assessment Check the component version, known vulnerabilities, test evidence, and integration risk SV DOCX + PDF
04 · Vulnerability notification and escalation Separate supplier notification, manufacturer reporting review, and actual remediation SV DOCX + PDF
05 · Component change and release decision Compare versions, perform retesting, and make a separate manual Go/No-Go decision SV DOCX + PDF
06 · Swedish user guide Workflow, sources, responsibility, exceptions, and four test scenarios SV DOCX + PDF
07 · English User Guide Instructions for the Swedish operational templates; not translated Swedish legal forms EN DOCX + PDF
08 · Excel – component check Nine tabs for components, suppliers, SBOM evidence, vulnerabilities, and remediations SV XLSX

The 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.

Excel in practice: nine working tabs

Overview, Products, Components, Suppliers, SBOM evidence, Vulnerabilities, Changes, Remediations, and Read me. 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 MISSING BASIS; with a basis ID it is marked BASIS PROVIDED – REVIEW. This does not mean that the component is secure or approved according to the law.

Excel 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.

How you use the documents

  1. Assess the product's and company's actual CRA applicability as well as responsibility for the final product and component.
  2. Identify the supplier, version, administrator, and agreed security contact.
  3. Request relevant information and protect any confidential security information.
  4. Perform actual vulnerability and security testing of the component and document the results.
  5. Assess separately whether a known vulnerability also triggers the manufacturer's reporting under Article 14.
  6. Upon version change: compare basis, perform tests, and obtain authorized manual release approval.
  7. Archive actual evidence IDs and follow up on open remediations without confusing registration with verification.

Important legal prerequisites and limitations

Articles 13.5–6: 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 December 11, 2027. Official Regulation (EU) 2024/2847.

Annex I Part II Point 1: 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. CRA Annex I and VII.

Article 14: Obligations to report actively exploited vulnerabilities and serious security incidents for affected manufacturers began to apply on September 11, 2026. 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. EU Commission reporting guidance.

Compare with related documents

Do you primarily need to handle actual CRA incident and regulatory reporting? See CRA PSIRT – vulnerability reception and reporting. For security updates over the product's lifecycle, see CRA support period – updates and lifecycle register. For a broad CRA inventory, see the CRA Compliance Package.

Frequently asked questions

Must all component suppliers provide a complete SBOM to the customer?

No, 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.

Is the Excel file sufficient to meet the CRA SBOM requirements?

No. Excel helps the user register basis references and deficiencies. It does not generate a standardized, machine-readable SBOM for the product.

Can I submit an Article 14 report with the Word template?

No. The Word template is an internal notification and decision basis. Applicable regulatory reports are submitted via the CRA's official reporting process.

Does completed component testing mean the product can be CE marked?

No. CE conformity and applicable assessment of the final product must be done separately.

Are all seven main templates in Swedish and English?

No. 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.

Are the documents ready to use in 2026?

Yes, 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.

Sources and transparency

Version 1.0 · AI-assisted legal source check on November 15, 2026. Official sources: CRA (EU) 2024/2847, EU Commission implementation timeline, and reporting guidance. 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.