Is There Tension Between Developers and Security Professionals?

“Everyone knows security needs to be baked into the development lifecycle, but that doesn’t mean it is,” writes ZDNet, reporting on a new survey they say showed that “long-standing friction between security and development teams remain.”

The results came from GitLab’s “2019 Global Developer Report: DevSecOps” survey of over 4,000 software professionals.

Nearly half of security pros surveyed, 49%, said they struggle to get developers to make remediation of vulnerabilities a priority. Worse still, 68% of security professionals feel fewer than half of developers can spot security vulnerabilities later in the life cycle. Roughly half of security professionals said they most often found bugs after code is merged in a test environment.

At the same time, nearly 70% of developers said that while they are expected to write secure code, they get little guidance or help. One disgruntled programmer said, “It’s a mess, no standardization, most of my work has never had a security scan.” Another problem is it seems many companies don’t take security seriously enough. Nearly 44% of those surveyed reported that they’re not judged on their security vulnerabilities.

ZDNet also cites Linus Torvalds’ remarks on the Linux kernel mailing list in 2017, complaining about how security people celebrate when code is hardened against an invalid access. “[F]rom a developer standpoint, things really are not done. Not even close. From a developer standpoint, the bad access was just a symptom, and it needs to be reported, and debugged, and fixed, so that the bug actually gets corrected. So from a developer standpoint, the end point of hardening is just the starting point, and when you think you’re done, we’re really only getting started.”

Torvalds then pointed out that the user community also has a third set of entirely different expectations, adding that “the number one rule of kernel development is that ‘we don’t break users’. Because without users, your program is pointless, and all the development work you’ve done over decades is pointless… and security is pointless too, in the end.” Juggling the interest of users and developers, Torvalds suggests security people should adopt “do no harm” as their mantra, and “when adding hardening features, the first step should *ALWAYS* be ‘just report it’. Not killing things, not even stopping the access. Report it. Nothing else.”

Share on Google+

View source

Codice amico Very Mobile Diagonal Media Digital Marketing