Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Application Security

6/26/2019
04:55 PM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Developers and Security Teams Under Pressure to Collaborate

The challenges and benefits to getting two traditionally adversarial groups on the same page.

AWS re:Inforce – BOSTON – The path to secure development involves closer collaboration between the security and developer teams, a duo with a traditionally rocky relationship.

Application security, DevOps, and DevSecOps were all terms frequently heard this week at Amazon Web Services' re:Inforce, its first-ever security conference. AWS has been very developer focused, pointed out Chris Eng, chief research officer at Veracode. It's positive to see a focus on security's role in development, which he said has been a growing issue for four to five years.

Looking back 10- to 15 years, there has been a clear way security and development worked: engineers built code and handed it over to security when it was ready. By the time security came back with fixes, developers would be in a time crunch; rarely was there time to address them all. "There was a very rigorous, very structured set of handoffs," said Brian Riley, Liberty Mutual's senior director of global cyber risk management. "We're in a different world now."

Indeed, the transition to cloud broke down those choke points. DevOps evolved along with the cloud, driving the speed of new software releases and requiring security to review applications more frequently. This caused "a huge adjustment" for those who did application security a long time ago, Eng explained, because it shifted responsibility for security teams who assessed code.

"There's a tradeoff between depth and speed," he continued. "If I have a shorter amount of time to review something, there's a greater chance I'm going to miss something."

Developers must understand the types of things security will be looking for, he continued. Security, which has a reputation for holding progress back with constant fixes, has to meet the developer teams where they are and try not to disrupt what they're already doing. Security practitioners are traditionally uncomfortable with accepting risk. As the process of software development continues to accelerate, they will have to learn how to let some things go.

It was the move to cloud that prompted Riley, a former developer to collaborate with the dev team. "It challenged me, as a longtime security professional, to realize I had to get a lot closer to development," he explained. "I needed to be where the developers were." It wasn't – and still isn't – where security teams operate. Riley cited "drawn-out battles" between security and dev teams: security often says "that's not controlled;" devs respond with "this could be better."

"Historically, it's adversarial," Eng said of the longtime relationship between developers and security practitioners. "It's had to move from adversarial to more cooperative."

Security Champions: Bridging the Gap

Eng pointed to a growing pattern of "security champions," or developers with an aptitude in security who become an extension of the infosec team. These individuals are trained to conduct code reviews themselves as opposed to sending it off to security. The idea is to shift responsibility and lessen the workload for security teams, which are also focused on tasks outside secure development and often don't have the number of employees they need.

Of course, the appointment of security champions doesn't always sit well with security teams, he added. They need to hand off responsibility for code reviews to someone else; however, if something goes wrong, they're still to blame. Many are afraid of shifting this responsibility.

"There's a need to be more comfortable with losing a little bit of control," Eng said. If a dev team can handle 80% of security work, he added, it's helpful to the development process.

Overall, it also helps when developers have a security background, as it improves understanding between the two teams and, consequently, their working relationship. It's often not required for developers to have a security background, but it is a plus if they're interested in the space. Veracode does quarterly boot camps and exercises to train developers in cybersecurity.

This evolving collaboration signifies growing the decentralization of security, Eng said. Over time, he predicts, the back-and-forth between security and development will be erased.

Related Content:

 

Black Hat USA returns to Las Vegas with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
<<   <   Page 2 / 2
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
6/28/2019 | 6:27:19 PM
10 years ago
Looking back 10- to 15 years, there has been a clear way security and development worked: engineers built code and handed it over to security when it was ready. By the time security came back with fixes, developers would be in a time crunch; rarely was there time to address them all. This is true. We were not paying that much attention to security at the beginning on the past.
tdsan
50%
50%
tdsan,
User Rank: Ninja
6/27/2019 | 3:18:50 PM
SecDev - wave of the future
Overall, it also helps when developers have a security background, as it improves understanding between the two teams and, consequently, their working relationship. It's often not required for developers to have a security background, but it is a plus if they're interested in the space. Veracoda does quarterly boot camps and exercises to train developers in cybersecurity.

This section identified in your article is the best thing any company could do. I loved the article and it brought insignt into some of the shortcomings in the private and public sector development shops. We will be incorporating "SecDev" or "Security Development" teams into our environment as well and thank you for this valuable insight.

Excellent.

Todd
<<   <   Page 2 / 2
Microsoft Patches Wormable RCE Vulns in Remote Desktop Services
Kelly Sheridan, Staff Editor, Dark Reading,  8/13/2019
The Mainframe Is Seeing a Resurgence. Is Security Keeping Pace?
Ray Overby, Co-Founder & President at Key Resources, Inc.,  8/15/2019
GitHub Named in Capital One Breach Lawsuit
Dark Reading Staff 8/14/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-15237
PUBLISHED: 2019-08-20
Roundcube Webmail through 1.3.9 mishandles Punycode xn-- domain names, leading to homograph attacks.
CVE-2019-15228
PUBLISHED: 2019-08-20
FUEL CMS 1.4.4 has XSS in the Create Blocks section of the Admin console. This could lead to cookie stealing and other malicious actions. This vulnerability can be exploited with an authenticated account but can also impact unauthenticated visitors.
CVE-2019-15229
PUBLISHED: 2019-08-20
FUEL CMS 1.4.4 has CSRF in the blocks/create/ Create Blocks section of the Admin console. This could lead to an attacker tricking the administrator into executing arbitrary code via a specially crafted HTML page.
CVE-2019-15231
PUBLISHED: 2019-08-20
Webmin 1.890, in a default installation, contains a backdoor that allows an unauthenticated attacker to remotely execute commands. This is different from CVE-2019-15107. NOTE: as of 2019-08-19, the vendor reports that &quot;at some point&quot; malicious code was inserted into their build infrastruct...
CVE-2019-15232
PUBLISHED: 2019-08-20
Live555 before 2019.08.16 has a Use-After-Free because GenericMediaServer::createNewClientSessionWithId can generate the same client session ID in succession, which is mishandled by the MPEG1or2 and Matroska file demultiplexors.