[{"data":1,"prerenderedAt":173},["ShallowReactive",2],{"seo-verification":3,"blog-self-host-defectdojo-vps-devsecops-ma-en":6,"promo-bar-likely":164},{"google":4,"bing":5},"EycwPY2XMyTkVzas3n1ygeNJFGAH513qrMjfDljzsMQ","",{"key":7,"data":8},"blog-self-host-defectdojo-vps-devsecops-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":114,"ctaBody":115,"ctaButton":116,"ctaUrl":117,"relatedPosts":118},589,"self-host-defectdojo-vps-devsecops",{"fr":12,"en":10,"ar":13,"es":14},"self-host-defectdojo-vps","استضافة-defectdojo-على-vps","autoalojar-defectdojo-vps-devsecops","DefectDojo on a VPS: centralize your vulnerabilities","Install OWASP DefectDojo on a VPS with Docker Compose: PostgreSQL, HTTPS behind nginx, Trivy, Semgrep or ZAP reports imported from CI and every flaw tracked.",7,0,false,"2026-11-21T00: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-defectdojo-vps-poster.svg",{"categorySlug":33,"appSlug":34},"cybersecurity-bastion","defectdojo","Trivy in CI, Semgrep on pull requests, a weekly ZAP scan, a yearly penetration test: each tool produces its own report, in its own format, and nobody knows any more which flaw has already been fixed. OWASP DefectDojo gathers all these results into a single list, removes duplicates, closes what has disappeared and gives each finding a remediation deadline. This guide installs it on a VPS with Docker Compose, publishes it over HTTPS behind nginx and wires it into your pipeline.",[],[38,42,52,79,82,95,99,102,105,108,111],{"type":39,"title":40,"body":41},"h2","What DefectDojo does","DefectDojo is an OWASP flagship project, released under the **BSD-3-Clause** license and written in Python with Django. It is not a scanner: it does not look for flaws itself. It receives the reports of your scanners — more than 200 formats recognized — and turns them into **findings** organized in a simple hierarchy: product type, product, engagement, test.\n\nIts value lies in what it does with those findings: it recognizes the same flaw seen twice, closes the ones that disappeared at the next scan, attaches a severity, an owner and a deadline, and keeps a record of every decision — including risk acceptance.",{"type":43,"title":44,"items":45},"ul","What DefectDojo gives you",[46,47,48,49,50,51],"**One list** — results from Trivy, Semgrep, Gitleaks, ZAP, Burp or Nessus in the same place, in the same format.","**Deduplication** — a flaw found by two tools, or on every build, appears only once.","**Reimport** — a new report closes fixed findings and adds new ones, without losing history.","**Deadlines (SLA)** — a remediation deadline per severity, with overdue findings highlighted.","**Recorded decisions** — false positive, out of scope or risk accepted until a date, with its justification.","**A complete API and Jira** — import from CI, tickets created and kept in sync, reports for clients and auditors.",{"type":53,"title":54,"headers":55,"rows":58},"comparison","Scattered scanner reports or DefectDojo on your VPS",[5,56,57],"Reports left in CI","With DefectDojo on your VPS",[59,63,67,71,75],[60,61,62],"Where to read results","One log per tool and per build","A single list per product",[64,65,66],"Duplicates","Every build repeats the same flaws","Deduplicated automatically",[68,69,70],"Fixed flaw","Checked by hand","Closed at the next reimport",[72,73,74],"Remediation deadline","Not tracked","SLA per severity, overdue items visible",[76,77,78],"Evidence for an audit","To be reconstructed","Dated history of every finding",{"type":39,"title":80,"body":81},"Prepare the server","Plan an Ubuntu 24.04 VPS with at least **2 GB of RAM** and 2 vCPUs: all the containers together use about 700 MB at rest. Move to **4 GB** if you import reports on every build across several products, since the Celery worker handles imports and deduplication. Allow 20 GB of disk.\n\nYou also need Docker with the Compose plugin, and a domain name (or subdomain) pointing to the VPS: your pipelines will upload their reports to that address over HTTPS.",{"type":83,"title":84,"steps":85},"steps","Install DefectDojo with Docker Compose",[86,89,92],{"title":87,"body":88},"Prepare the folder and the .env file","The file holds the domain, the database password, the admin password and the application's two keys.\n```bash\nmkdir -p \u002Fopt\u002Fdefectdojo && cd \u002Fopt\u002Fdefectdojo\ncat > .env \u003C\u003CEOF\nDOMAIN=defectdojo.example.com\nDB_PASSWORD=$(openssl rand -hex 16)\nADMIN_PASSWORD=$(openssl rand -hex 12)\nSECRET_KEY=$(openssl rand -hex 24)\nAES_KEY=$(openssl rand -hex 16)\nEOF\nchmod 600 .env\n```",{"title":90,"body":91},"Write the docker-compose.yml file","Seven services: PostgreSQL, Valkey (task queue and cache), the initializer, the application (uWSGI), the Celery worker and scheduler, and DefectDojo's official nginx. The images come from Docker Hub. The port is published on the loopback only: only the VPS's nginx will face the Internet.\n```yaml\nx-dd-env: &dd-env\n  DD_DATABASE_URL: postgresql:\u002F\u002Fdefectdojo:${DB_PASSWORD}@postgres:5432\u002Fdefectdojo\n  DD_CELERY_BROKER_URL: redis:\u002F\u002Fvalkey:6379\u002F0\n  DD_CACHE_URL: redis:\u002F\u002Fvalkey:6379\u002F1\n  DD_SECRET_KEY: ${SECRET_KEY}\n  DD_CREDENTIAL_AES_256_KEY: ${AES_KEY}\n  DD_ALLOWED_HOSTS: \"*\"\n  DD_SITE_URL: https:\u002F\u002F${DOMAIN}\n  DD_CSRF_TRUSTED_ORIGINS: https:\u002F\u002F${DOMAIN}\n  DD_SECURE_PROXY_SSL_HEADER: \"True\"\n\nservices:\n  postgres:\n    image: postgres:18.6-alpine\n    restart: unless-stopped\n    environment:\n      POSTGRES_DB: defectdojo\n      POSTGRES_USER: defectdojo\n      POSTGRES_PASSWORD: ${DB_PASSWORD}\n    volumes:\n      - postgres:\u002Fvar\u002Flib\u002Fpostgresql\u002Fdata\n    healthcheck:\n      test: [\"CMD-SHELL\", \"pg_isready -q -U defectdojo\"]\n      interval: 10s\n      retries: 30\n\n  valkey:\n    image: valkey\u002Fvalkey:9.1.2-alpine\n    restart: unless-stopped\n    volumes:\n      - valkey:\u002Fdata\n\n  initializer:\n    image: defectdojo\u002Fdefectdojo-django:3.5.202\n    restart: \"no\"\n    depends_on:\n      postgres:\n        condition: service_healthy\n    entrypoint: [\"\u002Fwait-for-it.sh\", \"postgres:5432\", \"--\", \"\u002Fentrypoint-initializer.sh\"]\n    environment:\n      \u003C\u003C: *dd-env\n      DD_INITIALIZE: \"true\"\n      DD_ADMIN_USER: admin\n      DD_ADMIN_MAIL: admin@example.com\n      DD_ADMIN_PASSWORD: ${ADMIN_PASSWORD}\n\n  uwsgi:\n    image: defectdojo\u002Fdefectdojo-django:3.5.202\n    restart: unless-stopped\n    depends_on:\n      initializer:\n        condition: service_completed_successfully\n    entrypoint: [\"\u002Fwait-for-it.sh\", \"postgres:5432\", \"--\", \"\u002Fentrypoint-uwsgi.sh\"]\n    environment: *dd-env\n    volumes:\n      - media:\u002Fapp\u002Fmedia\n\n  celerybeat:\n    image: defectdojo\u002Fdefectdojo-django:3.5.202\n    restart: unless-stopped\n    depends_on:\n      initializer:\n        condition: service_completed_successfully\n    entrypoint: [\"\u002Fwait-for-it.sh\", \"postgres:5432\", \"--\", \"\u002Fentrypoint-celery-beat.sh\"]\n    environment: *dd-env\n\n  celeryworker:\n    image: defectdojo\u002Fdefectdojo-django:3.5.202\n    restart: unless-stopped\n    depends_on:\n      initializer:\n        condition: service_completed_successfully\n    entrypoint: [\"\u002Fwait-for-it.sh\", \"postgres:5432\", \"--\", \"\u002Fentrypoint-celery-worker.sh\"]\n    environment: *dd-env\n    volumes:\n      - media:\u002Fapp\u002Fmedia\n\n  nginx:\n    image: defectdojo\u002Fdefectdojo-nginx:3.5.202\n    restart: unless-stopped\n    depends_on: [uwsgi]\n    ports:\n      - \"127.0.0.1:8080:8080\"\n    volumes:\n      - media:\u002Fusr\u002Fshare\u002Fnginx\u002Fhtml\u002Fmedia\n\nvolumes:\n  postgres: {}\n  valkey: {}\n  media: {}\n```",{"title":93,"body":94},"Start the stack","The initializer applies the migrations, loads the reference data and creates the `admin` account with `ADMIN_PASSWORD`, then stops. The other services wait for it to finish: allow a few minutes on first start.\n```bash\ndocker compose up -d\ndocker compose logs -f initializer\ncurl -s -o \u002Fdev\u002Fnull -w '%{http_code}\\n' http:\u002F\u002F127.0.0.1:8080\u002Flogin\n```\nThe last command answers `200` once the interface is ready.",{"type":96,"title":97,"body":98},"tip","Set the admin password yourself","Without `DD_ADMIN_PASSWORD`, DefectDojo draws a random password and writes it **only to the log** of the initializer, which any user of the `docker` group can read back. Put it in the `.env` file and change it at first sign-in if other people have access to the server. Remember `DD_CSRF_TRUSTED_ORIGINS` too: behind an HTTPS proxy, Django rejects the login form without it (CSRF error 403).",{"type":39,"title":100,"body":101},"Publish DefectDojo over HTTPS behind nginx","The VPS's nginx receives the domain and forwards to the local port. Raise `client_max_body_size`: a Nessus or ZAP report quickly exceeds the default 1 MB limit, and the import would fail with a 413 error.\n```nginx\nserver {\n  listen 443 ssl;\n  server_name defectdojo.example.com;\n  # Let's Encrypt certificates (certbot --nginx)\n  client_max_body_size 100m;\n  location \u002F {\n    proxy_pass http:\u002F\u002F127.0.0.1:8080;\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 https;\n    proxy_read_timeout 300s;\n  }\n}\n```\nGet the certificate with `certbot --nginx -d defectdojo.example.com`, then open `https:\u002F\u002Fdefectdojo.example.com` and sign in as `admin`.",{"type":39,"title":103,"body":104},"Import reports from CI","In your profile menu, open **API v2 Key** and copy the token; preferably create a dedicated service account, since the token acts with its owner's rights. Store it in your CI secrets.\n\nThen use the `reimport-scan` endpoint rather than `import-scan`: it updates the same test on every build instead of creating a new one, and `close_old_findings` closes what has disappeared. Example for GitHub Actions:\n```yaml\n- name: Send the Trivy report to DefectDojo\n  run: |\n    trivy image --format json -o trivy.json \"$IMAGE\"\n    curl -fsS -X POST \"https:\u002F\u002F$DD_HOST\u002Fapi\u002Fv2\u002Freimport-scan\u002F\" \\\n      -H \"Authorization: Token $DD_API_KEY\" \\\n      -F scan_type=\"Trivy Scan\" -F file=@trivy.json \\\n      -F product_type_name=\"Applications\" -F product_name=\"my-app\" \\\n      -F engagement_name=\"ci-main\" -F auto_create_context=true \\\n      -F close_old_findings=true -F minimum_severity=Low\n```\nThe same call works from GitLab CI or Jenkins; only `scan_type` changes from one tool to another (`Semgrep JSON Report`, `Gitleaks Scan`, `ZAP Scan`…).",{"type":39,"title":106,"body":107},"Triage, set deadlines, accept a risk","Under **Configuration → SLA Configuration**, set a deadline per severity, for example 7 days for a critical flaw and 30 for a high one: overdue findings stand out on the dashboard. Each finding can then be marked **false positive**, **out of scope** or covered by a dated **risk acceptance**, with its justification. Connect Jira under **Configuration → JIRA** to create one ticket per finding or per group of findings and keep statuses in sync.",{"type":39,"title":109,"body":110},"Backup and upgrades","All the useful state lives in PostgreSQL, plus the attachments in the `media` volume. Back up the database every night:\n```bash\ncd \u002Fopt\u002Fdefectdojo\ndocker compose exec -T postgres pg_dump -U defectdojo defectdojo | gzip > \u002Froot\u002Fdefectdojo-$(date +%F).sql.gz\n```\nTo upgrade, change the version number of the three `defectdojo` images in the Compose file, then run `docker compose pull && docker compose up -d`: the initializer replays the migrations before the application restarts. Read the release notes before skipping several versions at once.",{"type":39,"title":112,"body":113},"DefectDojo in one click on ServOrbit","On a ServOrbit VPS, DefectDojo installs from the Marketplace: official images, PostgreSQL and Valkey, an admin account created with a generated password shown in your client area, and an nginx reverse proxy over HTTPS on your domain or on the VPS's free subdomain. Pair it with **Dependency-Track** for your dependencies and **SonarQube** for code quality: DefectDojo can import their results.","Your vulnerabilities tracked, on your VPS","A ServOrbit Ubuntu 24.04 VPS with 2 GB of RAM is enough to start with DefectDojo. One-click install from the Marketplace, HTTPS on your domain or on the VPS's free subdomain, admin account created with a generated password.","Install DefectDojo","\u002Fapplications\u002Fcybersecurity-bastion\u002Fdefectdojo",[119,135,154],{"id":120,"slug":121,"slugs":122,"title":126,"excerpt":127,"readTime":17,"views":18,"isPinned":19,"noindex":19,"publishedAt":128,"updatedAt":21,"category":129,"categories":130,"featuredImage":29,"bgImage":30,"posterImage":132,"relatedSolution":133},587,"self-host-dependency-track-vps-sbom",{"fr":123,"en":121,"ar":124,"es":125},"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.","2026-11-20T00:00:00+00:00",{"id":17,"name":23,"slug":24,"color":25,"icon":26},[131],{"id":17,"name":23,"slug":24,"color":25,"icon":26},"\u002Fblog\u002Fcovers\u002Fself-host-dependency-track-vps-poster.svg",{"categorySlug":33,"appSlug":134},"dependency-track",{"id":136,"slug":137,"slugs":138,"title":142,"excerpt":143,"readTime":144,"views":18,"isPinned":19,"noindex":19,"publishedAt":145,"updatedAt":146,"category":147,"categories":148,"featuredImage":29,"bgImage":30,"posterImage":150,"relatedSolution":151},581,"self-host-sonarqube-vps-code-quality",{"fr":139,"en":137,"ar":140,"es":141},"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},[149],{"id":17,"name":23,"slug":24,"color":25,"icon":26},"\u002Fblog\u002Fcovers\u002Fself-host-sonarqube-vps-poster.svg",{"categorySlug":152,"appSlug":153},"development","sonarqube",{"id":155,"slug":156,"slugs":157,"title":161,"excerpt":162,"readTime":17,"views":163,"isPinned":19,"noindex":164,"publishedAt":165,"updatedAt":166,"category":167,"categories":168,"featuredImage":29,"bgImage":30,"posterImage":170,"relatedSolution":171},515,"self-host-jenkins-ci-cd-server-vps",{"fr":158,"en":156,"ar":159,"es":160},"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},[169],{"id":17,"name":23,"slug":24,"color":25,"icon":26},"\u002Fblog\u002Fcovers\u002Fself-host-jenkins-vps-poster.svg",{"categorySlug":152,"appSlug":172},"jenkins",1795272647991]