# Dependency-Track

> Software composition analysis and supply chain security.

- Category: DevOps & CI/CD
- Difficulty: intermediate
- Components: dependency-track-api, dependency-track-frontend
- Tags: dependency-track, sbom, security, vulnerabilities
- Source: https://docker.recipes/devops/dependency-track

## Overview

Dependency-Track is an intelligent Software Composition Analysis (SCA) platform designed to identify, track, and reduce risk across software supply chains through continuous monitoring of third-party and open source components. The dependency-track-api serves as the core engine, processing Software Bills of Materials (SBOMs), correlating component data with vulnerability databases like the National Vulnerability Database (NVD), OSS Index, and GitHub Security Advisories, while performing license risk analysis and policy enforcement. The dependency-track-frontend provides an intuitive web interface for visualization, reporting, and management of component inventories and security findings. This PostgreSQL-backed deployment creates a comprehensive supply chain security monitoring system capable of ingesting SBOMs in CycloneDX, SPDX, and SWID formats while providing real-time vulnerability intelligence, policy violation alerts, and detailed risk metrics across your entire software portfolio. Organizations implementing DevSecOps practices, compliance teams managing software inventories, and security teams responsible for third-party risk assessment will find this stack essential for maintaining visibility into component vulnerabilities, license compliance issues, and supply chain threats throughout the software development lifecycle.

## Features

- Multi-format SBOM ingestion supporting CycloneDX, SPDX 2.2/2.3, and SWID tag formats with automated component identification and cataloging
- Continuous vulnerability monitoring against multiple intelligence sources including NVD, OSS Index, GitHub Security Advisories, and VulnDB with real-time updates
- Component risk scoring and prioritization using CVSS metrics, EPSS probability scores, and exploitability assessments
- License risk analysis and compliance tracking with configurable policy enforcement for prohibited, restricted, and approved licenses
- Portfolio-wide vulnerability trending and metrics with executive dashboards showing risk reduction over time
- Webhook and notification integrations supporting Slack, Microsoft Teams, email alerts, and custom endpoints for policy violations
- RESTful API with comprehensive endpoints for SBOM uploads, vulnerability queries, and integration with CI/CD pipelines
- Component aging analysis identifying outdated dependencies and recommending version upgrades with security impact assessment

## Use cases

- Enterprise software composition analysis for tracking vulnerabilities across hundreds of applications and their third-party dependencies
- DevSecOps pipeline integration for automated SBOM analysis during CI/CD builds with build-breaking policy violations
- Regulatory compliance reporting for industries requiring software inventory documentation like healthcare, finance, and government contracting
- Vendor risk assessment programs where procurement teams evaluate third-party software components for security and licensing risks
- Incident response support for rapidly identifying which applications contain specific vulnerable components during security events
- Open source governance programs managing approved component libraries and enforcing corporate licensing policies
- Supply chain security monitoring for detecting newly disclosed vulnerabilities in previously approved software components

## Prerequisites

- Minimum 4GB RAM allocated to Docker with 8GB recommended for organizations processing large SBOM portfolios
- PostgreSQL database storage planning with at least 10GB initial space, scaling based on component inventory size and retention policies
- Port availability for 8080 (frontend), 8081 (API), and 5432 (PostgreSQL) with firewall configurations allowing access from client networks
- Understanding of SBOM generation tools like CycloneDX CLI, Syft, or Trivy for creating software inventories from your applications
- Network connectivity for vulnerability database synchronization requiring outbound HTTPS access to NVD, OSS Index, and other intelligence sources
- Database password configuration through environment variables with secure credential management practices

## docker-compose.yml

```yaml
services:
  dtrack-api:
    image: dependencytrack/apiserver:latest
    container_name: dtrack-api
    restart: unless-stopped
    environment:
      ALPINE_DATABASE_MODE: external
      ALPINE_DATABASE_URL: jdbc:postgresql://dtrack-db:5432/dtrack
      ALPINE_DATABASE_DRIVER: org.postgresql.Driver
      ALPINE_DATABASE_USERNAME: dtrack
      ALPINE_DATABASE_PASSWORD: ${DB_PASSWORD}
    ports:
      - "8081:8080"
    volumes:
      - dtrack_data:/data
    depends_on:
      - dtrack-db

  dtrack-frontend:
    image: dependencytrack/frontend:latest
    container_name: dtrack-frontend
    restart: unless-stopped
    environment:
      API_BASE_URL: http://localhost:8081
    ports:
      - "8080:8080"
    depends_on:
      - dtrack-api

  dtrack-db:
    image: postgres:15-alpine
    container_name: dtrack-db
    restart: unless-stopped
    environment:
      POSTGRES_USER: dtrack
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_DB: dtrack
    volumes:
      - dtrack_db:/var/lib/postgresql/data

volumes:
  dtrack_data:
  dtrack_db:
```

## .env

```bash
DB_PASSWORD=changeme
```

## Usage notes

- Docs: https://docs.dependencytrack.org/
- Access at http://localhost:8080 (frontend) - default: admin/admin
- API at http://localhost:8081 - generate API key in UI for automation
- Upload SBOMs: CycloneDX (preferred), SPDX, or VEX formats
- Generate SBOM: cyclonedx-cli/syft/trivy for various ecosystems
- Policy violations and vulnerability alerts via webhooks/email

## Troubleshooting

- Database connection failures with 'could not connect to server': Verify PostgreSQL container startup and DB_PASSWORD environment variable matches between API server and database containers
- Frontend showing 'API Server Unavailable': Check API_BASE_URL environment variable points to correct API server address and port 8081 accessibility from frontend container
- SBOM upload failures with 'unsupported format' errors: Ensure SBOM files are valid CycloneDX JSON/XML, SPDX 2.2+ JSON, or contain proper component structure with required fields
- Vulnerability data not updating with outdated CVE information: Verify outbound internet connectivity from API container and check vulnerability source configurations in administration settings
- High memory usage during vulnerability analysis: Increase Docker memory limits and consider adjusting ALPINE_DATABASE_POOL_MAX_SIZE for connection optimization
- Policy violations not triggering notifications: Confirm webhook URLs are accessible, notification rules are enabled, and policy conditions match your component criteria

