← CRA Glossary
Product Security Engineering

DevSecOps

DevSecOps is the practice of integrating security tools, testing, and responsibilities throughout the software development and operations pipeline - making security a shared responsibility of development, security, and operations teams rather than a final-stage gate. The CRA does not require DevSecOps or an SDLC. DevSecOps is one way to meet the Annex I requirements in continuous delivery environments.

DevSecOps is the practice of integrating security tools, testing, and responsibilities throughout the software development and operations pipeline - making security a shared responsibility of development, security, and operations teams rather than a final-stage gate. The CRA does not require DevSecOps or an SDLC. DevSecOps is one way to meet the Annex I requirements in continuous delivery environments.

Product Security Engineering

Last updated 16 November 2026

What Is DevSecOps?

DevSecOps extends the DevOps practice of integrating development and operations by adding security as a core, automated component of the development pipeline. In a DevSecOps model, security testing (SAST, DAST, SCA), security configuration validation, and secret scanning are all automated and run on every code commit or build - security is 'shifted left' into the development process rather than being a separate audit gate. The goal is to detect security issues early, when they are cheapest to fix, and to prevent known vulnerability classes from ever reaching production. For manufacturers of CRA-covered products, DevSecOps provides the technical infrastructure to meet the Annex I requirements and to keep the evidence, without creating bottlenecks in release velocity. The CRA itself requires neither DevSecOps nor an SDLC.

CRA reference:Annex I

Key DevSecOps Controls for CRA Manufacturers

A CRA-aligned DevSecOps pipeline should incorporate the following automated security controls:

  • SAST (Static Application Security Testing): Analyses source code and binaries for known vulnerability patterns (CWE instances). Tools: Semgrep, CodeQL, Coverity, SonarQube.
  • SCA (Software Composition Analysis): Identifies known CVEs in third-party dependencies and generates the SBOM. Tools: Dependency-Track, Snyk, FOSSA, Syft.
  • Secret scanning: Detects hardcoded credentials, API keys, and cryptographic material committed to source code. Tools: Gitleaks, Trufflehog, GitHub Advanced Security.
  • DAST (Dynamic Application Security Testing): Tests running applications for exploitable vulnerabilities through automated attack simulation. Tools: OWASP ZAP, Burp Suite (automated).
  • Container scanning: Analyses container images for OS and application vulnerabilities. Tools: Trivy, Grype, Snyk Container.
  • Infrastructure-as-code scanning: Detects misconfiguration in deployment infrastructure. Tools: Checkov, tfsec.
CRA reference:Annex I

DevSecOps Pipeline Architecture for CRA

A practical DevSecOps architecture for a CRA-covered product manufacturer typically stages security controls through the pipeline:

Pre-commit (developer workstation): IDE plugins for SAST linting; secret scanning on git commit hooks.

CI pipeline (on every pull request): SAST scan of changed code; SCA scan with SBOM update; secret scanning; unit tests including security-relevant cases.

Build pipeline (on merge to main): Full SCA scan; container scanning; SBOM generation and signing; policy gate (fail build on new Critical findings without approved exception).

Release pipeline (on release candidate): DAST scan of integration environment; firmware binary analysis; SBOM publishing to Dependency-Track; security sign-off checkpoint.

Post-release monitoring and operate: Dependency-Track continuous CVE monitoring; EPSS score monitoring for SBOM components; alert to PSIRT on new Critical findings; coordinated vulnerability disclosure (CVD) intake and triage per OWASP DevSecOps Guideline 2.7.5.

CRA reference:Annex I

DevSecOps Culture and Shared Responsibility

DevSecOps is as much a cultural shift as a tooling change. The core principle is that security is everyone's responsibility - developers own the security of the code they write; security engineers provide tooling, guidance, and triage support; operations teams are responsible for secure deployment and monitoring. For CRA manufacturers, this means:

  • Security training for all developers, not just a dedicated security team.
  • Security champions in each development team who are the primary contact for security questions.
  • Published secure coding guidelines specific to the technology stack.
  • Blameless security retrospectives that treat security findings as learning opportunities.
  • Metrics that track security debt (number of open vulnerabilities by severity) alongside feature velocity.

Annex VII requires the cybersecurity risk assessment and the test reports in the technical documentation. DevSecOps provides pipeline artifacts - scan reports, SBOM records, policy gate outcomes - that can serve as this evidence.

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

Is DevSecOps required for CRA compliance or just recommended?+

It is not required. The CRA does not require DevSecOps, and it does not require a manufacturer to operate an SDLC (Commission guidance C(2026) 5252 (section 7.2)). Article 13(2) requires a cybersecurity risk assessment that is taken into account through planning, design, development, production, delivery and maintenance. DevSecOps is one way to do that in continuous delivery environments. A manufacturer using a traditional waterfall development process with separate security testing phases can also comply with the CRA, provided security is genuinely addressed. However, DevSecOps's automated, continuous approach provides stronger and more easily evidenced compliance than manual security processes.

How does secret scanning relate to CRA compliance?+

The CRA prohibits products from shipping with hardcoded credentials. Secret scanning in the DevSecOps pipeline detects hardcoded passwords, API keys, private keys, and certificates committed to source code - a prerequisite for ensuring the CRA's 'no default passwords' and authentication requirements are met. Secret scanning should be run on the full git history when first implemented, not just new commits, as historical commits may contain long-forgotten credentials that are still valid.

Can small manufacturers implement DevSecOps affordably?+

Yes. Many high-quality DevSecOps tools are open-source or have free tiers for small organisations. GitHub Advanced Security includes CodeQL, secret scanning, and Dependabot for free on public repositories. OWASP ZAP is free. Trivy and Grype for container scanning are open-source. Dependency-Track is open-source. A small manufacturer can build a functional CRA-oriented DevSecOps pipeline using these tools at minimal cost, with the primary investment being the engineering time to integrate and tune them.

Sector checklists covering DevSecOps

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)).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)).Embedded Linux DevicesEmbedded Linux devices span a vast range - from network gateways and industrial HMIs to set-top boxes and smart displays. All are products with digital elements subject to the CRA. The open-source nature of Linux creates specific obligations around SBOM completeness and CVE monitoring. The class follows the core functionality of each device (Article 7(1)). An industrial HMI is default class. A network gateway whose core functionality is a router is Important Class I (Annex III, point 12). Industrial or infrastructure use does not change the class.

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

View checklists →