Recently, Techstrong Research released our PulseMeter report, “Tackling CI/CD Security Anti-Patterns.” Our research shed light on the evolving landscape of continuous integration/continuous deployment (CI/CD) pipeline security, drawing from the collective wisdom and experiences of professionals across DevOps, DevSecOps, software development and security disciplines.

Our aim is not merely to explore the challenges but to provide guidance toward actionable steps and best practices that can fortify the backbone of modern software delivery processes. The findings of our research underscore a pressing reality: The security of the software supply chain and CI/CD pipelines is now as critical as the integrity of physical supply chains in traditional sectors.

Step 1 of 7

14%

Which of the following best describes how you currently monitor and manage systems across your hybrid cloud environment?(Required)

Multiple separate tools for different environments

Multiple separate tools for different monitoring and management functions

Single consolidated dashboard

Custom built monitoring and management solution

No full monitoring and management solution

Don’t know

How valuable would it be for your monitoring and management solution to incorporate predictive analytics to help you identify and address system issues that are critical and not waste time or effort working through all the data and “noise” that is not critical?(Required)

Extremely valuable

Moderately valuable

Somewhat valuable

Slightly valuable

Not valuable

How do you most typically address potential system issues BEFORE they impact your operations?(Required)

Automated workflows and playbooks to remediate potential issues as soon as they are detected

An orchestrated response process that leverages automation, AI, and human expertise to rapidly respond to potential issues

Advanced monitoring tools such as predictive analytics and anomaly detection to proactively identify and address potential issues

Respond to issues as they arise, using manual processes and troubleshooting techniques

A combination of automated remediation, orchestrated response, and/or proactive monitoring to address potential system issues

Don’t know

Other

What methods does your organization use to control and monitor cloud/IT spending?(Required)

Centralized procurement processes

Pre-approved budget thresholds

Automated cost monitoring tools

Department-level spending controls

Regular cost audits and reviews

Cloud cost optimization platform

Approval workflows for resource provisioning

Native financial operations tools provided by the cloud provider

No formal controls in place

Don’t know

Other

Please specify:

Which methods do you rely on most to detect security vulnerabilities in your systems?(Required)

Automated scanning tools

Manual assessments

Vendor notifications

Threat modeling (for early detection)

None of these

Don’t know

Other

Please specify:

What are the TWO most common ways you prioritize vulnerabilities to address within your environment?(Required)

Based on potential impact

Based on exploitability

Regulatory compliance requirements

Based on CVSS scores

Risk-based analysis of multiple factors

First-in-first-out approach

No formal prioritization process

Don’t know

How do you typically handle system updates and security patches?(Required)

Automated updates and patches

Manually review and apply updates and patches on a regular schedule

A combination of automation and manual review

Apply updates and patches on an as-needed basis.

Outsourced update and patch management

No defined process

Don’t know

Other

Δ

This comparison is not made lightly; as digital infrastructure becomes the backbone of global commerce and communication, the repercussions of security lapses in software delivery can have widespread and consequential impacts. Our study reveals that the risks to software supply chains demand rigorous attention and strategic action, echoing the necessity for a shift in how organizations approach DevOps and CI/CD security.

A significant portion of our research was dedicated to identifying CI/CD security anti-patterns—practices that, albeit unintentionally, may provide a false sense of comprehensive security and even introduce vulnerabilities into development pipelines. These anti-patterns, such as the incorporation of external code from unverified sources or the adherence to rudimentary security measures without advancing to more robust strategies, significantly broaden the attack surface accessible to cyber adversaries. The research emphasizes the criticality of recognizing and rectifying anti-patterns to help safeguard the software supply chain from potential breaches and attacks.

Insightful Survey Findings: A Wake-Up Call

The survey provides a stark illustration of the current state of CI/CD pipeline security. With 84% of respondents acknowledging the importance of CI/CD pipeline security—motivated by the sobering statistic that over 20% of organizations reported a security incident within their pipelines in the previous year—the message is clear: Pipeline security must be improved beyond current measures.

These incidents showed tangible impacts, including but not limited to delayed deployments and significant data breaches. Moreover, the survey identified source/image repositories and code as particularly vulnerable points within the software development life cycle (SDLC), with a significant emphasis on the risks posed by open source vulnerabilities, secrets exposures and insecure code. This feedback from the field underscores the necessity for a proactive stance on security measures, one that anticipates potential vulnerabilities and implements robust defenses against them.

Drawing from the insights garnered through our research, Techstrong Research advocates for a holistic, strategic approach to enhancing CI/CD pipeline security. This includes the deployment of defensive measures designed to prevent unauthorized tampering with software production processes and the rigorous vetting of CI/CD pipeline artifacts to ensure their integrity through comprehensive role definitions and strict authorization protocols. Our endorsement of the NIST SP 800-204D draft underscores our belief in the necessity of a foundational framework that organizations can adopt to bolster their CI/CD pipeline security. Furthermore, our research shines a spotlight on the pivotal role of software composition analysis (SCA) in fortifying CI/CD pipelines against security threats. SCA facilitates the meticulous tracking of software elements and their dependencies, enabling organizations to identify and mitigate vulnerabilities swiftly. This tool is invaluable not only for preventive security measures but also as a critical component of incident response strategies.

Beyond traditional security measures, the research highlights the use of cloud-native continuous integration approaches, including containerization, to enhance security. These methodologies provide a framework for executing builds and tests within isolated environments, thereby minimizing the risk of conflicts and vulnerabilities. The adoption of containerization offers a myriad of benefits, including standardized packaging, enhanced transportability and improved traceability of software from development through to production.

The PulseMeter report on CI/CD security anti-patterns serves as a clarion call to the industry. The imperative to secure the software supply chain and CI/CD pipelines is undeniable and urgent. In this era of unprecedented digital reliance, our collective commitment to advancing CI/CD pipeline security is not just beneficial—it’s essential. The journey ahead is challenging, but with informed strategies and collaborative efforts, we can significantly reduce the vulnerability of the software we deliver as part of our digital infrastructures.