DevSecOps Rising: How German Teams Embed Security into Pipeline
Tacking security onto the end of development has always been expensive. Now it’s also illegal. NIS2, the Cyber Resilience Act, and growing awareness of supply-chain risks are forcing German software teams to …
Tacking security onto the end of development has always been expensive. Now it’s also illegal. NIS2, the Cyber Resilience Act, and growing awareness of supply-chain risks are forcing German software teams to consider security from the very first line of code. DevSecOps is the path forward – but the cultural shift weighs heavier than any tool.
TL;DR
- The NIS2 Directive – whose transposition deadline was October 2024 and which Germany incorporated into national law in December 2025 – obligates approximately 30,000 German companies to implement verifiable security measures in software development, including supply-chain security.
- According to a Bitkom survey, only 38% of German software teams run automated security tests within their CI/CD pipeline; among companies with over 1,000 employees, that figure rises to 57%.
- SAST, DAST, and Software Composition Analysis (SCA) form the triad of automated code security – and can be integrated into existing pipelines without modifying source code.
- According to IBM X-Force, the average cost of a software supply-chain breach is $4.46 million – early detection within the pipeline can reduce that figure by up to 80%.
- “Shift Left” only works if developers experience security not as a brake, but as a feature – tooling, culture, and training must align.
The numbers speak clearly: Most software vulnerabilities stem from errors introduced during development – but discovered only in production. Fixing a flaw during the design phase costs, per IBM Systems Sciences Institute, six times less than fixing it post-deployment. Yet in many German development teams, security still arrives only at the end of the cycle – as a penetration test before release or an audit ahead of certification.
DevSecOps breaks this pattern. It embeds security checks directly into the CI/CD pipeline: every commit is automatically scanned for known vulnerabilities, insecure coding practices, and vulnerable open-source dependencies. The goal? Security becomes part of daily development – not an exception just before go-live.
NIS2 and Regulatory Pressure
The NIS2 Directive was due to be transposed into national law by October 2024 – Germany completed its implementation in December 2025. The directive significantly expands the scope of affected organizations. In addition to critical infrastructure operators, it now covers companies in manufacturing, food production, waste management, postal services, and chemicals – roughly 30,000 organizations in Germany, according to the BSI (Federal Office for Information Security).
Three NIS2 requirements are especially relevant to software development:
Supply-chain risk management: Companies must assess the security posture of their suppliers – including software vendors. Using open-source libraries without knowing their security status may constitute a violation.
Incident reporting: Security incidents must be reported within 24 hours. Without automated detection built into the pipeline, teams often learn about vulnerabilities only after they’ve been exploited.
Auditability: Organizations must be able to demonstrate that appropriate technical safeguards have been implemented. A documented DevSecOps pipeline with automated scanning qualifies as such evidence.
Parallel to NIS2, the EU’s Cyber Resilience Act (CRA), effective from 2027, will require manufacturers to ensure the security of products containing digital elements across their entire lifecycle. For software vendors, this means Security by Design becomes a legal obligation.
The SAST-DAST-SCA Triad
The three pillars of automated code security integrate seamlessly into any modern CI/CD pipeline – often within days:
SAST (Static Application Security Testing) analyzes source code without executing it. Tools like SonarQube, Checkmarx, or Semgrep scan for patterns of insecure programming: SQL injection, cross-site scripting, hardcoded credentials, or weak cryptography. SAST ideally runs on every pull request – giving developers feedback before code is merged.
DAST (Dynamic Application Security Testing) tests the running application from the outside. Tools like OWASP ZAP or Burp Suite simulate attacks against the deployed app and uncover runtime-only flaws – such as broken authentication, exposed API endpoints, or misconfigured servers. DAST typically runs in staging environments as part of the release pipeline.
SCA (Software Composition Analysis) scans an application’s dependencies – npm packages, Maven dependencies, Python libraries – for known vulnerabilities. Given that modern applications consist of 80-90% third-party code, SCA is no longer optional. Tools like Snyk, Dependabot, or Mend (formerly WhiteSource) flag known CVEs – and often provide patches on the spot.
Together, these three approaches cover the vast majority of automatically detectable vulnerabilities. According to Veracode, enterprises with integrated pipeline security cut their Mean Time to Remediation (MTTR) by 60% compared to those relying solely on periodic audits.
In Practice: How German Teams Implement DevSecOps
The real challenge lies in culture – not technology. Tools can be deployed; but developers who perceive security as a roadblock will find ways to bypass them.
Allianz Technology: The Allianz Group’s IT subsidiary launched a program in 2024 to train every developer as a “Security Champion.” Each team designates one person as its security point of contact – and grants them 20% of their working time for that role. Security Champions collaborate with the central AppSec team to decide which SAST rules should be configured as “breaking” (blocking the pipeline) versus “warning” (non-blocking notifications).
SAP: As Europe’s largest software vendor, SAP operates one of Germany’s most extensive DevSecOps pipelines. Every commit to its product codebase automatically undergoes SAST, SCA, and container scanning. Results appear directly inside developers’ IDEs – not just in a separate security dashboard. Principle: Security feedback must land where code is written.
Mid-sized companies: Many German Mittelstand software firms adopt a pragmatic approach. A common rollout sequence: introduce SCA first (effort: one day), then activate SAST in the pipeline (one week), and finally add DAST for critical applications (two to four weeks). Open-source options – SonarQube Community, OWASP ZAP, Trivy – cost zero licensing fees – only implementation time.
What Endures: Culture Eats Tooling
Experience shows that companies implementing DevSecOps through tools alone fail more often than those prioritizing cultural transformation. Three principles have proven effective:
Don’t punish developers: When the security pipeline blocks a build, feedback must be constructive. Developers need context – what’s the risk? How do you fix it? Why does it matter? Tools that merely output “Critical Finding” without explanation or remediation guidance breed frustration – not security.
Gradually tighten thresholds: Start by blocking the pipeline only for Critical and High severity findings. Treat Medium and Low findings as warnings, tracked separately in a backlog. Only raise the bar once teams gain confidence and routine.
Make security visible: Dashboards showing how vulnerability counts evolve over time, how quickly findings get resolved, and which teams perform best. Positive reinforcement works better than compliance pressure.
DevSecOps isn’t a destination – it’s a maturing process. Companies starting now gain an advantage – not just regulatory, but in the quality of their code.
Frequently Asked Questions
What’s the difference between DevOps and DevSecOps?
DevOps unifies development and operations into a continuous process. DevSecOps extends that model by treating security as an equal, integrated dimension – security checks aren’t tacked on later, but embedded into every stage of the pipeline.
Do all companies need to comply with NIS2?
NIS2 applies to companies with at least 50 employees or €10 million in annual turnover across 18 defined sectors. Smaller firms may still fall under its scope if they serve as suppliers to critical infrastructure. Checking your business against the BSI’s sector list is strongly recommended.
How much does DevSecOps implementation cost?
The open-source stack – SonarQube Community, OWASP ZAP, Trivy, Dependabot – incurs no license fees – only implementation effort. Commercial platforms like Snyk, Checkmarx, or Veracode start at around €10,000 per year for small teams. ROI comes from reduced incident costs and accelerated release cycles.
Editor's Picks
cloudmagazinCloud Professionals: Why Germany Is Catching Up on UpskillingcloudmagazinSaaS Consolidation: How CIOs Tame Tool SprawlcloudmagazinEdge Computing and Industry 4.0More from the MBF Media Network
MyBusinessFutureKI Made in Germany: 935 StartupsDigital ChiefsEU AI Act 2026: What Companies Must ImplementSecurityTodayCybersecurity Trends 2026Header Image Source: Pexels / Tima Miroshnichenko
Translated from the German original using artificial intelligence. The German version is authoritative.

