CRA Obligations in Practice: A Legal & Compliance Officer’s Guide

Practical guidance for Legal and Compliance teams to understand what the EU Cyber Resilience Act requires you to document, report, and demonstrate — from product scope and manufacturer obligations to reporting deadlines and compliance evidence.

Determine which products fall within CRA scope and how they are classified

Understand Article 13 and Article 14 obligations and reporting requirements

- Build a product-level compliance program with the documentation and evidence CRA requires

CRA reporting obligations apply from 11 September 2026.

Full application follows on 11 December 2027.

What you will learn

CRA Scope and Product Classification

Understand which products fall within CRA scope, how open-source and commercial software are treated, and which conformity assessment route may apply.

Manufacturer and Reporting Obligations

Learn what Articles 13 and 14 require — from secure development, SBOMs, and vulnerability handling to the 24-hour and 72-hour reporting process.

Manufacturer and Reporting Obligations

See which technical documentation, vulnerability assessments, declarations, SBOMs, and release-level records need to be maintained to demonstrate compliance.

Timelines, Penalties, and Compliance Planning

Understand the CRA’s key application dates, enforcement and penalty structure, and how to turn the requirements into an actionable compliance program.

Make CRA Compliance Demonstrable

Support your CRA compliance program with verifiable release-level evidence connecting software artifacts to their source, build process, security checks, approvals, and release policy.

CRA Obligations in Practice:
A Legal & Compliance Officer’s Guide

Practical guidance for Legal and Compliance teams to understand what the EU Cyber Resilience Act requires you to document, report, and demonstrate — from product scope and manufacturer obligations to reporting deadlines and compliance evidence.

Determine which products fall within CRA scope and how they are classified

Understand Article 13 and Article 14 obligations and reporting requirements

- Build a product-level compliance program with the documentation and evidence CRA requires

CRA reporting obligations apply since 11 September 2026.

Full application follows on 11 December 2027.

What you will learn

CRA Scope and Product Classification

Understand which products fall within CRA scope, how open-source and commercial software are treated, and which conformity assessment route may apply.

Manufacturer and Reporting Obligations

Learn what Articles 13 and 14 require — from secure development, SBOMs, and vulnerability handling to the 24-hour and 72-hour reporting process.

Documentation and Compliance Evidence

See which technical documentation, vulnerability assessments, declarations, SBOMs, and release-level records need to be maintained to demonstrate compliance.

Timelines, Penalties, and Compliance Planning

Understand the CRA’s key application dates, enforcement and penalty structure, and how to turn the requirements into an actionable compliance program.

What you will learn

CRA Scope and Product Classification

Understand which products fall within CRA scope, how open-source and commercial software are treated, and which conformity assessment route may apply.

Manufacturer and Reporting Obligations

Learn what Articles 13 and 14 require — from secure development, SBOMs, and vulnerability handling to the 24-hour and 72-hour reporting process.

Manufacturer and Reporting Obligations

See which technical documentation, vulnerability assessments, declarations, SBOMs, and release-level records need to be maintained to demonstrate compliance.

Timelines, Penalties, and Compliance Planning

Understand the CRA’s key application dates, enforcement and penalty structure, and how to turn the requirements into an actionable compliance program.

Make CRA Compliance Demonstrable

Support your CRA compliance program with verifiable release-level evidence connecting software artifacts to their source, build process, security checks, approvals, and release policy.

Make CRA Compliance Demonstrable

Support your CRA compliance program with verifiable release-level evidence connecting software artifacts to their source, build process, security checks, approvals, and release policy.