Skip to product information
1 of 3

Svenska Dokumentmallar

Cyber Resilience Act (CRA) Compliance 2026/2027 – Swedish + English | Risk Assessment, SBOM & Incident Reporting Word/PDF/Excel

Cyber Resilience Act (CRA) Compliance 2026/2027 – Swedish + English | Risk Assessment, SBOM & Incident Reporting Word/PDF/Excel

File format
DOCX, PDF, XLSX
Document language
Swedish
Number of files
15

Digital download. No physical product is shipped.

Regular price $8.00 USD
Regular price Sale price $8.00 USD
Sale Sold out
Taxes included.
View full details

About this template

Cyber Resilience Act (CRA) Compliance 2026/2027 – complete 2-in-1 package

A comprehensive compliance package for companies that manufacture, develop, or place products with digital elements on the EU market and need to prepare or document their work in accordance with Regulation (EU) 2024/2847 – Cyber Resilience Act (CRA).

The package combines Swedish and English work templates with an advanced Excel register for cybersecurity risks, SBOM, vulnerabilities, CRA reporting, and technical documentation.

Delivery: 7 Swedish + 7 English document templates in both Word and PDF, as well as 1 Excel workbook – a total of 29 delivery files. The Word/PDF series comprises a total of 28 A4 pages per language version.

Legally and technically reviewed: October 5, 2026
The template package has been reviewed against the Cyber Resilience Act, Regulation (EU) 2024/2847, including Articles 13–14 and Annexes I, II, and VII, as well as the European Commission's current implementation and reporting guidance. The package is designed for practical compliance work during 2026/2027.

Important CRA dates 2026–2027

The CRA is already in force, but different obligations begin to apply at different times:

  • September 11, 2026: manufacturer reporting obligations for actively exploited vulnerabilities and severe incidents became applicable.
  • December 11, 2027: the CRA's main product and cybersecurity requirements become fully applicable.

This means that organizations should not wait until 2027 to build risk assessments, vulnerability management, reporting routines, technical documentation, and evidence chains.

What is included in the package

Template / tool Swedish English Format
CRA Implementation & Compliance Plan 2 pages 2 pages Word + PDF
Cybersecurity Risk Assessment 2 pages 2 pages Word + PDF
Vulnerability Management & CVD Policy 2 pages 2 pages Word + PDF
Incident & Vulnerability Reporting 24h/72h 2 pages 2 pages Word + PDF
Technical Documentation & Conformity Checklist 2 pages 2 pages Word + PDF
User Information, Security Updates & Support Period 2 pages 2 pages Word + PDF
Detailed User Guide 2 pages 2 pages Word + PDF
CRA Compliance Register – Risk, SBOM, Vulnerability & Reporting Bilingual workbook Excel (XLSX)
Built for a complete CRA workflow
The CRA is not just about a single policy. A company must be able to demonstrate how cybersecurity risks are identified and mitigated, how components and vulnerabilities are tracked, how actively exploited vulnerabilities and severe incidents are reported, how technical documentation is built, and how security updates are handled during the support period. Therefore, the package integrates governance, risk assessment, SBOM, CVD, incident reporting, technical documentation, user information, and an Excel register.

Which companies are affected by the CRA?

The CRA targets products with digital elements made available on the EU market. This can include both hardware and software, as well as many connected or network-related products.

The package is primarily built for manufacturers, but checklists and user guides also help identify issues that importers and distributors need to verify. The exact role must always be assessed based on the actual supply chain and product.

Cybersecurity Risk Assessment – a core component of the CRA

The CRA requires the manufacturer to conduct a cybersecurity risk assessment for products with digital elements and take the result into account during planning, design, development, production, delivery, and maintenance.

The risk template and Excel register help the organization document:

  • product, version, and intended use,
  • assets and security-critical functions,
  • threat and misuse scenarios,
  • likelihood and impact,
  • existing controls,
  • residual risk,
  • action plan, responsible party, and deadline,
  • connection to the CRA's essential cybersecurity requirements.

SBOM, Vulnerability Management, and Coordinated Vulnerability Disclosure

The CRA's vulnerability requirements mean that the manufacturer must be able to identify and document vulnerabilities and components included in the product. Annex I specifies, among other things, that vulnerabilities and components must be identified and documented, including through a machine-readable SBOM that at least covers the product's top-level dependencies.

Therefore, the package contains:

  • SBOM register in Excel,
  • component/version/supplier/PURL/CPE,
  • direct or transitive dependency,
  • CVE/advisory and severity,
  • fixed version and review date,
  • CVD policy and external vulnerability contact,
  • triage, remediation, and disclosure routine.

Practical deep dive – CRA SBOM and risk assessment: Read our new step-by-step guide to cybersecurity risk assessment, software dependencies, and machine-readable SBOM. It explains how companies can document components, vulnerabilities, risk decisions, and technical evidence ahead of the main requirements taking effect on December 11, 2027. The article also distinguishes these preparations from the reporting obligations that have been in effect since September 11, 2026.

CRA Reporting: 24 hours, 72 hours, and final report

Since September 11, 2026, manufacturers must report actively exploited vulnerabilities and severe incidents affecting the security of products with digital elements.

The European Commission's reporting guidance generally states:

  • within 24 hours: early warning after the organization becomes aware,
  • within 72 hours: full notification,
  • actively exploited vulnerability: final report no later than 14 days after corrective or mitigating measures become available,
  • severe incident: final report within one month from the 72-hour notification.

The Excel file has a dedicated sheet for reporting cases where the 24h and 72h deadlines are calculated automatically from the awareness date and time.

Technical Documentation – Annex VII

The CRA's technical documentation must provide supervisory and conformity evidence for the product. The package's technical documentation checklist includes:

  • product description and intended use,
  • architecture, component relationships, and secure development process,
  • SBOM and vulnerability handling,
  • cybersecurity risk assessment,
  • support period and justification,
  • applied standards/specifications,
  • test and verification data,
  • EU declaration of conformity and release gate.

User Information – Annex II

User information must, among other things, enable the user to identify the manufacturer and product, find a point of contact for vulnerabilities, understand the intended use and relevant security conditions, as well as receive instructions for secure installation, use, updates, and decommissioning.

The template therefore has a dedicated worksheet for Annex II-style customer/user information and a clear field for the support period end date.

Support Period and Security Updates

The manufacturer must determine a support period that reflects the expected useful life of the product, taking into account, among other things, the nature of the product, expected use, and relevant market conditions. The CRA's general rule is that the support period should normally be at least five years, unless the product is reasonably expected to be used for a shorter time.

The package helps the organization document:

  • expected product lifetime,
  • determined support period,
  • justification and evidence,
  • security updates and distribution,
  • end date to be communicated to users.

The CRA also contains requirements for how long security updates must be kept available. Therefore, the organization should plan for both distribution and long-term availability of relevant updates.

Conformity Assessment, EU Declaration, and CE

Which conformity assessment path is permitted depends on, among other things, the product's CRA classification. The package contains checkpoints for:

  • standard product/default category,
  • important product class I,
  • important product class II,
  • critical product,
  • applicable standards/specifications,
  • notified body if applicable,
  • EU declaration of conformity,
  • CE release gate.

The template does not replace a formal product classification or external conformity assessment when required.

Excel register – more than a static checklist

The included XLSX file is a practical compliance register with separate tabs for:

  • Dashboard – key performance indicators and important CRA dates,
  • Product Register – products, versions, classification, and support period,
  • Risk Register – risk level and action plan,
  • SBOM – components, version data, and vulnerability link,
  • Vulnerability Register – CVE/advisories, severity, and status,
  • Reporting Deadlines – automatic 24h/72h deadlines,
  • Evidence Checklist – technical documentation and evidence chain,
  • Sources – key official CRA sources.

The workbook contains data validation, risk level formulas, and automated deadline calculations, but is designed so that the user can further customize it.

CRA versus NIS2 – different focus

The CRA and NIS2 can both be relevant to the same organization, but they have different focuses. The CRA is primarily a product regulation for cybersecurity in products with digital elements and their vulnerability management. NIS2/cybersecurity regulation focuses more on the risk management and incident reporting of organizations as providers of essential or important services.

Sanctions – why documentation matters

The CRA contains significant administrative penalty levels. For certain core violations, maximum administrative fines can reach 15 million euros or 2.5 percent of total global annual turnover, whichever is higher, subject to the conditions and exceptions set out in the regulation.

Recommended workflow

  1. Identify products and economic actor role.
  2. Classify the product according to the CRA.
  3. Conduct and document the cybersecurity risk assessment.
  4. Build SBOM and CVD/vulnerability process.
  5. Determine support period and update strategy.
  6. Prepare technical documentation and user information.
  7. Set up 24h/72h reporting and chain of responsibility.
  8. Carry out conformity assessment and collect evidence.
  9. Keep registers updated after release and during the support period.

Frequently Asked Questions about the CRA

Are reporting requirements already in effect?

Yes. Manufacturers' CRA reporting obligations for actively exploited vulnerabilities and severe incidents began on September 11, 2026.

When does the main part of the CRA take effect?

The main application begins on December 11, 2027.

Do we need an SBOM?

The CRA's vulnerability handling requirement includes documentation of components and vulnerabilities, including a machine-readable SBOM that at least covers top-level dependencies.

Is the CRA the same as NIS2?

No. The CRA focuses on products with digital elements and the product cybersecurity lifecycle. NIS2 has a different organizational and operational focus. A company may be affected by both.

Does the CRA only apply to hardware?

No. The regulation covers products with digital elements and can include both hardware and software depending on the product and market situation.

Are Swedish and English templates included?

Yes. All seven Word/PDF documents are provided in both Swedish and English.

Is Excel included?

Yes. The package contains a separate XLSX workbook for product registers, risks, SBOM, vulnerabilities, reporting deadlines, and evidence.

Is this a certification?

No. The package is a professional documentation and work support tool. It does not replace a notified body, product testing, external cybersecurity testing, or individual legal assessment when required.

Format and delivery

  • 7 Swedish document templates + 7 English document templates.
  • 14 DOCX + 14 PDF + 1 XLSX = 29 files in total.
  • 28 A4 pages per Word/PDF format series.
  • Excel workbook with 8 compliance tabs.
  • Digital product – no physical goods are shipped.

Legal basis and official sources

Important: The CRA is a technical and legal product regulatory framework. Product classification, conformity assessment, applicable standards, and reporting obligations must be verified based on the actual product, the actor's role, and the distribution model. The template package is a structured work and documentation aid – not a guarantee of full compliance in every individual situation.
  • 5 stars: 8 (73%)
  • 4 stars: 3 (27%)
  • 3 stars: 0 (0%)
  • 2 stars: 0 (0%)
  • 1 star: 0 (0%)
H
Hanna Holmberg
Bra arbetsmaterial

Framför allt ville jag slippa börja med ett tomt dokument för Cyber Resilience Act (CRA) Compliance 2026/2027. Det här blev framför allt ett sätt att få bättre överblick. Det hjälpte mig särskilt att skriva ner våra interna rutiner mer konsekvent. Resultatet blev precis den start jag behövde.

L
Lina Gustafsson
Bonne base de travail

J'ai utilisé le modèle «Cyber Resilience Act (CRA) Compliance 2026/2027» pour préparer une première version. J'ai modifié quelques passages pour mon cas. Très satisfait de cet outil pratique.

K
Karin Hedström
Handig en overzichtelijk

Ik gebruikte het sjabloon voor ‘Cyber Resilience Act (CRA) Compliance 2026/2027’ als vertrekpunt. De onderdelen waren overzichtelijk opgebouwd. Voor ons werkte dit erg prettig.

S
Sara Hammar
Goede basis met aanpassingen

Ik gebruikte het sjabloon voor ‘Cyber Resilience Act (CRA) Compliance 2026/2027’ als vertrekpunt. Zo was meteen duidelijk welke gegevens nog ontbraken. Een goede basis, met nog wat eigen werk.

M
Malin Johansson
Praktisk i vårt ärende

Hade ganska ont om tid när jag skulle ordna Cyber Resilience Act (CRA) Compliance 2026/2027, så det var skönt att ha något konkret att arbeta från. Helheten kändes saklig och ganska lätt att arbeta med. Den engelska versionen gjorde det lättare att dela underlaget med fler. Det här gav oss faktiskt mer arbetsro i processen.

E
Elin Söderström
Genomtänkt upplägg

Vi behövde ta fram ett underlag för Cyber Resilience Act (CRA) Compliance 2026/2027, och det sparade en hel del förarbete. Inget onödigt krångel i upplägget, vilket jag uppskattar. Den engelska versionen gjorde det lättare att dela underlaget med fler. Det hjälpte mig särskilt att skriva ner våra interna rutiner mer konsekvent. Resultatet blev precis den start jag behövde.

E
Emma Håkansdotter
Hyödyllinen pohja

Käytin mallia ”Cyber Resilience Act (CRA) Compliance 2026/2027” ensimmäisen version laatimiseen. Rakenteen avulla puuttuvat tiedot löytyivät nopeasti. Olen kokonaisuuteen tyytyväinen.

A
Anna Lindgren
Genomtänkt upplägg

Vi ville kunna prata igenom Cyber Resilience Act (CRA) Compliance 2026/2027 med samma underlag framför oss, och det fungerade bra. Det var enkelt att bocka av de punkter vi hade kvar att gå igenom. Den engelska versionen gjorde det lättare att dela underlaget med fler. Resultatet blev precis den start jag behövde.

L
Lucas Larsson
Buena base con ajustes

Utilicé la plantilla «Cyber Resilience Act (CRA) Compliance 2026/2027» para preparar un primer borrador. Tuve que adaptar algunas frases a nuestro caso. Buen material, aunque requiere pequeños cambios.

N
Nora Berggren
Genomtänkt upplägg

Framför allt ville jag slippa börja med ett tomt dokument för Cyber Resilience Act (CRA) Compliance 2026/2027. Bra med en mall som lämnar plats för egna förutsättningar. Den engelska versionen gjorde det lättare att dela underlaget med fler. Det hjälpte mig särskilt att skriva ner våra interna rutiner mer konsekvent. Resultatet blev precis den start jag behövde.

S
Sofia Åkesson
Nöjd med upplägget

Det märks att materialet om Cyber Resilience Act (CRA) Compliance 2026/2027 är tänkt att kunna bearbetas vidare. Det gick att anpassa upplägget utan att tappa den röda tråden. Den engelska versionen gjorde det lättare att dela underlaget med fler. Bra hjälp på vägen, med utrymme för egna kompletteringar.