02511nas a2200253   4500008004100000022001400041245006100055210006100116260004200177300001000219490000600229520182100235653001802056653001402074653001802088653000802106653001202114653001602126653002102142100001602163700001902179700002302198856003602221       2016                        eng d  a1927-032100aLicense Compliance in Open Source Cybersecurity Projects0 aLicense Compliance in Open Source Cybersecurity Projects  aOttawabTalent First Networkc02/2016  a28-350 v63 aDevelopers of cybersecurity software often include and rely upon open source software packages in their commercial software products. Before open source code is absorbed into a proprietary product, developers must check the package license to see if the project is permissively licensed, thereby allowing for commercial-friendly inheritance and redistribution. However, there is a risk that the open source package license could be inaccurate due to being silently contaminated with restrictively licensed open source code that may prohibit the sale or confidentiality of commercial derivative work. Contamination of commercial products could lead to expensive remediation costs, damage to the company's reputation, and costly legal fees. In this article, we report on our preliminary analysis of more than 200 open source cybersecurity projects to identify the most frequently used license types and languages and to look for evidence of permissively licensed open source projects that are likely contaminated by restrictive licensed material (i.e., containing commercial-unfriendly code). Our analysis identified restrictive license contamination cases occurring in permissively licensed open source projects. Furthermore, we found a high proportion of code that lacked copyright attribution. We expect that the results of this study will: i) provide managers and developers with an understanding of how contamination can occur, ii) provide open source communities with an understanding on how they can better protect their intellectual property by including licenses and copyright information in their code, and ii) provide entrepreneurs with an understanding of the open source cybersecurity domain in terms of licensing and contamination and how they affect decisions about cybersecurity software architectures.10acontamination10acopyright10acybersecurity10aGPL10alicense10aopen source10athird-party code1 aShah, Ahmed1 aSelman, Selman1 aAbualhaol, Ibrahim  uhttp://timreview.ca/article/96600496nas a2200193   4500008004100000022001400041245003700055210003400092260004200126300001000168490000600178653001100184653000800195653001300203653001600216653001900232100001500251856003600266       2013                        eng d  a1927-032100aQ&A. Is Open Source Sustainable?0 aQA Is Open Source Sustainable  aOttawabTalent First Networkc01/2013  a46-490 v310aApache10aGPL10alicenses10aopen source10asustainability1 aAsay, Matt  uhttp://timreview.ca/article/650