The Myth of Mutual Exclusivity: Making the DevOps Process More Agile Without Compromising Security
Source – securityintelligence.com
The marketplace is demanding agility, but many enterprises perceive the need for agility as an ongoing security risk. If applications are constantly evolving, they assume, the process will constantly open up new avenues for attackers to exploit. This worry has given rise to a widespread misconception that security or agility is a binary choice.
But a growing number of organizations are challenging this stereotype and actively working to integrate security into the DevOps process. These proactive players in the agility game are acting on two basic principles and responding to two basic realities. One is that effective security is built in, not bolted on — meaning that even if agility were not an issue, security needs to be an integral part of the development process. The second principle is that attackers are agile, which means that security must also be agile.
Integrating Security Into the DevOps Process
A recent DigiCert survey titled “Making Security Agile” queried 300 enterprise leaders to determine “whether organizations are breaking down silos and inviting security to join the DevOps movement.” The survey revealed that these leaders put strong and nearly equal emphasis on increasing information security (90 percent), IT agility (88 percent) and development agility (87 percent).
Clearly, the respondents believe that they don’t need to choose between security and agility. Instead, they can integrate them and achieve both.
One significant challenge the survey found is that working faster often results in increased risk, while maximizing security sometimes means slowing down operations. The report suggested “changing how security works within the organization.”
Nearly half of respondents (49 percent) reported that they had already integrated security into the DevOps process, while another 49 percent said that they were working on completing that integration. Only 2 percent expressed no interest in doing so — a number so small that it may merely represent people who misread the question.
The greatest practical challenge, according to the survey, is that integration takes longer than most organizations anticipated: one to two years, as opposed to the typical expectation that it would take seven to 11 months.
Agility and Active Security
The survey specifically advised organizations to establish a social leader “to drive cultural change.” It also recommended limiting access, using encryption within an automated public key infrastructure (PKI), and investing in automated certificate management, patch management, vulnerability scanning and stack code analysis. These specific recommendations encapsulate the whole range of practical requirements for overcoming the security or agility conundrum.
But what stands out in the broader picture is how natural this integration is. When security is integrated into development, the result is an inherently robust architecture in which basic protective measures have been built in from the outset.
This security architecture is flexible when it comes to handling new threats because it is built with strong components that already achieve the basics and can be reconfigured as the threat environment changes. Agility thus includes an agile response to threats, making security more effective.
Rather than a false choice of security or agility, it turns out that agility is the right choice for enhanced security.