Resources
Resources

AppSec and DevOps: How to bridge the DevSecOps Disconnect

  • Share on Twitter
  • Share on LinkedIn
  • Share on Instagram

It’s a tale as old as time: developers want to ship an app but are lambasted with security requests, and security teams want to secure an app but are brought in too late to do their job without knocking some heads in the process. The ensuing result is usually insecure code and frustrated teams. 

The time is ripe for rethinking how developers and security teams work together. It’s no longer kosher to have two integral teams at odds with each other in a time when all eyes are on speed and safety. Collaboration is key, and to get to a place where seamless collaboration happens, it’s important to understand and overcome the challenges faced on both sides.

WHO OWNS APPSEC?

Let’s start with the obvious: Who owns application security? Developers will tell you they’ve gone to great pains to ensure every line of code is as secure as they need it to be. Security teams will tell you they haven’t gone far enough. This clash of opinions stems from a mutual misunderstanding of the other’s function. We commonly refer to this as the DevSec Disconnect. Giving problems a catchy name is great and all, but with teams operating in such a way, how do we go about bridging the gap? We’ll touch a bit on this later, but communication and collaboration built into the development process is key.

Zooming into the misunderstanding on both sides, we can see exactly how it is such a source of frustration. No one team can have full oversight if developers lack the time and technology to close security gaps; while security teams are notoriously understaffed and tend to lack the full development cycle view. 

Lack of visibility and communication

Human error is still the biggest threat to application security, and 90% of cyberattacks are aimed at software. Faced with this status quo, you would think that teams would share knowledge and talk to each other. But that’s not necessarily happening across the board. DevSecOps technologies have yet to reach proper market adoption levels and organisational inertia is one of the main obstacles to DecSecOps implementation. 

A lack of visibility also challenges the role of analytics and measurement. Security tools generate reports and tasks to get software up to scratch, but with a cohesion gap, how does anyone make sense of the data, and who is accountable for it?

People, processes, and priorities

Culturally, some ingrained attitudes and behaviours challenge the success of any DevSecOps efforts. Security teams think developers don’t care about security, developers think security people are naysayers and give inconsistent advice. Each party has their manager to please, their own set of metrics that they’re measured against, and a priority list as long as their arms already.

Both teams operate at different levels, follow different processes and crucially, use different tools. Developers can’t get around the security tool complexity, and security teams have no control over the CI pipeline to best implement findings.

We also see different meanings and weighting of security risks between developers and security teams. What’s an absolute necessity to one might be seen as a nice-to-have to the other. This leads to a mismatch in the prioritisation of risks and disagreements about where to focus efforts. 

There is a silver lining and a caution. GitHub’s 2021 Global DevSecOps Survey found some good news and some not so good news. 

  • Good news: 70% of security team members say security has shifted left 
  • So-so news: over three-quarters of the security team continue to think devs find too few bugs too late in the process

The Developer/Security relationship has come on leaps and bounds, but there’s still a long way to go.

DevSecOps automation: Bridging the DevSec disconnect

Shifting security left has been at the forefront of every software company’s plans for the last few years. There is an industry-wide appreciation for the need to get security involved at all levels of the SDLC, with no exceptions. 

But goodwill only gets DevSecOps so far. According to a 2019 DORA report, only 31% of the top organisations doing DevSecOps properly have been able to automate security within their environment, and 70% of organisations lack adequate working knowledge of DevSecOps practices. Without investing time to instil organisational-level understanding and best practices, and money into the tools to make light work of it, DevSecOps maturity levels will stagnate. 

DevSecOps is a culture

Imagine a world where high-performing teams spot vulnerabilities early and eliminate false positives. A universe in which developers become security-aware, and security teams reduce real risks early in the life cycle. When collaboration starts, development and security teams begin to confidently ship safe software faster.

Solutions start with collaboration

DevSecOps automation and orchestration platforms like Uleska can help to improve collaboration between developer and security teams by streamlining testing and correlating results. They can fundamentally change the way development and security teams work and improve the organisation’s DevSecOps maturity. 

To learn more about the challenges facing DevSecOps today, check out our in-depth guide, and to discover more about overcoming these collaboration challenges by automating DevSecOps, let’s talk about Uleska.

overcome the challenge of devsecops

Subscribe to the Uleska blog

You may unsubscribe at any time using the unsubscribe link in the newsletter.

Popular Articles
Visit the Blog
DevSecOps

DevSecOps tool examples that will alleviate your workload

Nowhere is this more apparent than in DevSecOps where developers and releases outnumber security experts by thousands to one. It’s simply not...

DevSecOps

What is CI/CD? A Complete Guide to CI/CD

Software development cycles have changed immensely in the last ten years. New practices and design philosophies are being tried every day. One of...

Tools

How to source the right tools to scale an AppSec programme

Everyone’s development is different, it stands to reason everyone’s perfect security toolkit will also be different. But finding the right tools to...

Security

What is Penetration Testing (Pen Testing)?

Penetration testing (also known as pen testing) is the process of checking if your infrastructure and applications are robust enough to protect...

Tools

What is Dynamic Application Security Testing (DAST)?

DAST, meaning Dynamic Application Security Testing, is a form of black-box security testing. It simulates external attacks on a live application,...

DevSecOps

Ultimate Guide to DevSecOps

What is DevSecOps?  DevSecOps meaning (Development, Security, and Operations) primarily aims to automate security in each part of the software...

Company News, Security

Uleska and Log4Shell

Summary TL;DR: If you are a cloud customer of Uleska, you are not vulnerable to log4shell. If you are an on-premise customer of Uleska and are using...

Tools

The Top Application Security Tools in 2021

In modern businesses, applications have assumed a pivotal role. And while applications help with operational processes, the majority of cyber-attacks...

Tools

The Ultimate Guide to Application Security Tools

With the emergence of new software security threats, businesses need robust, flexible and affordable methods to ensure their applications are...

Tools

Introducing the DevSecOps Toolkit: A guide to scaling an AppSec programme

Imagine you’ve been asked to build a house from scratch. You don’t have any tools. You don’t have any experience. In fact, all you have is an empty...

Tools

What is Static Application Security Testing (SAST) and how does it work?

What is SAST? Static Application Security Testing (SAST), or static analysis, is a method of testing and analysing source code. This method allows...

Tools, Featured

Choosing the Best AppSec Tools: Advice from Experienced Engineers

In our latest webinar Gary Robinson and Martin Hewitt from Uleska gave us a fascinating and comprehensive look into how experienced security teams...

Managing Risk

How to Use Risk Based Security Testing [With Video]

Last week we discussed how using risk-based decisions can help speed up pipelines. You can watch the webinar on demand and read a summary of the...

DevSecOps

Can DevSecOps Tools Open Security Testing To Everyone?

At Uleska, we focus on moving security testing away from experts running manual tests and move it to automating security checks into existing...

Company News

Start your DevSecOps journey with the Uleska free plan

Companies are developing and shipping software faster than ever before. The very nature of DevOps means that developers can work in an always-on...