The CRA's Annex I lists essential cybersecurity requirements that every product with digital elements must satisfy. These aren't vague guidelines โ they're legally binding conditions for placing products on the EU market.
Security Requirements (Product Properties)
- Risk-appropriate security โ Protection level proportionate to the cybersecurity risks
- No known exploitable vulnerabilities โ Products must ship without known exploitable vulnerabilities
- Secure default configuration โ Security features enabled by default; option to reset to secure state
- Protection against unauthorized access โ Authentication, access control, integrity protection
- Confidentiality protection โ Encryption of data at rest and in transit where appropriate
- Data integrity โ Mechanisms to detect and prevent unauthorized modification
- Data minimization โ Process only data necessary for the intended purpose
- Availability and resilience โ Design for resilience against denial-of-service attacks
- Minimal attack surface โ Reduce the exposure to the extent possible
- Incident impact mitigation โ Mechanisms to limit the impact of security incidents
- Security logging โ Record relevant security events
- Secure update mechanism โ Ability to apply security updates, ideally automatically
Vulnerability Handling Requirements
- Identify and document vulnerabilities and components (SBOM)
- Apply effective patches without undue delay
- Provide free security updates during the support period
- Establish a coordinated vulnerability disclosure policy
- Share relevant information about fixed vulnerabilities
Kubernetes Recipes
A practical guide for container orchestration and deployment by Grzegorz Stencel & Luca Berton (Apress).
Watch on Skillshare โPractical Implementation
Map each requirement to specific technical controls in your product architecture. Document the mapping in your technical file. This documentation is what assessors โ or market surveillance authorities โ will review.
Luca Berton