DEVELOPMENT ENVIRONMENTrelease v0.33.0-97 · design 2026-10-13 (5e68d8f)
Skip to content

Research report·

Impact of Platform Strategies on Security Practices in Software Development

Organisations without DevOps standardisation show between two and three times lower rates of integrating security practices into their CI/CD pipelines

This report examines the security practices that developers integrate into their CI/CD pipelines, with a particular focus on how platform standardisation approaches influence which security tools see adoption and success. In this report, platform standardisation refers to organisation-wide standardisation strategies for DevOps practices, and we categorise platform configurations into five distinct groups: specialised internal developer platforms (IDPs), dedicated teams or individuals responsible for developer experience, unified systems for managing DevOps processes, curated lists of approved tools, and organisations engaging in none of these approaches. This report is based on data from SlashData’s 30th edition of the Developer Nation survey and represents the adoption patterns of more than 4,700 professional developers using CI/CD pipelines.

Questions this report answers

Which security practices see the highest adoption, and which lag behind?

How does platform architecture (IDP vs curated tools vs unified systems vs no standardisation) affect security tool adoption?

Why do some security tools succeed in centralised platforms while others thrive in developer-controlled environments?

What are the implications of platform abstraction on developer awareness of security practices?

How does organisational size influence both platform choice and security maturity?

How does platform architecture impact deployment frequency?