← CRA Glossary
Product Security Engineering

Defence in Depth

Defence in depth is a security strategy that employs multiple overlapping layers of security controls so that if one layer fails, others continue to protect the system. It is a core principle behind the CRA's essential requirements, which take a holistic view of product security rather than relying on any single mechanism.

Defence in depth is a security strategy that employs multiple overlapping layers of security controls so that if one layer fails, others continue to protect the system. It is a core principle behind the CRA's essential requirements, which take a holistic view of product security rather than relying on any single mechanism.

Product Security Engineering

Last updated 19 July 2026

What Is Defence in Depth?

Defence in depth is a security architecture principle derived from military strategy: rather than relying on a single defensive line, multiple overlapping layers of protection are deployed so that an attacker must defeat all layers, not just one. In product security, this means combining multiple different types of security controls - physical, firmware, OS, application, network, monitoring - such that the compromise of any single control does not lead to full system compromise. The term recognises the reality that no single security control is perfect: attackers will find flaws in any individual mechanism. Defence in depth ensures that flaws in one layer are compensated for by other layers, limiting the blast radius of any individual failure.

CRA reference:Annex I

Defence in Depth in CRA Essential Requirements

The CRA's Annex I essential requirements collectively implement a defence-in-depth approach to product security. No single requirement is presented as sufficient - the requirements span multiple layers:

  • Hardware layer: Secure boot, hardware-backed key storage, physical interface lockdown.
  • Firmware/OS layer: Least privilege, process isolation, memory protection.
  • Application layer: Input validation, authentication, authorisation, secure coding practices.
  • Communication layer: Encrypted communications, certificate validation, protocol security.
  • Update layer: Signed firmware updates, rollback protection, integrity verification.
  • Monitoring layer: Audit logging, anomaly detection, CVD policy for external input.
  • Process layer: SDLC, threat modelling, penetration testing, PSIRT.

A conformity assessment examines all these layers collectively - a product that excels in one area but has significant gaps in another does not satisfy the Annex I requirements.

CRA reference:Annex I

Applying Defence in Depth to IoT Product Design

A concrete defence-in-depth architecture for a connected IoT product might include:

Physical: Locked debug interfaces, tamper-evident enclosures. Boot: Secure Boot with hardware root of trust, rollback protection. OS: Read-only root filesystem, process isolation, AppArmor profiles, minimal installed packages. Network: Firewall denying all inbound connections except required services, TLS for all communications, certificate pinning for update server. Application: Input validation, authentication for all APIs, privilege separation between services. Update: Signed OTA updates, A/B partitioning, update server authentication. Monitoring: Syslog forwarding to operator SIEM, anomaly detection for abnormal network behaviour. Response: Published CVD policy with safe harbour, PSIRT process, CSAF advisory publication.

This layered architecture means an attacker exploiting a single application vulnerability cannot directly access the firmware update mechanism, and cannot bypass Secure Boot even if they achieve code execution.

CRA reference:Annex I

Documenting Defence in Depth for CRA Technical Files

The Annex VII technical file should document the product's defence-in-depth architecture to demonstrate to Notified Bodies and MSAs that the essential requirements are comprehensively addressed. Effective documentation approaches:

  • Security architecture diagram: A visual representation of all security layers, showing how they interact and overlap.
  • Control mapping: A table mapping each CRA Annex I essential requirement to the specific security controls that address it, showing which controls are primary and which are compensating.
  • Residual risk register: For identified threats where the defence-in-depth architecture does not provide complete mitigation, document the residual risk and the risk acceptance rationale.
  • Test coverage: For each security layer, reference the testing evidence that demonstrates the control is effective - pen test reports, code review findings, fuzzing results.

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

How many layers of defence are required for CRA compliance?+

The CRA does not specify a required number of layers - it specifies outcomes (the product must not have exploitable vulnerabilities, must have secure update mechanisms, must protect data, etc.). The number and nature of security layers required to achieve these outcomes depends on the product's complexity, connectivity, and risk classification. A simple sensor with limited connectivity needs fewer layers than a complex industrial gateway. Threat modelling should guide the depth of defence required for each specific product.

Does defence in depth mean every product needs penetration testing?+

For products claiming compliance with CRA essential requirements, independent penetration testing is a recommended means of verifying that the defence-in-depth architecture is effective in practice, not just on paper. The CRA does not mandate penetration testing by name, but it requires manufacturers to test their products' security. For Important Class products and any product in a high-risk category, penetration testing evidence significantly strengthens the conformity assessment case. Notified Bodies examining Important Class II products will typically expect penetration test evidence.

How does defence in depth relate to risk acceptance?+

Risk acceptance and defence in depth interact: where the defence-in-depth architecture cannot fully mitigate a risk (perhaps because a perfect control does not exist or is not feasible at the product's price point), the residual risk must be formally accepted. The CRA requires that residual risks be documented in the risk assessment and that mitigation measures have been considered. Defences-in-depth thinking helps identify whether the residual risk is truly irreducible or whether an additional compensating control could further reduce it. Undocumented risk acceptance - not formally acknowledging a gap - is a compliance weakness.

Sector checklists covering Defence in Depth

Consumer Routers & ModemsConsumer routers and modems are high-value targets for attackers and face specific CRA requirements around default credentials, remote management security, and firmware update integrity. Routers, internet modems, switches and wireless access points are Important Class I (Annex III, point 12), for home, industrial and critical infrastructure markets alike. No CRA harmonised standard is cited yet, so today a router needs a notified body for conformity assessment (Article 32(2)).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.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.Enterprise Networking EquipmentEnterprise networking equipment - switches, firewalls, load balancers, and network management systems - spans multiple Annex III classifications. Firewalls in hardware or software form and intrusion detection and prevention systems are Important Class II. Switches, routers, wireless access points, network management systems and SIEM systems are Important Class I. A load balancer is default class unless its core functionality is a listed category, such as a web application firewall. Class II products always need third-party conformity assessment (Article 32(3)). Class I products need a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)).

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 Defence in Depth fits into your complete CRA compliance programme.

View checklists →