@article {ford2007open, title = {Open vs. closed: which source is more secure?}, journal = {Queue}, volume = {5}, number = {1}, year = {2007}, pages = {32{\textendash}38}, publisher = {ACM}, abstract = {There is no better way to start an argument among a group of developers than proclaiming Operating System A to be {\textquotedblleft}more secure{\textquotedblright} than Operating System B. I know this from first-hand experience, as previous papers I have published on this topic have led to reams of heated e-mails directed at me{\textemdash}including some that were, quite literally, physically threatening. Despite the heat (not light!) generated from attempting to investigate the relative security of different software projects, investigate we must. Understanding why products are (and are not) secure is a critical stepping stone toward building better software. Before wading into these dangerous waters, we should clarify the question. All too often when comparing open and closed source approaches, the question is unconsciously interpreted as Windows versus Linux. While that{\textquoteright}s a fantastic question to knock around, doing so is a very narrow way of looking at the world, as it ignores many other projects in both the open and closed source worlds. Although it{\textquoteright}s foolish to ignore the data points the Windows/Linux world provides, they are simply examples of the process. So, let us first strip away the misconception that the question is about these particular platforms and recognize its real breadth. With this in mind, our answer requires three crucial definitions in order to have meaning: {\textquotedblleft}What is open source?{\textquotedblright}; {\textquotedblleft}What is closed source?{\textquotedblright}; and, surprisingly, {\textquotedblleft}What is security?{\textquotedblright} The first two we can deal with quickly; the third is a lot subtler, however, so we shall tackle it first.}, url = {http://queue.acm.org/detail.cfm?id=1217267}, attachments = {https://flosshub.org/sites/flosshub.org/files/p32-ford.pdf}, author = {Ford, Richard} }