← CRA Glossary
CRA Legal Terms

Secure by Design

Secure by design means that security is built into a product's architecture and development process from the earliest design stage, rather than added as an afterthought after development is complete. The EU Cyber Resilience Act's essential requirements in Annex I mandate a secure-by-design approach for all products with digital elements.

Secure by design means that security is built into a product's architecture and development process from the earliest design stage, rather than added as an afterthought after development is complete. The EU Cyber Resilience Act's essential requirements in Annex I mandate a secure-by-design approach for all products with digital elements.

CRA Legal Terms

Last updated 19 July 2026

What Is Secure by Design?

Secure by design is an engineering philosophy in which security properties - confidentiality, integrity, availability, and resilience - are treated as first-class functional requirements from the earliest stages of product conception. Rather than treating security as a layer applied at the end of development (or, worse, only after a breach), secure-by-design organisations define security requirements alongside feature requirements, conduct threat modelling during architecture design, apply secure coding standards throughout development, and integrate security testing at every stage of the build pipeline. The approach recognises that the cost of fixing a security flaw increases exponentially the later in the lifecycle it is discovered.

CRA reference:Annex I Part I, Article 13(1)

Secure by Design as a CRA Requirement

The CRA's Annex I Part I requires manufacturers to ensure their products are designed, developed, and produced to achieve an appropriate level of cybersecurity based on the risks involved. The use of 'designed' as the first verb in this formulation is deliberate: the regulation requires security to be addressed at the design stage, not retrofitted. Article 13(1) reinforces this by requiring the cybersecurity risk assessment to be incorporated into the product during planning and design. The essential requirements in Annex I - including least privilege, attack surface reduction, and data minimisation - are architectural properties that can only be achieved through design-stage decisions.

CRA reference:Annex I Part I, Article 13(1)

How Manufacturers Implement Secure by Design

Implementing secure by design requires embedding security into the Software Development Lifecycle (SDLC). Key practices include: defining security requirements and acceptance criteria before development begins; conducting formal threat modelling (e.g. using STRIDE or attack trees) during architecture design; applying secure coding standards such as OWASP Top 10 for web components or MISRA C for embedded firmware; conducting peer code review with security focus; integrating Static Application Security Testing (SAST) and dependency scanning into CI/CD pipelines; and requiring sign-off on security test results before any release reaches production. Security champions embedded in engineering teams help sustain this culture at scale.

CRA reference:Annex I Part I, Article 13(1)(2)

Common Mistakes

The most common failure of secure-by-design intent is treating threat modelling as a compliance checkbox - producing a document at the start of a project and then never revisiting it as the architecture evolves. A second error is siloing security reviews to a specialist team that only engages at the end of development sprints, removing engineers from security decision-making. Manufacturers also frequently focus secure-by-design efforts on the application layer while neglecting the hardware abstraction layer, bootloader, and update mechanism - components that often have greater security impact. Secure-by-design must extend to every tier of the product.

CRA reference:Annex I Part I

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

What is the difference between secure by design and secure by default?+

Secure by design refers to the development process - security is built into the architecture from the start. Secure by default refers to the shipped product configuration - the device arrives in the user's hands with security settings pre-configured to a protective state. Both are required by the CRA. A product can be designed with security in mind but still ship with insecure defaults; conversely, secure defaults cannot compensate for fundamental architectural security flaws.

Is threat modelling part of the secure-by-design obligation under the CRA?+

Threat modelling is not mentioned by name in the CRA, but it is the primary mechanism by which manufacturers can demonstrate that security was considered during design - a requirement of Annex I Part I and Article 13(1). Conformity assessment bodies and market surveillance authorities will look for evidence that the manufacturer systematically identified and addressed threats during product design. A documented threat model is the most widely accepted evidence of this.

Can a manufacturer achieve CRA compliance by hardening a product after development?+

No. The CRA requires security to be addressed during design and development, not retrofitted. Post-development hardening can reduce risk and is valuable, but it cannot compensate for architectural decisions that baked in insecurity - for example, a protocol choice that does not support encryption, or a data model that stores user credentials in plaintext. Manufacturers must address security requirements during the design phase, not as an afterthought before launch.

Sector checklists covering Secure by Design

Industrial Controllers & PLCsIndustrial controllers, PLCs, and SCADA components are default-class products under the CRA, because classification follows core functionality (Article 7(1)) and Annex III lists no industrial control category. They can use Module A internal control (Article 32(1)). These products have long operational lifetimes (10–20+ years), network connectivity, and significant safety implications. These facts raise the risk that the Article 13(2) risk assessment must address. Article 14 reporting applies from 11 September 2026, and the conformity obligations apply from 11 December 2027.Medical DevicesMedical devices regulated under the EU Medical Device Regulation (MDR) or In Vitro Diagnostic Regulation (IVDR) are generally excluded from the CRA. However, software products used in healthcare that are not classified as medical devices under MDR may fall within CRA scope. Manufacturers should carefully verify their product's regulatory classification.Smart Home DevicesSmart home devices, such as thermostats, smart speakers, lighting controllers and home security cameras, are among the most common products with digital elements in scope for the CRA. Thermostats and lighting controllers are default class, and Module A internal control is open to them (Article 32(1)). A smart speaker with a general purpose virtual assistant is Important Class I (Annex III, point 16). A home security camera, smart lock, baby monitor or alarm system is Important Class I (Annex III, point 17). So is a hub or software that centrally controls these security products.

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Secure by Design fits into your complete CRA compliance programme.

View checklists →