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

April 27, 2017

In a movement that has gained momentum as quickly as DevOps has, it's always good to stop from time to time and evaluate where we are, where we have come from, and where we are going. We asked four industry experts some questions about the progress of ALM and DevOps ...

April 26, 2017

It's easy to ignore downtime. But ignoring downtime is a surefire way to upset your customers and your colleagues. More and more, teams need to think about shipping stellar experiences. Proper incident response is a great place to start ...

April 24, 2017

The expectation of regular software updates – it's what developers are tasked with, and what users expect and demand. Increased functionality, better performance, and fewer bugs – often in a week or less. Automation of critical processes such as QA can help meet the gargantuan task of constant updates, but it can also send your software into a death spiral of user abandonment unless deployed correctly ...

April 20, 2017

One could argue that testing is the most important phase of an IT project. It's also time-consuming and expensive. It's essential to strike a balance between an IT testing program that ensures a quality product and the cost-to-value ratio of your project. But when you're dealing with replatforming projects, how much testing is enough testing? ...

April 18, 2017

Whether through formal methods such as classroom or virtual training, job shadowing, and mentoring; or through informal methods such as team discussions or presentations, teaching needs to be a frequent element of team integration. It is a given that IT and business teams have difficulty understanding each other without a common taxonomy. Even teams within IT often fail to understand each other ...

April 17, 2017

Although DBAs fortunately have the rare ability to bridge the gap between development and operations, they have been detrimentally overlooked in many companies that deploy DevOps practices. A DBA's ability to interrogate code and construct a resilient, well–performing database environment uniquely defines the capabilities needed for DevOps – leaving me perplexed about why DBAs were not one of the first operations team members asked to join the DevOps movement ...

April 12, 2017

DEVOPSdigest asked experts across the industry — including analysts, consultants and vendors — for their opinions on the best way for a development or DevOps team to become more Agile. Part 5, the final installment in this series, provides tips on empowering people ...

April 10, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 4 covers DevOps technologies ...

April 07, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 3 provides some tips for getting started and gaining feedback ...

April 05, 2017

DEVOPSdigest asked experts across the industry for their opinions on the best way for a development or DevOps team to become more Agile. Part 2 covers processes including automation, continuous delivery and testing ..

Share this