[{"data":1,"prerenderedAt":181},["ShallowReactive",2],{"seo-verification":3,"blog-self-host-dependency-track-vps-sbom-ma-en":6,"promo-bar-likely":154},{"google":4,"bing":5},"EycwPY2XMyTkVzas3n1ygeNJFGAH513qrMjfDljzsMQ","",{"key":7,"data":8},"blog-self-host-dependency-track-vps-sbom-ma-en",{"id":9,"slug":10,"slugs":11,"title":15,"excerpt":16,"readTime":17,"views":18,"isPinned":19,"noindex":19,"publishedAt":20,"updatedAt":21,"category":22,"categories":27,"featuredImage":29,"bgImage":30,"posterImage":31,"relatedSolution":32,"intro":35,"keyPoints":36,"sections":37,"ctaTitle":120,"ctaBody":121,"ctaButton":122,"ctaUrl":123,"relatedPosts":124},587,"self-host-dependency-track-vps-sbom",{"fr":12,"en":10,"ar":13,"es":14},"self-host-dependency-track-vps","استضافة-dependency-track-على-vps","autoalojar-dependency-track-vps-sbom","Dependency-Track on a VPS: SBOMs and vulnerable dependencies","Self-host OWASP Dependency-Track on a VPS with Docker Compose: PostgreSQL, HTTPS behind nginx, SBOM uploads from CI and alerts on vulnerable dependencies.",7,0,false,"2026-11-20T00:00:00+00:00","2026-11-21T14:39:55+00:00",{"id":17,"name":23,"slug":24,"color":25,"icon":26},"Self-hosting","self-hosting","bg-indigo-500\u002F10 text-indigo-400","cloud",[28],{"id":17,"name":23,"slug":24,"color":25,"icon":26},null,"\u002Fblog\u002Fcovers\u002Fbg.svg","\u002Fblog\u002Fcovers\u002Fself-host-dependency-track-vps-poster.svg",{"categorySlug":33,"appSlug":34},"cybersecurity-bastion","dependency-track","A modern application ships hundreds of libraries that nobody picked one by one. The day a critical vulnerability hits one of them, the only question that matters is: where did we deploy it? OWASP Dependency-Track answers it continuously. Your CI sends it the SBOM of every build, it matches each component against public vulnerability databases and warns you as soon as a version in production is affected. This guide installs it on a VPS with Docker Compose, replaces the factory password, publishes it over HTTPS behind nginx and connects it to your pipeline.",[],[38,42,52,79,82,101,105,108,111,114,117],{"type":39,"title":40,"body":41},"h2","What Dependency-Track does","Dependency-Track is an OWASP flagship project, released under the Apache-2.0 licence. It does not read your code: it reads the **inventory** of what your application ships, the SBOM (Software Bill of Materials), in CycloneDX format. Each component in it is identified by its Package URL (`pkg:npm\u002Flodash@4.17.21`, `pkg:maven\u002F…`), which lets it be matched unambiguously against vulnerability databases: NVD, GitHub Advisories, OSV.\n\nThe difference from a scanner run in CI is time. The scanner judges today's build; Dependency-Track keeps **every** version of **all** your projects and re-evaluates them each time its databases are updated. A vulnerability published three months from now will be flagged on the version you deploy today.",{"type":43,"title":44,"items":45},"ul","What Dependency-Track gives you",[46,47,48,49,50,51],"**A portfolio** — every application and every version, with the list of its direct and transitive components.","**Retroactive alerts** — a vulnerability published after deployment surfaces on the versions already in production.","**Policies** — forbidden licences, maximum tolerated severity, banned components, evaluated on every SBOM upload.","**Vulnerability triage** — severity, EPSS exploit probability score, and analysis tracking (“not affected”, “resolved”…).","**Notifications** — Slack, Microsoft Teams, webhook or email, per project and per severity.","**A complete API** — SBOM uploads, result retrieval and administration, with per-team API keys.",{"type":53,"title":54,"headers":55,"rows":58},"comparison","One-off scanner or Dependency-Track on your VPS",[5,56,57],"Scanner run in CI","With Dependency-Track on your VPS",[59,63,67,71,75],[60,61,62],"When the analysis runs","At build time, then nothing","On every build, then continuously",[64,65,66],"Vulnerability published after deployment","Invisible until the next build","Flagged on the versions in production",[68,69,70],"Overview","One report per repository","The whole portfolio, searchable by component",[72,73,74],"Licences","Depends on the tool","Explicit licence policies",[76,77,78],"Where the inventory lives","In CI logs","On your VPS, with its history",{"type":39,"title":80,"body":81},"Prepare the server","Plan an Ubuntu 24.04 VPS with at least **4 GB of RAM** and 2 vCPUs: the API server, written in Java, is capped at 2 GB, and PostgreSQL shares the rest with the system. Beyond a few dozen projects analysed each day, move up to 8 GB. Count on 30 GB of disk.\n\nInstall Docker and the Compose plugin, then point a subdomain (for example `dtrack.example.com`) at the VPS's IP address: your pipelines will upload their SBOMs to this address, and the web interface will open there.\n\n```bash\ncurl -fsSL https:\u002F\u002Fget.docker.com | sh\ndocker compose version\n```",{"type":83,"title":84,"steps":85},"steps","Install Dependency-Track with Docker Compose",[86,89,92,95,98],{"title":87,"body":88},"Prepare the directory and the .env file","The file holds the PostgreSQL database password and the admin account password.\n```bash\nmkdir -p \u002Fopt\u002Fdependency-track && cd \u002Fopt\u002Fdependency-track\ncat > .env \u003C\u003CEOF\nDB_PASSWORD=$(openssl rand -hex 16)\nADMIN_PASSWORD=$(openssl rand -hex 16)\nEOF\nchmod 600 .env\n```",{"title":90,"body":91},"Write the internal proxy configuration","The web interface calls the API on its own address. A small nginx therefore routes `\u002Fapi` to the API server and everything else to the interface: one port to publish, one domain, no CORS settings.\n```nginx\nserver {\n  listen 80;\n  client_max_body_size 64m;\n  location \u002Fapi\u002F {\n    proxy_pass http:\u002F\u002Fapiserver:8080;\n    proxy_set_header Host $host;\n    proxy_set_header X-Forwarded-Proto $scheme;\n    proxy_read_timeout 300s;\n  }\n  location \u002F {\n    proxy_pass http:\u002F\u002Ffrontend:8080;\n    proxy_set_header Host $host;\n  }\n}\n```\nSave this block as `\u002Fopt\u002Fdependency-track\u002Fproxy.conf`.",{"title":93,"body":94},"Write the docker-compose.yml file","Four services: PostgreSQL, the API server, the interface and the proxy. The port is published on the loopback interface only: just the VPS's nginx will be exposed to the internet.\n```yaml\nservices:\n  db:\n    image: postgres:18.7-alpine\n    restart: unless-stopped\n    environment:\n      POSTGRES_DB: dtrack\n      POSTGRES_USER: dtrack\n      POSTGRES_PASSWORD: ${DB_PASSWORD}\n    volumes:\n      - db:\u002Fvar\u002Flib\u002Fpostgresql\n    healthcheck:\n      test: [\"CMD-SHELL\", \"pg_isready -q -U dtrack -d dtrack\"]\n      interval: 10s\n      retries: 30\n\n  apiserver:\n    image: ghcr.io\u002Fdependencytrack\u002Fapiserver:5.2.2\n    restart: unless-stopped\n    depends_on:\n      db:\n        condition: service_healthy\n    deploy:\n      resources:\n        limits:\n          memory: 2g\n    environment:\n      DT_DATASOURCE_URL: jdbc:postgresql:\u002F\u002Fdb:5432\u002Fdtrack\n      DT_DATASOURCE_USERNAME: dtrack\n      DT_DATASOURCE_PASSWORD: ${DB_PASSWORD}\n    volumes:\n      - data:\u002Fdata\n\n  frontend:\n    image: ghcr.io\u002Fdependencytrack\u002Ffrontend:5.2.2\n    restart: unless-stopped\n    environment:\n      API_BASE_URL: \"\"\n\n  proxy:\n    image: nginx:1.27-alpine\n    restart: unless-stopped\n    depends_on: [apiserver, frontend]\n    ports:\n      - \"127.0.0.1:8127:80\"\n    volumes:\n      - .\u002Fproxy.conf:\u002Fetc\u002Fnginx\u002Fconf.d\u002Fdefault.conf:ro\n\nvolumes:\n  db: {}\n  data: {}\n```",{"title":96,"body":97},"Start the stack","The first start creates the database schema, then the API server downloads the vulnerability databases in the background.\n```bash\ndocker compose up -d\ncurl -s http:\u002F\u002F127.0.0.1:8127\u002Fapi\u002Fversion\n```\nThe second command returns the server version as soon as the API is ready.",{"title":99,"body":100},"Replace the factory password","The `admin` account is created with the password `admin`. Replace it before publishing anything:\n```bash\n. .\u002F.env\ncurl -fsS http:\u002F\u002F127.0.0.1:8127\u002Fapi\u002Fv1\u002Fuser\u002FforceChangePassword \\\n  --data-urlencode username=admin --data-urlencode password=admin \\\n  --data-urlencode newPassword=\"$ADMIN_PASSWORD\" \\\n  --data-urlencode confirmPassword=\"$ADMIN_PASSWORD\"\n```",{"type":102,"title":103,"body":104},"tip","Never publish an instance with admin\u002Fadmin","Dependency-Track does force a password change at first login, but between startup and that login, anyone can do it in your place and take over the inventory of your applications — in other words, the list of their vulnerabilities. Replace the password **before** configuring nginx.",{"type":39,"title":106,"body":107},"Publish Dependency-Track over HTTPS behind nginx","The VPS's nginx receives the domain and forwards to the local port. Raise the upload size: the SBOM of a sizeable application quickly exceeds the one megabyte nginx accepts by default.\n\n```nginx\nserver {\n  server_name dtrack.example.com;\n  client_max_body_size 64m;\n  location \u002F {\n    proxy_pass http:\u002F\u002F127.0.0.1:8127;\n    proxy_set_header Host $host;\n    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\n    proxy_set_header X-Forwarded-Proto $scheme;\n  }\n}\n```\n\nThen issue the certificate with `certbot --nginx -d dtrack.example.com`. Open `https:\u002F\u002Fdtrack.example.com`, log in with `admin` and your new password, and create your team's accounts under **Administration → Access Management**.",{"type":39,"title":109,"body":110},"Upload SBOMs from your CI","In **Administration → Access Management → Teams**, open the **Automation** team and generate an API key; store it in your CI secrets. The pipeline then produces the SBOM and uploads it on every build — here with cdxgen, which recognises most ecosystems (npm, Maven, PyPI, Composer, Go…):\n\n```yaml\n# .github\u002Fworkflows\u002Fsbom.yml\nname: sbom\non: [push]\njobs:\n  sbom:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions\u002Fcheckout@v4\n      - run: npx --yes @cyclonedx\u002Fcdxgen -o bom.json\n      - run: |\n          curl -fsS -X POST https:\u002F\u002Fdtrack.example.com\u002Fapi\u002Fv1\u002Fbom \\\n            -H \"X-Api-Key: ${{ secrets.DT_API_KEY }}\" \\\n            -F autoCreate=true -F projectName=${{ github.event.repository.name }} \\\n            -F projectVersion=${{ github.ref_name }} -F bom=@bom.json\n```\n\nThe project appears in the portfolio with the uploaded version. For a container image, `syft \u003Cimage> -o cyclonedx-json > bom.json` produces the equivalent, system packages included.",{"type":39,"title":112,"body":113},"Policies and notifications","A policy turns a finding into a rule. In **Policy Management**, create for example a security policy that flags any vulnerability of severity *High* or above, and a licence policy that rejects the licences your contract forbids. Every SBOM upload is evaluated, and violations are shown on the project.\n\nThen, in **Administration → Notifications**, connect a channel — Slack, Microsoft Teams, webhook or email — to the *New Vulnerability* and *Policy Violation* events, limited to the projects that matter. This alert is what makes the tool worthwhile: it arrives the day the vulnerability is published, not the day of the next build.",{"type":39,"title":115,"body":116},"Backup and upgrades","All the useful state lives in PostgreSQL: projects, SBOMs, analyses and settings. Back up the database; the `\u002Fdata` directory can be rebuilt (it mostly holds the downloaded vulnerability databases).\n\n```bash\ncd \u002Fopt\u002Fdependency-track\ndocker compose exec -T db pg_dump -U dtrack dtrack | gzip > dtrack-$(date +%F).sql.gz\n```\n\nTo upgrade, read the release notes, change both image tags (`apiserver` and `frontend`, always at the **same** version), then run `docker compose pull && docker compose up -d`. The API server migrates the schema on startup. Keep a recent backup before every version upgrade.",{"type":39,"title":118,"body":119},"One-click Dependency-Track on ServOrbit","On a ServOrbit VPS, Dependency-Track installs from the Marketplace: official images, PostgreSQL and the internal proxy in place, the admin account's factory password replaced with a generated one shown in your client area, and the nginx reverse proxy over HTTPS on your domain or on the VPS's free subdomain. All that is left is to create the CI API key and upload your first SBOM.","Your dependencies under watch, on your VPS","A ServOrbit Ubuntu 24.04 VPS with 4 GB of RAM is enough to start with Dependency-Track. One-click install from the Marketplace, HTTPS on your domain or on the VPS's free subdomain, factory password replaced for you.","Install Dependency-Track","\u002Fapplications\u002Fcybersecurity-bastion\u002Fdependency-track",[125,144,163],{"id":126,"slug":127,"slugs":128,"title":132,"excerpt":133,"readTime":134,"views":18,"isPinned":19,"noindex":19,"publishedAt":135,"updatedAt":136,"category":137,"categories":138,"featuredImage":29,"bgImage":30,"posterImage":140,"relatedSolution":141},581,"self-host-sonarqube-vps-code-quality",{"fr":129,"en":127,"ar":130,"es":131},"self-host-sonarqube-vps","استضافة-sonarqube-على-vps","autoalojar-sonarqube-vps-calidad-codigo","SonarQube on a VPS: self-hosted code quality and security","Install SonarQube Community Build on a VPS with Docker Compose: PostgreSQL, HTTPS behind nginx, an analysis token and a quality gate in your CI.",6,"2026-11-16T00:00:00+00:00","2026-11-20T14:16:42+00:00",{"id":17,"name":23,"slug":24,"color":25,"icon":26},[139],{"id":17,"name":23,"slug":24,"color":25,"icon":26},"\u002Fblog\u002Fcovers\u002Fself-host-sonarqube-vps-poster.svg",{"categorySlug":142,"appSlug":143},"development","sonarqube",{"id":145,"slug":146,"slugs":147,"title":151,"excerpt":152,"readTime":17,"views":153,"isPinned":19,"noindex":154,"publishedAt":155,"updatedAt":156,"category":157,"categories":158,"featuredImage":29,"bgImage":30,"posterImage":160,"relatedSolution":161},515,"self-host-jenkins-ci-cd-server-vps",{"fr":148,"en":146,"ar":149,"es":150},"self-host-jenkins-vps","استضافة-jenkins-على-vps-خادم-ci-cd","autoalojar-jenkins-servidor-ci-cd-vps","Jenkins on a VPS: your open-source CI\u002FCD server with Docker","Install Jenkins LTS on a VPS with Docker Compose: Jenkinsfile pipelines, Git webhooks, HTTPS behind nginx and build agents isolated from the controller.",1,true,"2026-10-28T00:00:00+00:00","2026-11-04T16:30:29+00:00",{"id":17,"name":23,"slug":24,"color":25,"icon":26},[159],{"id":17,"name":23,"slug":24,"color":25,"icon":26},"\u002Fblog\u002Fcovers\u002Fself-host-jenkins-vps-poster.svg",{"categorySlug":142,"appSlug":162},"jenkins",{"id":164,"slug":165,"slugs":166,"title":170,"excerpt":171,"readTime":172,"views":153,"isPinned":19,"noindex":19,"publishedAt":173,"updatedAt":174,"category":175,"categories":176,"featuredImage":29,"bgImage":30,"posterImage":178,"relatedSolution":179},74,"host-gitea-on-your-own-vps",{"fr":167,"en":165,"ar":168,"es":169},"heberger-gitea","استضافة-gitea-على-خادم-vps-الخاص-بك","alojar-gitea-en-un-vps","Host Gitea on your own VPS in 2026","Deploy Gitea 1.25 on a VPS with Docker and SSL. Full guide: Gitea Actions CI\u002FCD, Gitea vs Forgejo v16 comparison, daily administration, SSH and HTTPS troubleshooting.",13,"2026-04-07T00:00:00+00:00","2026-11-08T16:32:50+00:00",{"id":17,"name":23,"slug":24,"color":25,"icon":26},[177],{"id":17,"name":23,"slug":24,"color":25,"icon":26},"\u002Fblog\u002Fcovers\u002Fheberger-gitea-poster.svg",{"categorySlug":142,"appSlug":180},"gitea",1795272648049]