Secure default configurations in accordance with CRA requirements

CRA Security by Default: Secure Products Out of the Box

Security by default is a core CRA requirement.

  • 01Full CRA conformity for default configurations
  • 02Minimisation of security risks through secure factory settings
  • 03Reduction of user misconfiguration through secure defaults
  • 04Strengthening trust in your digital products
11+Years of experience
120+Employees
540+Projects
ISO 27001certified

CRA Secure by Default: Safe Factory Settings for Digital Products

The Cyber Resilience Act mandates that products with digital elements must be securely configured out of the box. Secure by default means: no weak default passwords, encrypted communication as standard, automatic security updates and disabled unnecessary services. These requirements apply to all product categories from December 2027.

We guide you from gap analysis of your current default configurations through to fully CRA-compliant secure by default implementation with documentation for the EU declaration of conformity.

2 service modules

Service scope

01

Security by Default Gap Analysis

Comprehensive assessment of your current product configurations against CRA Security by Default requirements.

  • Detailed analysis of current default configurations
  • Identification of CRA compliance gaps
  • Risk assessment of insecure factory settings
  • Roadmap for Security by Default implementation
02

Implementation of Secure Defaults

Technical implementation and integration of Security by Default principles into your product development.

  • Design of secure default configurations
  • Integration into development and deployment processes
  • Automated security configuration management
  • Continuous monitoring and validation

5 phases

Our Approach

We work with you to develop a systematic Security by Default strategy that ensures both technical excellence and CRA compliance.

  1. Assessment of current product configurations and security settings

  2. Identification of CRA-relevant Security by Default requirements

  3. Design and development of secure default configurations

  4. Implementation and testing of Security by Default measures

  5. Validation of CRA conformity and final documentation

Sarah Richter

Your contact

Sarah Richter

Head of Information Security, Cyber Security

10+ years of experience, CISA, CISM, Lead Auditor, DORA, NIS2, BCM, Cyber and Information Security

Why ADVISORI for Secure by Default

  • 01Hands-on experience with CRA Annex I requirements and BSI guidance
  • 02Specialisation in secure product configurations and default hardening
  • 03End-to-end approach: technical implementation, documentation and conformity assessment
  • 04Experience with CE marking and EU declarations of conformity for software products

CRA Obligation from 2026

The mandatory reporting of actively exploited vulnerabilities applies from September 2026. Full secure by default requirements take effect from December 2027. Manufacturers must begin implementation now.

7 QUESTIONS, BRIEFLY ANSWERED

Frequently asked questions about CRA Cyber Resilience Act - Security by Default

What does secure by default mean under the Cyber Resilience Act?

Secure by default under the CRA means digital products must ship with the most secure available configurations out of the box. Specifically, the CRA mandates: no weak default passwords, encrypted communication as the default setting, automatic installation of security updates (with opt-out option) and disabling of unnecessary services. The BSI describes this as the configuration principle where default settings must actively contribute to enhancing product security.

When do CRA secure by default requirements take effect?

CRA requirements are phased in: from September 2026, manufacturers must report actively exploited vulnerabilities to ENISA and the relevant CSIRT within 24 hours. Full secure by default requirements under Annex I apply from December 2027 for all new products with digital elements placed on the EU single market.

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

Secure by design refers to integrating security throughout the entire product development process from the start. Secure by default concerns the delivery configuration: the product must be securely configured for the end user without requiring additional steps. The CRA requires both: security must be built into the architecture (by design) and default settings must provide maximum security (by default).

What specific secure by default measures does the CRA require?

The CRA requires among others: prohibition of generic or weak default passwords, automatic security updates with opt-out option for users, separation of security and feature updates where feasible, encrypted communication as default, minimal attack surface through disabling unnecessary interfaces and services, secure authentication mechanisms and access controls out of the box.

What are the penalties for CRA secure by default non-compliance?

Non-compliance with essential cybersecurity requirements including secure by default can result in fines of up to EUR 15 million or 2.5 percent of global annual turnover. Additionally, market surveillance authorities can order the recall of non-compliant products or prohibit their placement on the EU market.

Does secure by default apply to all CRA product categories?

Yes, secure by default applies to all three CRA product categories: standard products, important products (Class I and II) and critical products. The difference lies in the conformity assessment procedure: standard products may use self-assessment under Module A, while important and critical products require third-party assessment. The secure by default requirements themselves are identical across categories.

How does ADVISORI support CRA secure by default implementation?

ADVISORI guides manufacturers from gap analysis through to CRA-compliant implementation: we assess existing default configurations against CRA Annex I, develop secure default profiles, support implementation of automatic update mechanisms, conduct penetration testing of factory settings and prepare technical documentation for the EU declaration of conformity.