We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Building the FOSS security commons

Formal Metadata

Title
Building the FOSS security commons
Subtitle
Why Is There No Free and Open Software Vulnerability Database?
Title of Series
Number of Parts
45
Author
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Something is not right: databases of known FOSS software vulnerabilities are mostly proprietary and privately maintained. Why is there no free and open data solution alternative? After all this is all about FOSS code. Security data is too important to not be free. "Using Components with Known Vulnerabilities" is one of the OWASP Top 10 Most Critical Web Application Security Risks. Identifying such vulnerable components is currently hindered by data structures and tools that are (1) designed primarily for proprietary software components and (2) incomplete and too dependent on voluntary submissions to the National Vulnerability Database sponsored by the US government. With the explosion of FOSS usage we need a new approach to efficiently catalog and identify FOSS security vulnerabilities based on open data and FOSS tools. Find how about the FOSS tools we have built to aggregate, relate together and curate software component vulnerability data from multiple sources and automate the search for FOSS component security vulnerabilities. Help us build the security commons and improve the security of software applications with open tools and data for everyone.