DevSecOps: Eat Carrots, Not Cupcakes
You Are What You Eat
March 21, 2017

Derek Weeks
Sonatype

When it comes to food, we all know what's considered "good" and what's "bad".

For fried, battered, buttery or creamy: the category of cupcakes and such ... just say no. When fresh, grilled, steamed or baked: of course, you should eat your veggies and other fine foods ... bon appetite.

We can all understand this simple rule when eating. But for many, when it comes to software development, simple rules and advice from nutritional labels aren't always there for us. Simple rules like: use "good" open source components, not "bad" ones (i.e., vulnerable, outdated, risky licenses) when building and deploying your next app.

Evidence of Gluttony

To meet the need for speed, virtually all modern development organizations are using open source and third party components to assemble applications rather than build every function from scratch. According to the 2016 State of the Software Supply Chain Report, conducted by Sonatype, the average development organization feasts on over 229,000 open source Java components each year, but we're seeing similar consumption practices in the JavaScript, Python, Ruby, and .NET development realms. While the upside of this gluttony is improved productivity, there is a downside to consuming components without the proper insight into their quality.

Beyond the consumption of open source and third-party software components in development, the same guidance holds true for containers used by DevOps teams. Today, over 100,000 free apps are available on Docker Hub, and consumption of those applications into DevOps tool chains and infrastructure often goes unchecked.

The Downside of Efficiency

While sourcing components and containers can accelerate development efforts, many organizations do not apply sufficient scrutiny to assessing their quality or security. The 2016 Software Supply Chain report also indicates that 1 in 15 of the components used in applications contain at least one known security vulnerability. What this means is that not all components and containers are created equal. It also means that blind consumption practices can have both immediate and long-term consequences for the organization consuming the open source software components or containerized applications.

According to the 2017 DevSecOps Community Survey, conducted by Sonatype, 58% of organizations looking to improve the quality of components used in their development practices have implemented an open source governance practice. This is up only slightly from the 2014 survey which showed 57% of organizations with open source policies in place.

For those without a policy, there are no rules in place when it comes to "good" vs. "bad" consumption practices. Having policies in place can help to improve the quality of applications being produced, reduce vulnerabilities to attack, and eliminate use of components with risky license types.

Breaking Bad

At the time, over 2,700 survey participants of the 2014 survey indicated that more than 1 in 10 organizations (14%) had experienced or suspected a breach in their applications related to an open source software component. Because, that survey took place in the same month that the notorious OpenSSL software component (a.k.a"Heartbleed") vulnerability was announced, I felt like it might have inflated the number of breach related responses. To my surprise, the 2017 survey shows that 20% of organizations (1 in 5) had or suspected a breach related to open source software components in their applications.

In the past three years, as the rate of confirmed or suspected breaches related to vulnerable open source components increased by 50%, the number of organizations having rules in place to govern the use of secure components remained the same.

Across the DevOps community, we are seeing much more attention being paid to security concerns and more organizations finding news ways to automate practices early in the SDLC. Automating the evaluation of open source and third party components against rules designated in open source governance policies is one the approaches being adopted. While not the only answer to DevSecOps requirements, having an automated policy in place to enforce governance and guide remediation can pay off handsomely if it also helps prevent a breach.

When it comes to carrots and cupcakes, the right choices can offer great short- and long-term benefits. In the realm of components and containers, making "good" choices will also benefit your DevSecOps practice.

Read about more findings from the 2017 DevSecOps Community Survey

Derek Weeks is VP and DevOps Advocate at Sonatype.

The Latest

July 20, 2017

Financial services organizations are high value targets for cyber criminals all over the world. Because of this, it is imperative that the keys and certificates used by financial service DevOps teams are properly protected. If not, bad actors can easily exploit cryptographic assets and wreak havoc on sensitive corporate data, all while remaining undetected ...

July 18, 2017

In the last year, businesses around the globe significantly increased their use of open source and although they readily acknowledge growing concerns about open source-related security and operational risks, the effective management of open source is not keeping pace with the increase in use ...

July 17, 2017

A Forrester survey confirmed what high-performance organizations have already said – DevOps is here to stay. Diving into the details, however, the study also shows that the DevOps journey may be in for a rude awakening. Companies in all industries are embracing DevOps for superior productivity, but many organizations struggle to overcome barriers that prevent them from translating these programs into improved business results ...

July 14, 2017

Despite the pervasive belief that security and development teams have conflicting priorities, initiatives such as creating DevOps environments and focusing on product innovation have the two teams aligned toward a common goal of creating secure software, according to a new study from Veracode ...

July 12, 2017

Gartner, Inc. highlighted the top technologies for information security and their implications for security organizations in 2017 ...

July 10, 2017

DevOps practices lead to higher IT performance, according to the 2017 State of DevOps report This higher performance delivers improved business outcomes, as measured by productivity, profitability, and market share ...

June 28, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 5, the final installment, covers how Agile improves product quality and the customer experience ...

June 26, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 4 covers how Agile impacts team productivity ...

June 23, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 3 covers how Agile enables you to grow and adapt to change ...

June 21, 2017

Why Agile? DEVOPSdigest asked the experts for their opinions on what are the most important advantages of being Agile. Part 2 is all about speed ...

Share this