Flagship Projects: Dependency-Check
summary
OWASP Dependency-Check claims to find known vulnerable components by matching dependencies against the NVD and OSS Index, using evidence-based identification from manifests and binaries and offering suppression and hints files to manage false positives and false negatives. It prefers build-plugin analysis (Maven/Gradle) over CLI/docker, caches NVD data locally to avoid NVD rate limits, reports surprising scale like 1,000,000 CLI downloads and 2.5 million Docker pulls, and is actively maintained.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:35Software Composition Analysis
- 6:52Primary Data Sources
- 10:06Vulnerability Data Source • National Vulnerability Database (NVD) List of Common Vulnerability and Exposures (CVE) • Each CVE entry contains • A description of the vulnerability
- 12:43Library Identification Problems • Development & Security use different identifiers
- 16:18Evidence Based Identification Issues
- 17:31Dealing with False Positives Invalid dependency identification can be resolved using a suppression file
- 18:51Onboarding an Application
- 25:01Use Cases for dependency-check
- 28:01How can you help?
related talks
27mFind and Track the hidden vulnerabilities inside your dependencies
46mSafely through the dependency minefield using OWASP Dependency Track
01h 00mDependency Check Project
20mDetect and track the aliens hiding in your dependencies
34mDependency Track
17mDetect and Track the Vulnerabilities Hiding in Your Dependencies
54mSupply Chain Sec /w Dependency Track
26mKnow Your Dependencies: A Guide to Automating Dependency Assurance
