JFrog Xray VS OWASP Dependency-Track

I was very thankful for JFrog Xray these past few days. It spotted some embedded cases that wouldn't have shown in a simple dependency graph. Source: over 2 years ago

Services that were vulnerable were pretty easily identified with xray. We're really noisy about keeping 3rd party deps up-to-date, so we were able to take full advantage of log4j2.formatMsgNoLookups for like 90% of our services. All of the services involved had config management in place, so it took less than an hour once we had all the service owners in-the-loop to get the quick-fix rolled out everywhere. Bunch... Source: over 2 years ago

I've become interested in SBOM recently, and found there were great tools like https://dependencytrack.org/ for CycloneDX SBOMs, but all I have is SPDX SBOMs generated by GitHub. I decided to have a go at writing my own dependency track esque tool aiming to integrate with the APIs GitHub provides. It's pretty limited in functionality so far, but can give a high level summary of the types of licenses your... - Source: Hacker News / 6 days ago

To detect these types of vulnerabilities, we should first and foremost know our dependencies and versions, and which of them have vulnerabilities. The OWASP Top 10 2021 identifies this need as A06:2021-Vulnerable and Outdated Components. OWASP has several tools for this, including Dependency Check and Dependency Track. These tools will warn about the use of components with vulnerabilities. - Source: dev.to / 16 days ago

Https://dependencytrack.org/ You just need to use one of the various tools out there to scan. - Source: Hacker News / 7 months ago

OWASP Dependency Track - https://dependencytrack.org/. Source: 11 months ago

I actually want to build the same thing you are after, and I think I’ll go for the setup you describe in idea 2. The tool you can use for this is Trivy (https://trivy.dev), have it generate a SBOM and send it to Dependencytrack (https://dependencytrack.org). Source: over 1 year ago