News · August 23, 2022
GitLab survey: security now drives how teams choose DevOps tools
GitLab's annual survey of more than 5,000 software professionals shows security moving to the top of the agenda and toolchain sprawl eating engineering time. Both points matter for anyone running a mixed in-house and external team.
What happened
- GitLab reported on August 23, 2022 that its sixth annual survey of 5,001 software professionals, conducted in May, found security had overtaken cloud computing as the top investment area for DevOps teams.
- According to GitLab, nearly three-quarters of respondents had adopted a DevOps platform or planned to within the year, 69% wanted to consolidate their toolchains, and nearly 40% spent a quarter to half of their time maintaining or integrating tools, more than double the 2021 share.
- GitLab said 60% of developers release code faster than before.
- Virtualization Review reported that 53% of developers said they were fully responsible for security, up 14 points from 2021, and that 47% of teams had full test automation, nearly double the previous year.
Why it matters
Two signals stand out. Developers are being asked to own security, and they are losing large chunks of time to keeping tools glued together. Both get worse when work is spread across several vendors and contractors, each bringing its own setup.
If you use external engineers, give them your pipeline rather than letting each team build its own: one repository host, one CI configuration, shared security scanning and the same definition of done. It cuts maintenance time and makes security checks consistent no matter who writes the code.
Sources
- GitLab: GitLab Inc.'s Sixth Annual Global DevSecOps Survey Shows Security is the Driving Force for Choosing a DevOps Platform
- Virtualization Review: Survey: For DevOps Pros, It's 'Security, Security, Security'
This post is CMM’s own summary and commentary on publicly reported news. Facts are attributed to the sources linked above; please read them for full details. CMM is not affiliated with these publishers or with the companies mentioned, and trademarks belong to their owners. Prepared with AI assistance. Corrections or requests: [email protected]. See our editorial policy.
Want help with this?
Tell us what you need, and we will suggest the right team model on a short call.
Talk to us