Mobile SDKs (software developments kits); love them or hate them, they're here to stay. They provide our apps with all sorts of functionality that would be incredibly time consuming to build, and they give us another means to monetize our apps. While it would be difficult to argue that SDKs aren’t useful, it’s also hard for developers to get a good idea of the amount of resources used by each SDK once the app is in production ...
When was the last time you worked closely with your IT security team? Your CISO may provide you (and every other employee) with guidelines for avoiding ransomware and other types of malware, but that may be the extent of your interactions with the security team. Your top priority is to improve application development agility, but you may run into roadblocks put up by a security team that (mistakenly) believes speed is the enemy of effective cybersecurity. A new survey finds a majority of enterprises are working to overcome those roadblocks by integrating security into their existing DevOps methodology.
That is the key finding of DigiCert's 2017 Inviting Security into DevOps survey. DigiCert polled 300 senior management professionals within IT, DevOps and Security teams with small, medium and large organizations that have already implemented a DevOps posture.
98 percent of respondents say they have made integrating their security teams into their existing DevOps methodology a priority in order to accomplish two primary goals: increase business agility, and improve information security. The market is at a tipping point. About half (49 percent) are working on doing so and half (49 percent) say they have completed the process.
"The faster that we implement something, the more likely it is to have vulnerability issues," said one respondent who is an IT manager for a large central US manufacturing firm. “That's why for us security is so important; it saves us time and money in the long run."
Underscoring the security risk, 59 percent of the respondents say they sometimes or often have rogue certificates (for example, certificates that DevOps purchased, but neglected to tell anyone in Security about, causing problems when they expire).
Integrating security with DevOps is not easy and presents several issues to overcome. To make matters more complex, these challenges can change once the integration process begins.
The top three obstacles in the minds of respondents who are just beginning their efforts are that:
1. The organization structure prohibits integration
2. They lack a champion for the transition
3. The security team doesn't really work well in a team environment
However, that list changes once an enterprise nears completion:
1. Takes too much time
2. Security team resists the change
3. The relationship skills required to integrate the two teams
Note the top challenge cited after integrating was that the transition took too long. Technical teams underestimate the challenge of integrating security into DevOps, thinking the integration will take less than a year (seven to 11 months), whereas those who claim to have completed the process say it took roughly twice as long – on average one to two years.
The latter group has another list, and it's one that should encourage companies that are still in the early stages: how their efforts have improved both security and agility. They are:
■ 22 percent more likely to report they are doing well with information security
■ 21 percent more likely to report doing well meeting app delivery deadlines
■ 21 percent more likely to report doing well at lowering app risk
The survey's findings also reveal four key steps any organization can take to achieve the optimum balance of development agility and information security:
1. Appoint a Social Leader
Identify one person who will drive cultural change by clearly defining IT, security, DevOps roles and integrating the disparate teams.
2. Bring Security to the Table
Place a security lead on all DevOps teams and involve them from the beginning. Limit access, and implement automated PKI to require signing and encrypting everything within the network.
3. Invest in Automation
Automate baseline security practices within DevOps workflow, including: certificate management, patching, vulnerability scanning, stack code analysis.
4. Integrate and Standardize
Implement controls on certificate management processes and integrate with server configuration and orchestration platforms to enable automated security behind the scenes.
If there's one key takeaway of the 2017 Inviting Security into DevOps survey findings, it's this: Integrating security into DevOps is well worth the effort.
“We've found that agility was actually a byproduct of putting security upfront," said a senior project manager at a large metals manufacturer in the northeast. “If you really want to be agile, you don't want to do things twice."