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

Open Source v. Closed Source: What's More Secure?

0%
100%

In the wake of Shellshock and Heartbleed, has the glow of open-source application security dimmed?

Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
Molly666
50%
50%
Molly666,
User Rank: Apprentice
7/22/2020 | 10:01:33 AM
Re: Devil's Advocate
In general, both options have their strengths, https://utopia.fans/security/whats-the-difference-between-open-source-vs-closed-source/  therefore, it has not been possible to come to a single solution so far, on the other hand, I will personally voice my opinion based on the experience of working with both. I still believe that closed source is more secure. Yes, you have to pay for it, but in general it guarantees a high level of quality and safety.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
10/21/2014 | 11:07:40 AM
Re: Devil's Advocate
Agreed, sometimes when something is implemented that cannot increase security posture you need to go back to the framework and make changes to the baseline. This may be off topic from Open Source vs Closed Source, but DoS is the same way. Its still very prevalent due to the way hardware handles packets. A needed functionality, so changes need to be made to the overall hardware handling. However, I do think that more hands involved in the rearchitecture would be optimal. 
Lucamp
50%
50%
Lucamp,
User Rank: Strategist
10/21/2014 | 5:29:54 AM
Open source
From my persective, open source is more secure and more people work on it that in close code. However, the types of vulnerabilites that open source is exposed is different that in close code. Also the quality of open source projeects is higher that in close code from my experience (Two Big Companies). 
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/20/2014 | 1:46:59 PM
Re: Devil's Advocate
Good point. That also depends of the architecture of the system, you can not make Java any more secure regardless of how many developers you put on it. A new way of thinking and architecture is needed for that.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/20/2014 | 1:44:47 PM
Agree with the video
 

I think video is taking right approach tough, no need to differentiate open source from closed source when it comes to security, both will have vulnerabilities and they requires us to do ongoing monitoring and analysis to catch those vulnerabilities before they heard us.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/20/2014 | 1:42:17 PM
Open source
Open source may reveal more information in its structure but at the same time it may also be an environment that vulnerabilities are found and mitigated early enough since more than one set of eyes are looking at it.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
10/20/2014 | 11:16:26 AM
Devil's Advocate
I agree very much with this ideology of closed versus open source. But to be the devil's advocate, wouldn't the same reason provided "more people being able to see the source code" also provide for a more adept security model. In theory, the more eyes that look at the code the greater the exposure to expanding on that code beneficially. This includes not only security but app development. Linux and Linux derivatives are very much based on this methodology. What reasoning then is it assumed that more exposure to the code will result in a detrimental outcome over a beneficial one?
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Browsers to Enforce Shorter Certificate Life Spans: What Businesses Should Know
Kelly Sheridan, Staff Editor, Dark Reading,  7/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17366
PUBLISHED: 2020-08-05
An issue was discovered in NLnet Labs Routinator 0.1.0 through 0.7.1. It allows remote attackers to bypass intended access restrictions or to cause a denial of service on dependent routing systems by strategically withholding RPKI Route Origin Authorisation ".roa" files or X509 Certificate...
CVE-2020-9036
PUBLISHED: 2020-08-05
Jeedom through 4.0.38 allows XSS.
CVE-2020-15127
PUBLISHED: 2020-08-05
In Contour ( Ingress controller for Kubernetes) before version 1.7.0, a bad actor can shut down all instances of Envoy, essentially killing the entire ingress data plane. GET requests to /shutdown on port 8090 of the Envoy pod initiate Envoy's shutdown procedure. The shutdown procedure includes flip...
CVE-2020-15132
PUBLISHED: 2020-08-05
In Sulu before versions 1.6.35, 2.0.10, and 2.1.1, when the "Forget password" feature on the login screen is used, Sulu asks the user for a username or email address. If the given string is not found, a response with a `400` error code is returned, along with a error message saying that th...
CVE-2020-7298
PUBLISHED: 2020-08-05
Unexpected behavior violation in McAfee Total Protection (MTP) prior to 16.0.R26 allows local users to turn off real time scanning via a specially crafted object making a specific function call.