Vulnerabilities / Threats

10:00 AM
Zeus Kerravala
Zeus Kerravala
Connect Directly
E-Mail vvv

DevOps & Security: Butting Heads for Years but Integration is Happening

A combination of culture change, automation, tools and processes can bring security into the modern world where it can be as agile as other parts of IT.

DevOps has been a hot topic now for the better part of a half-decade - and IT security has been on fire for longer than that. However, the two disciplines have been going down parallel paths for years, never to meet, because infrastructure teams and application development groups tend to work in their own little silos and claim ignorance as to what they others group does.

Why? There appears to be no good reason other than, "that’s the way it’s always been." I believe there is some element of CYA in here, where if something doesn’t work, it’s easy to point a finger to a group you have nothing to do with. But by in large it’s just a legacy IT mindset. 

This sentiment seems to be changing and IT leaders are actually attempting to bring infrastructure and applications together. I attended a recent conference where Mike Giresi, the CIO of Royal Caribbean Cruise, discussed this issue and noted that "the fact [that] the infrastructure and application teams don’t work together is completely insane." He said there was a mandate inside Royal Caribbean that the DevOps and infrastructure teams would be goaled on the same thing – the success of applications. The common goal was in place to ensure collaboration and avoid finger-pointing. 

I get why DevOps teams may be hesitant to work with infrastructure groups. The primary focus of DevOps is speed and continuous innovation. Infrastructure, particularly security, thrives on keeping the lights on so "if it ain’t broke don’t fix it," which is in stark contrast to the agile mindset of DevOps. 

Recently, DigiCert, a vendor of encryption solutions for enterprise and Internet of Things (IoT) security, ran their "2017 Inviting Security into DevOps Survey" to find the status of enterprises integrating security with DevOps. 

Before I get into the survey results, le me get on my soapbox regarding the need to bring infrastructure, particularly security, and DevOps together. Digital transformation requires businesses to move with speed. Speed requires IT agility. IT agility requires app development and infrastructure to be agile and, in most organizations, security is anything but agile.  In fact, security is often left to the very end so companies can build a new app and then have to wait months until the security teams have made their changes and are ready. A better approach is to build security into the application development process.

The survey shows that a surprising 49% of organizations have completed the process of integrating security and DevOps, and another 49% are in the process of doing so. I suspect the group that says they were "finished" simply does not know what they do not know, so there’s likely more work to be done that they aren’t aware of it.  From personal interviews, I think that the number of companies that have completed the process is about 25% or less. 

Whatever the real number is, the survey shows that the results have been positive as respondents are 22% more likely to report they are doing well with information security, 21% more likely to report they are meeting application delivery deadlines, and 21% more likely to lower application risk.

The study also looks at the ramifications of not changing, and these results really hit home.  Respondents to the survey were concerned that failure to integrate security and DevOps would add to the following already existing problem:

  • 78% cite increased costs
  • 73% cite slower application delivery
  • 71% cite increased security risk.

I find it interesting that more respondents are concerned with cost and speed than increased security risks but that’s likely a function of how critical agile development has become to organizations. Another way to think about this result is that security doesn’t matter if costs skyrocket or application development is too slow, as the organization will fall behind its competitors. 

To DigiCert’s credit, the company didn’t just run the survey and show the results.  The company also provided some recommendations and best practices on how to bring these formerly independent worlds together:

  • Appoint a social leader. Putting a leader in place to drive cultural change across the company is extremely important to success. This needs to be a top-down initiative where all parties understand the importance and the consequences of failure. Personally, I like the approach Royal Caribbean took of shifting to an outcome-based approach as it gives everyone a common lighthouse to row to.
  • Bring security to the table.  A security lead must be present on all DevOps initiatives - and be involved from the outset of projects. DigiCert suggests limiting access, signing and encrypting everything in the network using automated PKI. This makes sense given DigiCert’s solution but baking security into the development process ensures success at every step.
  • Invest in automation. This is music to my ears as I’ve long been a proponent of automating everything possible.  People work too slowly to keep up with digital trends, and automating things like patching, vulnerability scanning and certificate management is the only way to keep up with the speed of business today.
  • Integrate and standardize. Standardization and repeatability is the key to on-going success. Doing things ad hoc is a sure way to lead to failure.

DevOps and security have been butting heads for years but they don’t have to. A combination of culture change, automation, tools, and processes can bring security into the modern world where it can be as agile as other parts of IT. The DigiCert survey shows the importance of going down this path and the repercussions of not doing so. There’s never been a better time to bring security and DevOps together, so let's start now. 

Black Hat USA returns to the fabulous Mandalay Bay in Las Vegas, Nevada, July 22-27, 2017. Click for information on the conference schedule and to register.


Related Content:


Zeus Kerravala provides a mix of tactical advice and long term strategic advice to help his clients in the current business climate. Kerravala provides research and advice to the following constituents: end user IT and network managers, vendors of IT hardware, software and ... View Full Bio
Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Strategist
7/24/2017 | 4:10:53 PM
Re: 2 responses
My initial post was meant to highlight the problem and not use the post to self-promote. I hope that was clear. That said, the author's comment is exactly the line that my team and I follow. While it is the most appropriate course of action, when dealing with large organizations, it's pretty tough to get the attention of a CIO responsible for so much.

Stil, if you are trying to shake the tree, the top down approach is the best path to follow.
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
7/22/2017 | 3:05:24 PM
Re: 2 responses
@zkerravala: Moreover, in addition from these initiatives having to come from the top down, they have to have unity from the top down as well -- demonstrating the CIO and other C-suiters/top execs publicly "shaking hands" and agreeing to work together on them. This will help unite goals and methodologies while increasing collaboration.
User Rank: Author
7/21/2017 | 10:22:33 AM
Re: 2 responses
Thanks for your feedback.  I agree with the "good luck" statement as I often feel that infrastructure and DevOps do not want to work together.  This is why this needs to be driven top down from the CIO and the goals of the groups need to be aligned
User Rank: Apprentice
7/21/2017 | 8:07:27 AM
Re: 2 responses
I was able to find good advice from your blog posts. 
Joe Stanganelli
Joe Stanganelli,
User Rank: Ninja
7/20/2017 | 4:02:29 PM
2 responses
Considering the friction and finger-pointing that already exists in organizations among DevOps itself (i.e., between front-end and back-end developers), when you suggest getting security involved from the outset, I say two things:

(1) "Hear, hear!"


(2) "Good luck."
User Rank: Apprentice
7/20/2017 | 12:15:00 PM
Re: security adoption
Well said. 
User Rank: Strategist
7/20/2017 | 11:59:08 AM
security adoption
This post accurately portrays the friction that has existed between two critical company teams. Top line stakeholders who are responsible for compliance, brand integrity and sometimes revenue have a clear interest in seeing the two work together. Application security has been a daunting task as it typically requires the diverting of precious resources to integrate solutions that actually work but do not affect user experience. Solid solutions do exist, but only a few deliver on the promise of easy deployment without integration.
6 Security Trends for 2018/2019
Curtis Franklin Jr., Senior Editor at Dark Reading,  10/15/2018
6 Reasons Why Employees Violate Security Policies
Ericka Chickowski, Contributing Writer, Dark Reading,  10/16/2018
Getting Up to Speed with "Always-On SSL"
Tim Callan, Senior Fellow, Comodo CA,  10/18/2018
Register for Dark Reading Newsletters
White Papers
Latest Comment: Too funny!
Current Issue
Flash Poll
The Risk Management Struggle
The Risk Management Struggle
The majority of organizations are struggling to implement a risk-based approach to security even though risk reduction has become the primary metric for measuring the effectiveness of enterprise security strategies. Read the report and get more details today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2018-10-16
Qemu emulator <= 3.0.0 built with the NE2000 NIC emulation support is vulnerable to an integer overflow, which could lead to buffer overflow issue. It could occur when receiving packets over the network. A user inside guest could use this flaw to crash the Qemu process resulting in DoS.
PUBLISHED: 2018-10-16
The Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
PUBLISHED: 2018-10-16
Z-BlogPHP (Zero) has a stored XSS Vulnerability in zb_system/function/c_system_admin.php via the Content-Type header during the uploading of image attachments.
PUBLISHED: 2018-10-16
Advanced HRM 1.6 allows Remote Code Execution via PHP code in a .php file to the user/update-user-avatar URI, which can be accessed through an "Update Profile" "Change Picture" (aka user/edit-profile) action.
PUBLISHED: 2018-10-16
XSS exists in the MetInfo 6.1.2 admin/index.php page via the anyid parameter.