Agile Software Development

Is DevOps Security A Single Person’s Responsibility?

In recent times, DevOps is becoming an increasingly popular approach to software development. DevOps helps in building, releasing, and managing software through faster and frequent cycles. According to GitLab’s latest industry survey, 84% of developers reported faster code release than before with DevOps. Nearly 57% said that code was released twice as fast, indicating a significant jump from last year’s 35%. Though organizations have embraced this integrated approach, they are slow to include security within this framework.

In this article at TechRepublic, Owen Hughes shares insights into GitLab’s latest survey and explains how to overcome security issues.

Survey Insights

  • Over 19% of respondents said that code was going out the door 10x faster.
  • 21% mentioned that they added source code management to their DevOps practices (15% increase from the previous year), 18% added continuous integration, and 13% added continuous delivery.
  • Nearly 25% of DevOps teams reported using full test automation—double the 2020 figure.
  • 31% of respondents said security teams were responsible for security, while 28% felt it was a shared responsibility.
  • More than 83% of security professionals believed that the ability to catch bugs should be benchmarked, based on which developer’s performance must be measured.

How to Overcome the Issue?

Industry experts believe that there must be coordinated responsibility between the security team, developers, and operations team. Additionally, planning the security policy around compliance requirements saves time and improves efficiency. Organizations must also include security tests early in the software development lifecycles to minimize revisions and patches. Furthermore, DevOps promotes the use of automation tools. Automating security processes will undoubtedly reduce the chances of human error.

To read the original article, click on

Related Articles

Back to top button

We use cookies on our website

We use cookies to give you the best user experience. Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.