DefectDojo · Maffooch · Aug 18, 2026 · Aug 17, 2026 · Aug 17, 2026
@@ -13,4 +13,6 @@ seo:
   robots: "" # custom robot tags (optional)
 pro-feature: true
 exclude_search: true
+aliases:
+  - "/en/customize_dojo/notifications/"
 ---
@@ -2,6 +2,7 @@
 title: "Set System-Wide Notifications"
 description: "How to configure Personal & System notifications"
 aliases:
+  - "/en/notifications/configure_system_notifs/"
   - /en/customize_dojo/notifications/configure_system_notifs
 ---
 DefectDojo has two different kinds of notifications: **Personal** (sent to a single account) and **System** (which are sent to all users).

@@ -2,6 +2,7 @@
 title: "Set up Email, Slack or Teams notifications"
 description: "Set up Microsoft Teams to receive notifications"
 aliases:
+  - "/en/notifications/configure-a-slack-integration/"
   - /en/customize_dojo/notifications/email_slack_teams
 ---
 **You will need Superuser access to use the System Settings page, which is required to complete this process.**

@@ -4,6 +4,8 @@ description: "Configure LDAP authentication in DefectDojo Pro"
 weight: 20
 audience: pro
 aliases:
+  - "/admin/sso/os__ldap/"
+  - "/open_source/ldap-authentication/"
   - /en/open_source/ldap-authentication
 ---
 

@@ -16,6 +16,7 @@ seo:
 exclude_search: true
 pro-feature: true
 aliases:
+  - "/en/customize_dojo/user_management/configure_sso/"
   - /admin/user_management/configure_sso/
   - /admin/sso/os__saml/
   - /admin/sso/os__auth0/

@@ -4,6 +4,7 @@ description: "Access audit logs for DefectDojo objects"
 weight: 1
 audience: opensource
 aliases:
+  - "/admin/user_management/audit_logging/"
   - /en/customize_dojo/user_management/audit_logging
 ---
 Audit logs for DefectDojo can be accessed in a few different ways.

@@ -13,6 +13,8 @@ seo:
   canonical: "" # custom canonical URL (optional)
   robots: "" # custom robot tags (optional)
 exclude_search: true
+aliases:
+  - "/en/customize_dojo/user_management/"
 ---
 
 DefectDojo's user management surface is different in each edition. Pick the section that matches your installation.

@@ -15,4 +15,22 @@ seo:
   canonical: "" # custom canonical URL (optional)
   robots: "" # custom robot tags (optional)
 exclude_search: true
+aliases:
+  - "/en/open_source/archived_docs/"
+  - "/en/open_source/archived_docs/importing/"
+  - "/en/open_source/archived_docs/integrations/social-authentication/"
+  - "/en/open_source/archived_docs/jira/"
+  - "/en/open_source/archived_docs/notifications/"
+  - "/en/open_source/archived_docs/usage/features/"
+  - "/en/open_source/archived_docs/usage/index.xml"
+  - "/en/open_source/archived_docs/usage/permissions/"
+  - "/en/open_source/archived_docs/usage/questionnaires/"
+  - "/open_source/archived_docs/"
+  - "/open_source/archived_docs/burp-plugin/"
+  - "/open_source/archived_docs/google-sheets-sync/"
+  - "/open_source/archived_docs/index.xml"
+  - "/open_source/archived_docs/usage/"
+  - "/open_source/archived_docs/usage/features/"
+  - "/open_source/archived_docs/usage/models"
+  - "/open_source/archived_docs/usage/questionnaires/"
 ---
@@ -4,6 +4,7 @@ description: "How DefectDojo calculates an Asset Health Grade"
 weight: 7
 audience: opensource
 aliases:
+  - "/asset_modelling/hierarchy/product_health_grade/"
   - /asset_modelling/os_hierarchy/product_health_grade/
   - /en/asset_modelling/os_hierarchy/product_health_grade/
 ---

@@ -4,6 +4,7 @@ description: "Understand Organizations, Assets, Engagements, Tests and Findings"
 weight: 1
 audience: opensource
 aliases:
+  - "/asset_modelling/hierarchy/product_hierarchy/"
   - /en/working_with_findings/organizing_engagements_tests/product_hierarchy
   - /asset_modelling/os_hierarchy/product_hierarchy/
   - /en/asset_modelling/os_hierarchy/product_hierarchy/

@@ -4,6 +4,7 @@ description: "Configure Service Level Agreements for different Assets"
 weight: 2
 audience: opensource
 aliases:
+  - "/asset_modelling/hierarchy/os__sla_configuration/"
   - /en/working_with_findings/sla_configuration
 ---
 Each Asset in DefectDojo can have its own Service Level Agreement (SLA) configuration, which represents the days your organization has to remediate or otherwise manage a Finding.

@@ -5,6 +5,7 @@ draft: false
 weight: 5
 audience: opensource
 aliases:
+  - "/asset_modelling/hierarchy/os__source-code-repositories/"
   - /en/working_with_findings/organizing_engagements_tests/source-code-repositories
 ---
 Certain tools (particularly SAST tools) will include the associated file name and line number in vulnerability data. If the repository of the source code is specified in the Engagement, DefectDojo will present the filepath as a link and the user can navigate directly to the location of the vulnerability.

@@ -8,4 +8,6 @@ weight: 3
 sidebar:
   collapsed: false
 exclude_search: true
+aliases:
+  - "/asset_modelling/hierarchy/"
 ---
@@ -3,6 +3,8 @@ title: "OWASP ASVS Benchmarks"
 description: "Benchmark an Asset against the OWASP Application Security Verification Standard"
 weight: 6
 audience: opensource
+aliases:
+  - "/asset_modelling/hierarchy/benchmarks/"
 ---
 
 DefectDojo supports benchmarking Assets against the [OWASP Application Security Verification Standard (ASVS)](https://owasp.org/www-project-application-security-verification-standard/), which provides a basis for testing web application technical security controls.

@@ -4,8 +4,9 @@ description: "How DefectDojo ranks your Findings"
 weight: 1
 audience: pro
 aliases:
- - /en/working_with_findings/finding_priority
- - /en/working_with_findings/priority_adjustments
+  - "/asset_modelling/hierarchy/pro__priority_sla/"
+  - "/en/working_with_findings/finding_priority"
+  - "/en/working_with_findings/priority_adjustments"
 ---
 
 ![image](images/pro_finding_priority.png)

@@ -3,6 +3,8 @@ title: "Organizations"
 description: "Understanding Organizations in DefectDojo Pro"
 audience: pro
 weight: 1
+aliases:
+  - "/asset_modelling/hierarchy/pro__assets_organizations/"
 ---
 **ORGANIZATIONS** → Assets → Engagements → Tests → Findings
 

@@ -5,4 +5,6 @@ draft: false
 type: docs
 weight: 1
 exclude_search: true
+aliases:
+  - "/en/working_with_findings/organizing_engagements_tests/"
 ---
@@ -5,6 +5,8 @@ draft: false
 weight: 2
 exclude_search: false
 audience: opensource
+aliases:
+  - "/asset_modelling/tags/tagging_objects/"
 ---
 
 Tags are ideal for grouping objects in a manner that can be filtered out into smaller, more digestible chunks.  They can be used to denote status, or to create custom sets of Organizations, Assets, Engagements or Findings across the data model.

@@ -13,4 +13,6 @@ seo:
   canonical: "" # custom canonical URL (optional)
   robots: "" # custom robot tags (optional)
 exclude_search: true
+aliases:
+  - "/en/api/"
 ---
@@ -4,6 +4,7 @@ description: "Import language composition data for an Asset using the cloc tool"
 weight: 3
 audience: opensource
 aliases:
+  - "/open_source/languages/"
   - /en/open_source/languages
 ---
 

@@ -4,6 +4,19 @@ description: "Send HTTP webhook notifications to an external server on DefectDoj
 weight: 8
 audience: opensource
 aliases:
+  - "/en/open_source/notification_webhooks/"
+  - "/en/open_source/notification_webhooks/engagement_added/"
+  - "/en/open_source/notification_webhooks/ping/"
+  - "/en/open_source/notification_webhooks/scan_added/"
+  - "/open_source/notification_webhooks/"
+  - "/open_source/notification_webhooks/engagement_added/"
+  - "/open_source/notification_webhooks/how_to/"
+  - "/open_source/notification_webhooks/ping/"
+  - "/open_source/notification_webhooks/product_added"
+  - "/open_source/notification_webhooks/product_added/"
+  - "/open_source/notification_webhooks/scan_added/"
+  - "/open_source/notification_webhooks/test_added"
+  - "/open_source/notification_webhooks/test_added/"
   - /en/open_source/notification_webhooks/how_to
 ---
 

@@ -4,6 +4,7 @@ description: "Configure rate limiting on the login page to mitigate brute force
 weight: 4
 audience: opensource
 aliases:
+  - "/open_source/rate_limiting/"
   - /en/open_source/rate_limiting
 ---
 

@@ -4,6 +4,7 @@ description: "Work with the Jira integration"
 weight: 2
 audience: opensource
 aliases:
+  - "/issue_tracking/jira/jira_guide/"
   - /issue_tracking/jira/os__jira_guide/
 ---
 DefectDojo's Jira integration can be used to push Finding data to one or more Jira Spaces.  By doing so, you can integrate DefectDojo into your standard development workflow.  Here are some examples of how this can work:

@@ -3,6 +3,8 @@ title: "Online Demo"
 description: "There is DefectDojo demo site running the latest officially released version"
 draft: false
 weight: 6
+aliases:
+  - "/en/open_source/installation/demo/"
 ---
 
 Two online demos are available for DefectDojo.  Both come pre-loaded with data and are fully functional, running the latest version of DefectDojo.

@@ -76,7 +76,7 @@ Um den Unterschied zu verstehen, hilft es, sich Import als das Erfassen eines ei
 
 Hier eine Analogie: Wären Sie Buchhalter, könnten Sie Import verwenden, um einen einzelnen Beleg zu erfassen, während Sie Reimport nutzen würden, um ein fortlaufendes Ausgabenbuch zu führen.
 
-Beide Methoden nutzen die Deduplizierung außerdem unterschiedlich: Während zwei separate importierte Tests im selben Produkt doppelte Befunde jeweils eigenständig erkennen und kennzeichnen, erstellt Reimport innerhalb des Tests keine Befunde, die es als [Duplikate](/en/working_with_findings/finding_deduplication/avoiding_duplicates_via_reimport/) identifiziert.
+Beide Methoden nutzen die Deduplizierung außerdem unterschiedlich: Während zwei separate importierte Tests im selben Produkt doppelte Befunde jeweils eigenständig erkennen und kennzeichnen, erstellt Reimport innerhalb des Tests keine Befunde, die es als [Duplikate](/triage_findings/finding_deduplication/avoid_excess_duplicates/) identifiziert.
 
 Grundsätzlich gilt: Wenn Sie einen Bericht zu einem bestimmten Zeitpunkt benötigen, ist Import die beste Methode. Wenn Sie fortlaufend Berichte aus einem Tool ausführen und einlesen, ist Reimport die bessere Methode, um alles organisiert zu halten.
 

@@ -76,7 +76,7 @@ Para entender la diferencia, resulta útil pensar en Import como el registro de
 
 A modo de analogía: si fuera contador, podría usar Import para registrar un único recibo, mientras que usaría Reimport para llevar un libro contable continuo de gastos
 
-Ambos métodos también utilizan la Deduplicación de forma diferente: mientras que dos Tests Importados por separado dentro del mismo Producto identificarán y etiquetarán los Hallazgos duplicados de manera independiente, Reimport no creará ningún Hallazgo que identifique como [duplicado](/en/working_with_findings/finding_deduplication/avoiding_duplicates_via_reimport/) dentro del Test.
+Ambos métodos también utilizan la Deduplicación de forma diferente: mientras que dos Tests Importados por separado dentro del mismo Producto identificarán y etiquetarán los Hallazgos duplicados de manera independiente, Reimport no creará ningún Hallazgo que identifique como [duplicado](/triage_findings/finding_deduplication/avoid_excess_duplicates/) dentro del Test.
 
 En términos generales, si lo que necesita es un informe puntual, Import es el mejor método a utilizar. Si ejecuta e ingiere informes de una herramienta de forma continua, Reimport es el mejor método para mantener todo organizado.
 

@@ -76,7 +76,7 @@ Pour comprendre la différence, il est utile de considérer l'Import comme l'enr
 
 Voici une analogie : si vous étiez comptable, vous utiliseriez l'Import pour suivre un reçu unique, tandis que vous utiliseriez le Reimport pour tenir un registre continu des dépenses.
 
-Les deux méthodes utilisent également la Déduplication différemment : alors que deux Tests Importés distincts dans le même Produit identifieront et étiquetteront les Constatations en double séparément, le Reimport ne créera aucune Constatation qu'il identifie comme [doublon](/en/working_with_findings/finding_deduplication/avoiding_duplicates_via_reimport/) au sein du Test.
+Les deux méthodes utilisent également la Déduplication différemment : alors que deux Tests Importés distincts dans le même Produit identifieront et étiquetteront les Constatations en double séparément, le Reimport ne créera aucune Constatation qu'il identifie comme [doublon](/triage_findings/finding_deduplication/avoid_excess_duplicates/) au sein du Test.
 
 De manière générale, si vous avez besoin d'un rapport ponctuel, l'Import est la meilleure méthode à utiliser. Si vous exécutez et ingérez en continu des rapports depuis un outil, le Reimport est la meilleure méthode pour garder les choses organisées.
 

@@ -76,7 +76,7 @@ DefectDojoは、[500以上](/supported_tools/)の商用およびオープンソ
 
 たとえるなら、あなたが会計士だとして、インポートは1枚の領収書を記録するために使い、再インポートは経費の継続的な台帳を記録するために使う、というイメージです。
 
-両方の方法は、重複排除の使い方も異なります。同じ製品内で個別にインポートされた2つのテストは、重複する検出事項をそれぞれ別々に特定してラベル付けしますが、再インポートはテスト内で[重複](/en/working_with_findings/finding_deduplication/avoiding_duplicates_via_reimport/)と判断した検出事項を作成しません。
+両方の方法は、重複排除の使い方も異なります。同じ製品内で個別にインポートされた2つのテストは、重複する検出事項をそれぞれ別々に特定してラベル付けしますが、再インポートはテスト内で[重複](/triage_findings/finding_deduplication/avoid_excess_duplicates/)と判断した検出事項を作成しません。
 
 一般的に言えば、単一時点のレポートが必要な場合はインポートが最適な方法です。ツールからレポートを継続的に実行・取り込んでいる場合は、物事を整理しておくために再インポートの方が適しています。
 

@@ -75,7 +75,7 @@ To understand the difference, it’s helpful to think of Import as recording a s
 
 Here is an analogy; if you were an accountant, you could use Import to track a single receipt, while you would use Reimport to track a continuous ledger of expenses
 
-Both methods also use Deduplication differently: while two discrete Imported Tests in the same Asset will identify and label duplicate Findings separately, Reimport will not create any Findings it identifies as [duplicates](/en/working_with_findings/finding_deduplication/avoiding_duplicates_via_reimport/) within the Test.
+Both methods also use Deduplication differently: while two discrete Imported Tests in the same Asset will identify and label duplicate Findings separately, Reimport will not create any Findings it identifies as [duplicates](/triage_findings/finding_deduplication/avoid_excess_duplicates/) within the Test.
 
 Generally speaking, if a point-in-time report is what you need, Import is the best method to use. If you are continuously running and ingesting reports from a tool, Reimport is the better method for keeping things organized.
 

@@ -5,6 +5,7 @@ weight: 5
 chapter: true
 audience: opensource
 aliases:
+  - "/open_source/contributing/"
   - /en/open_source/contributing
 ---
 

@@ -5,6 +5,7 @@ draft: false
 weight: 3
 audience: opensource
 aliases:
+  - "/open_source/contributing/branching-model/"
   - /en/open_source/contributing/branching-model
 ---
 ## Regular releases

@@ -5,6 +5,7 @@ draft: false
 weight: 1
 audience: opensource
 aliases:
+  - "/open_source/contributing/how-to-write-a-parser/"
   - /en/open_source/contributing/how-to-write-a-parser
 ---
 All commands assume that you're located at the root of the django-DefectDojo cloned repo.

@@ -4,6 +4,7 @@ toc_hide: true
 weight: 2
 audience: opensource
 aliases:
+  - "/open_source/contributing/parser-documentation-template/"
   - /en/open_source/contributing/parser-documentation-template
 ---
 This template is designed to document a new or existing parser. Please feel free to improve with any additional information that might help your fellow security professionals.

@@ -3,4 +3,7 @@ title: "🔹 DefectDojo Community Edition"
 date: 2021-02-02T20:46:29+01:00
 weight: 3
 audience: opensource
+aliases:
+  - "/en/open_source/"
+  - "/open_source/"
 ---
@@ -5,6 +5,7 @@ draft: false
 weight: 1
 audience: opensource
 aliases:
+  - "/open_source/installation/architecture/"
   - /en/open_source/installation/architecture
 ---
 ![image](images/dd-architecture.png)

@@ -5,6 +5,7 @@ draft: false
 weight: 1
 audience: opensource
 aliases:
+  - "/en/open_source/installation/"
   - /en/open_source/installation/installation
 ---
 ## **Recommended Options**

@@ -5,6 +5,7 @@ draft: false
 weight: 4
 audience: opensource
 aliases:
+  - "/open_source/installation/running-in-production/"
   - /en/open_source/installation/running-in-production
 ---
 ## Production Use (with Docker compose)

@@ -4,4 +4,6 @@ date: 2021-02-02T20:46:29+01:00
 weight: 3
 collapsed: true
 audience: pro
+aliases:
+  - "/en/cloud_management/"
 ---
@@ -56,7 +56,7 @@ Bevor Sie den Prozess abschließen, bestätigen Sie bitte den gewünschten Plan
 
 ## Schritt 6: Überprüfen und Absenden Ihrer Anfrage
 
-Wir bitten Sie, Ihre Anfrage noch einmal zu überprüfen. Nach dem Absenden können von Ihrem Team ohne Unterstützung durch den Support nur noch die Firewall-Regeln geändert werden. Um den Support zu kontaktieren, senden Sie bitte eine E-Mail an [support@defectdojo.com](mailto:support@defectdojo.com) oder folgen Sie den Anweisungen in [diesem Artikel](/en/about_defectdojo/contact_defectdojo_support/).
+Wir bitten Sie, Ihre Anfrage noch einmal zu überprüfen. Nach dem Absenden können von Ihrem Team ohne Unterstützung durch den Support nur noch die Firewall-Regeln geändert werden. Um den Support zu kontaktieren, senden Sie bitte eine E-Mail an [support@defectdojo.com](mailto:support@defectdojo.com) oder folgen Sie den Anweisungen in [diesem Artikel](/help/contact_support/).
 
 ![image](images/request_a_trial_6.png)
 

@@ -55,7 +55,7 @@ Antes de completar el proceso, confirme el plan que desea utilizar junto con la
 
 ## Paso 6: Revise y Envíe su Solicitud
 
-Se le pedirá que revise su solicitud una vez más. Una vez enviada, solo su equipo podrá modificar las Reglas de Firewall sin la asistencia de Soporte. Para contactar a Soporte, envíe un correo electrónico a [support@defectdojo.com](mailto:support@defectdojo.com) o siga las instrucciones en [este artículo](/en/about_defectdojo/contact_defectdojo_support/).
+Se le pedirá que revise su solicitud una vez más. Una vez enviada, solo su equipo podrá modificar las Reglas de Firewall sin la asistencia de Soporte. Para contactar a Soporte, envíe un correo electrónico a [support@defectdojo.com](mailto:support@defectdojo.com) o siga las instrucciones en [este artículo](/help/contact_support/).
 
 ![imagen](images/request_a_trial_6.png)
 

@@ -55,7 +55,7 @@ Avant de finaliser le processus, veuillez confirmer le forfait que vous souhaite
 
 ## Étape 6 : Vérifiez et soumettez votre demande
 
-Nous vous inviterons à relire votre demande une dernière fois. Une fois soumise, seules les règles de pare-feu pourront être modifiées par votre équipe sans l'aide du support. Pour contacter le support, merci d'envoyer un e-mail à [support@defectdojo.com](mailto:support@defectdojo.com) ou de suivre les instructions de [cet article](/en/about_defectdojo/contact_defectdojo_support/).
+Nous vous inviterons à relire votre demande une dernière fois. Une fois soumise, seules les règles de pare-feu pourront être modifiées par votre équipe sans l'aide du support. Pour contacter le support, merci d'envoyer un e-mail à [support@defectdojo.com](mailto:support@defectdojo.com) ou de suivre les instructions de [cet article](/help/contact_support/).
 
 ![image](images/request_a_trial_6.png)