diff --git a/docs/config/_default/hugo.toml b/docs/config/_default/hugo.toml index 0b623542125..c21cf152354 100644 --- a/docs/config/_default/hugo.toml +++ b/docs/config/_default/hugo.toml @@ -1,6 +1,6 @@ title = "DefectDojo Documentation" baseurl = "http://localhost/" -disableAliases = true +disableAliases = false disableHugoGeneratorInject = true disableKinds = ["taxonomy", "term"] enableEmoji = true diff --git a/docs/content/admin/notifications/about_notifications.md b/docs/content/admin/notifications/about_notifications.md index cb27b5e0995..34462e51fc0 100644 --- a/docs/content/admin/notifications/about_notifications.md +++ b/docs/content/admin/notifications/about_notifications.md @@ -1,8 +1,9 @@ --- title: "About Notifications & 🔔 Alerts" description: "Learn about notifications, in-app alerts" +aliases: + - /en/customize_dojo/notifications/about_notifications --- - DefectDojo keeps you up to date in a variety of ways. Notifications can be sent for upcoming Engagements, user Mentions, SLA expiry, and other events in the software. This article contains an overview of notifications at both System\-wide and Personal levels. diff --git a/docs/content/admin/notifications/configure_personal_notifs.md b/docs/content/admin/notifications/configure_personal_notifs.md index 1aed2b41efc..cae2d03b2ef 100644 --- a/docs/content/admin/notifications/configure_personal_notifs.md +++ b/docs/content/admin/notifications/configure_personal_notifs.md @@ -1,8 +1,9 @@ --- title: "Set Personal Notifications" description: "Configure notifications for a personal account" +aliases: + - /en/customize_dojo/notifications/configure_personal_notifs --- - ## Configure Personal notifications Personal Notifications are sent in addition to System\-Wide Notifications, and will apply to any Product, Product Type or other data type that you have access to. Personal Notification preferences only apply to a single user, and can only be set on the account which is configuring them. diff --git a/docs/content/admin/notifications/configure_system_notifs.md b/docs/content/admin/notifications/configure_system_notifs.md index cc09adb3a45..24dcca2c810 100644 --- a/docs/content/admin/notifications/configure_system_notifs.md +++ b/docs/content/admin/notifications/configure_system_notifs.md @@ -1,8 +1,9 @@ --- title: "Set System-Wide Notifications" description: "How to configure Personal & System notifications" +aliases: + - /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). Both an account’s Personal Notifications and the global System Notifications can be configured from the same page: **⚙️Configuration \> Notifications** in the sidebar. diff --git a/docs/content/admin/notifications/email_slack_teams.md b/docs/content/admin/notifications/email_slack_teams.md index 248defa7b70..665fb34ab42 100644 --- a/docs/content/admin/notifications/email_slack_teams.md +++ b/docs/content/admin/notifications/email_slack_teams.md @@ -1,8 +1,9 @@ --- title: "Set up Email, Slack or Teams notifications" description: "Set up Microsoft Teams to receive notifications" +aliases: + - /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.** Notifications can be pushed to Slack or Teams when certain events trigger in DefectDojo. diff --git a/docs/content/admin/user_management/about_perms_and_roles.md b/docs/content/admin/user_management/about_perms_and_roles.md index 05a9da19acd..fdc27288eb9 100644 --- a/docs/content/admin/user_management/about_perms_and_roles.md +++ b/docs/content/admin/user_management/about_perms_and_roles.md @@ -2,8 +2,9 @@ title: "Permissions in DefectDojo" description: "Summary of all DefectDojo permission options, in detail" weight: 2 +aliases: + - /en/customize_dojo/user_management/about_perms_and_roles --- - If you have a team of users working in DefectDojo, it's important to set up Role\-Based Access Control (RBAC) appropriately so that users can only access specific data. Security data is highly sensitive, and DefectDojo's options for access control allow you to be specific about each team member’s access to information. This article is an overview of how permissions in DefectDojo work. If you would prefer to see a detailed breakdown of **each action** that can be controlled by Permissions, see our **[Permissions Chart](../user_permission_chart/)** article. diff --git a/docs/content/admin/user_management/audit_logging.md b/docs/content/admin/user_management/audit_logging.md index eb4a2c8cc63..3ee27209f82 100644 --- a/docs/content/admin/user_management/audit_logging.md +++ b/docs/content/admin/user_management/audit_logging.md @@ -2,8 +2,9 @@ title: "Audit Logs" description: "Access audit logs for DefectDojo objects" weight: 1 +aliases: + - /en/customize_dojo/user_management/audit_logging --- - Audit logs for DefectDojo can be accessed in a few different ways. ## Individual Object Logs diff --git a/docs/content/admin/user_management/configure_sso.md b/docs/content/admin/user_management/configure_sso.md index 67d804d6e7d..864b852b11f 100644 --- a/docs/content/admin/user_management/configure_sso.md +++ b/docs/content/admin/user_management/configure_sso.md @@ -2,8 +2,9 @@ title: "SSO Configuration (OAuth, SAML)" description: "Sign in to DefectDojo using OAuth or SAML login options" pro-feature: true +aliases: + - /en/customize_dojo/user_management/configure_sso --- - Users can connect to DefectDojo with a Username and Password, but if you prefer, you can allow users to authenticate using a Single Sign\-On or SSO method. You can set up DefectDojo to work with your own SAML Identity Provider, but we also support many OAuth methods for authentication: * **[Auth0](./#auth0-setup)** diff --git a/docs/content/admin/user_management/create_user_group.md b/docs/content/admin/user_management/create_user_group.md index 3c68e5cf3a5..1a4f9ed7305 100644 --- a/docs/content/admin/user_management/create_user_group.md +++ b/docs/content/admin/user_management/create_user_group.md @@ -2,8 +2,9 @@ title: "Share permissions: User Groups" description: "Share and maintain permissions for many users" weight: 3 +aliases: + - /en/customize_dojo/user_management/create_user_group --- - If you have a significant number of DefectDojo users, you may want to create one or more **Groups**, in order to set the same Role\-Based Access Control (RBAC) rules for many users simultaneously. Only Superusers can create User Groups. Groups can work in multiple ways: diff --git a/docs/content/admin/user_management/pro_permissions_overhaul.md b/docs/content/admin/user_management/pro_permissions_overhaul.md index ba174ac7eee..6aa71094bb6 100644 --- a/docs/content/admin/user_management/pro_permissions_overhaul.md +++ b/docs/content/admin/user_management/pro_permissions_overhaul.md @@ -3,6 +3,8 @@ title: "Set Permissions in Pro" description: "Overhaul, pro feature" weight: 3 audience: pro +aliases: + - /en/customize_dojo/user_management/pro_permissions_overhaul --- ## Introduction to Permission Types diff --git a/docs/content/admin/user_management/set_user_permissions.md b/docs/content/admin/user_management/set_user_permissions.md index 538cde02d26..d783e79d791 100644 --- a/docs/content/admin/user_management/set_user_permissions.md +++ b/docs/content/admin/user_management/set_user_permissions.md @@ -3,8 +3,9 @@ title: "Set a User's permissions" description: "How to grant Roles & Permissions to a user, as well as superuser status" weight: 2 audience: opensource +aliases: + - /en/customize_dojo/user_management/set_user_permissions --- - ## Introduction to Permission Types Individual users have four different kinds of permission that they can be assigned: diff --git a/docs/content/admin/user_management/user_permission_chart.md b/docs/content/admin/user_management/user_permission_chart.md index b3532e25acf..15a63d1afae 100644 --- a/docs/content/admin/user_management/user_permission_chart.md +++ b/docs/content/admin/user_management/user_permission_chart.md @@ -2,8 +2,9 @@ title: "Action permission charts" description: "All user permissions in detail" weight: 4 +aliases: + - /en/customize_dojo/user_management/user_permission_chart --- - ## Role Permission Chart This chart is intended to list all permissions related to a Product or Product Type, as well as which permissions are available to each role. diff --git a/docs/content/asset_modelling/hierarchy/OS__sla_configuration.md b/docs/content/asset_modelling/hierarchy/OS__sla_configuration.md index 5dc7957adb5..87cf294abae 100644 --- a/docs/content/asset_modelling/hierarchy/OS__sla_configuration.md +++ b/docs/content/asset_modelling/hierarchy/OS__sla_configuration.md @@ -3,8 +3,9 @@ title: "SLA Configuration" description: "Configure Service Level Agreements for different Products" weight: 2 audience: opensource +aliases: + - /en/working_with_findings/sla_configuration --- - Each Product 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. SLA can be set based on either **[Finding Severity](/asset_modelling/hierarchy/product_hierarchy/#findings)** or **[Finding Risk](/asset_modelling/hierarchy/pro__priority_sla/)** (in DefectDojo Pro). diff --git a/docs/content/asset_modelling/hierarchy/OS__source-code-repositories.md b/docs/content/asset_modelling/hierarchy/OS__source-code-repositories.md index dfd25c66c6b..a6c41c90d79 100644 --- a/docs/content/asset_modelling/hierarchy/OS__source-code-repositories.md +++ b/docs/content/asset_modelling/hierarchy/OS__source-code-repositories.md @@ -4,8 +4,9 @@ description: "Integration of repositories to navigate to the location of finding draft: false weight: 5 audience: opensource +aliases: + - /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. ## Setting the repository in the Engagement and Test diff --git a/docs/content/asset_modelling/hierarchy/PRO__assets_organizations.md b/docs/content/asset_modelling/hierarchy/PRO__assets_organizations.md index 65c56d584b5..c1588159dce 100644 --- a/docs/content/asset_modelling/hierarchy/PRO__assets_organizations.md +++ b/docs/content/asset_modelling/hierarchy/PRO__assets_organizations.md @@ -3,8 +3,9 @@ title: "Assets and Organization structure" description: "DefectDojo Pro - Product Hierarchy Overhaul" audience: pro weight: 1 +aliases: + - /en/working_with_findings/organizing_engagements_tests/pro_assets_organizations --- - DefectDojo Pro is extending the Product/Product Type object classes to provide greater flexibility with the data model. Currently, this feature is in Beta. Pro users who are interested in opting in can do so by emailing [support@defectdojo.com](mailto:support@defectdojo.com). diff --git a/docs/content/asset_modelling/hierarchy/PRO__priority_sla.md b/docs/content/asset_modelling/hierarchy/PRO__priority_sla.md index 75abb100e54..5baf8753d9a 100644 --- a/docs/content/asset_modelling/hierarchy/PRO__priority_sla.md +++ b/docs/content/asset_modelling/hierarchy/PRO__priority_sla.md @@ -3,6 +3,9 @@ title: "Assign Priority, Risk and SLAs" description: "How DefectDojo ranks your Findings" weight: 1 audience: pro +aliases: + - /en/working_with_findings/finding_priority + - /en/working_with_findings/priority_adjustments --- ![image](images/pro_finding_priority.png) diff --git a/docs/content/asset_modelling/hierarchy/product_health_grade.md b/docs/content/asset_modelling/hierarchy/product_health_grade.md index 30e883f5e3c..53961251fd3 100644 --- a/docs/content/asset_modelling/hierarchy/product_health_grade.md +++ b/docs/content/asset_modelling/hierarchy/product_health_grade.md @@ -1,8 +1,9 @@ --- title: "Product Health Grade" description: "How DefectDojo calculates a Product Health Grade" +aliases: + - /en/working_with_findings/organizing_engagements_tests/product_health_grade --- - DefectDojo can calculate a grade for your Products based on the amount of Findings contained within. Grades are ranked from A \- F. Note that only Active \& Verified Findings contribute to a Product Grade \- unverified Findings will not have an impact. diff --git a/docs/content/asset_modelling/hierarchy/product_hierarchy.md b/docs/content/asset_modelling/hierarchy/product_hierarchy.md index 77458d98df1..36e0149b34a 100644 --- a/docs/content/asset_modelling/hierarchy/product_hierarchy.md +++ b/docs/content/asset_modelling/hierarchy/product_hierarchy.md @@ -3,8 +3,9 @@ title: "Product Hierarchy: Overview" description: "Understand Product Types, Products, Engagements, Tests and Findings" weight: 1 audience: opensource +aliases: + - /en/working_with_findings/organizing_engagements_tests/product_hierarchy --- - DefectDojo uses five main data classes to organize your work: **Product Types, Products**, **Engagements**, **Tests**, and **Findings**. DefectDojo is made to be flexible to conform to your team, rather than making your team conform to the tool. You'll be able to design a robust, adaptable workspace once you understand how these data classes can be used to organize your work. diff --git a/docs/content/asset_modelling/tags/PRO__tagging_objects copy.md b/docs/content/asset_modelling/tags/PRO__tagging_objects copy.md index cc729ee5141..bb9e69720b5 100644 --- a/docs/content/asset_modelling/tags/PRO__tagging_objects copy.md +++ b/docs/content/asset_modelling/tags/PRO__tagging_objects copy.md @@ -5,8 +5,9 @@ draft: false weight: 2 exclude_search: false audience: pro +aliases: + - /en/working_with_findings/organizing_engagements_tests/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 Product Type, Products, Engagements or Findings across the data model. In DefectDojo, tags are a first class citizen and are recognized as the facilitators diff --git a/docs/content/automation/api/api-v2-docs.md b/docs/content/automation/api/api-v2-docs.md index df8ba8b6d70..1d55a413a7b 100644 --- a/docs/content/automation/api/api-v2-docs.md +++ b/docs/content/automation/api/api-v2-docs.md @@ -3,8 +3,9 @@ title: "DefectDojo API v2" description: "DefectDojo's API lets you automate tasks, e.g. uploading scan reports in CI/CD pipelines." draft: false weight: 2 +aliases: + - /en/api/api-v2-docs --- - DefectDojo\'s API is created using [Django Rest Framework](http://www.django-rest-framework.org/). The documentation of each endpoint is available within each DefectDojo installation at diff --git a/docs/content/automation/rules_engine/about.md b/docs/content/automation/rules_engine/about.md index 86700c3853c..150d889ae04 100644 --- a/docs/content/automation/rules_engine/about.md +++ b/docs/content/automation/rules_engine/about.md @@ -3,8 +3,9 @@ title: "Rules Engine Automation" description: "Working with Rules Engine Automation" weight: 1 audience: pro +aliases: + - /en/customize_dojo/rules_engine --- - Note: Rules Engine is a DefectDojo Pro-only feature. DefectDojo's Rules Engine allows you to build custom workflows and bulk actions to handle Findings and other objects. Rules Engine allows you to build automated actions that are triggered when an object matches a Rule. diff --git a/docs/content/get_started/about/PRO__new_user_checklist.md b/docs/content/get_started/about/PRO__new_user_checklist.md index bb321882b24..3b6e7b2726d 100644 --- a/docs/content/get_started/about/PRO__new_user_checklist.md +++ b/docs/content/get_started/about/PRO__new_user_checklist.md @@ -4,6 +4,8 @@ description: "Get Started With DefectDojo" draft: "false" weight: 3 audience: pro +aliases: + - /en/about_defectdojo/new_user_checklist --- The essence of DefectDojo is to import security data, organize it, and present it to the folks who need to know. Here's a quick reference you can use to ensure successful implementation, from a blank canvas to a fully functional app. diff --git a/docs/content/get_started/about/about_defectdojo.md b/docs/content/get_started/about/about_defectdojo.md index d86ae4c646a..5e9fb0c4bc6 100644 --- a/docs/content/get_started/about/about_defectdojo.md +++ b/docs/content/get_started/about/about_defectdojo.md @@ -4,8 +4,9 @@ date: 2021-02-02T20:46:29+01:00 draft: false type: docs weight: 1 +aliases: + - /en/about_defectdojo/about_docs --- - ![image](images/dashboard.png) diff --git a/docs/content/get_started/about/faq.md b/docs/content/get_started/about/faq.md index 4f668222763..9132248fd89 100644 --- a/docs/content/get_started/about/faq.md +++ b/docs/content/get_started/about/faq.md @@ -4,8 +4,9 @@ description: "DefectDojo FAQ" draft: "false" weight: 2 chapter: true +aliases: + - /en/about_defectdojo/faq --- - Here are some frequently asked questions about working with DefectDojo - both in DefectDojo Pro or DefectDojo OS. ## General Questions diff --git a/docs/content/get_started/about/ui_pro_vs_os.md b/docs/content/get_started/about/ui_pro_vs_os.md index 93bb7204886..e01fa48fbef 100644 --- a/docs/content/get_started/about/ui_pro_vs_os.md +++ b/docs/content/get_started/about/ui_pro_vs_os.md @@ -4,8 +4,9 @@ description: "Working with different UIs in DefectDojo" draft: "false" weight: 5 audience: pro +aliases: + - /en/about_defectdojo/ui_pro_vs_os --- - In late 2023, DefectDojo Inc. released a new UI for DefectDojo Pro, which is now the default UI for this edition. The Pro UI brings the following enhancements to DefectDojo: diff --git a/docs/content/get_started/common_use_cases/common_use_cases.md b/docs/content/get_started/common_use_cases/common_use_cases.md index de2d3c143e5..0565035ddfd 100644 --- a/docs/content/get_started/common_use_cases/common_use_cases.md +++ b/docs/content/get_started/common_use_cases/common_use_cases.md @@ -4,8 +4,9 @@ description: "Use Cases and examples" draft: "false" weight: 2 chapter: true +aliases: + - /en/about_defectdojo/examples_of_use --- - This article is based on DefectDojo Inc's February 2025 Office Hours: "Tackling Common Use Cases". diff --git a/docs/content/get_started/open_source/architecture.md b/docs/content/get_started/open_source/architecture.md index e34e29d089c..971291a9afc 100644 --- a/docs/content/get_started/open_source/architecture.md +++ b/docs/content/get_started/open_source/architecture.md @@ -4,8 +4,9 @@ description: "The DefectDojo platform consists of several components that work t draft: false weight: 1 audience: opensource +aliases: + - /en/open_source/installation/architecture --- - ![image](images/dd-architecture.png) ## NGINX diff --git a/docs/content/get_started/open_source/configuration.md b/docs/content/get_started/open_source/configuration.md index e97709392e4..df7bcb14e63 100644 --- a/docs/content/get_started/open_source/configuration.md +++ b/docs/content/get_started/open_source/configuration.md @@ -4,8 +4,9 @@ description: "DefectDojo is highly configurable." draft: false weight: 2 audience: opensource +aliases: + - /en/open_source/installation/configuration --- - ## dojo/settings/settings.dist.py The main settings are stored in [`dojo/settings/settings.dist.py`](https://github.com/DefectDojo/django-DefectDojo/blob/master/dojo/settings/settings.dist.py). It is great to use this file as a reference for what can be configured, but it shouldn\'t be edited directly, because changes will be overwritten when updating DefectDojo. There are several methods to change the default settings: diff --git a/docs/content/get_started/open_source/installation.md b/docs/content/get_started/open_source/installation.md index 105ac4f119a..0515e41419b 100644 --- a/docs/content/get_started/open_source/installation.md +++ b/docs/content/get_started/open_source/installation.md @@ -4,8 +4,9 @@ description: "DefectDojo supports various installation options." draft: false weight: 1 audience: opensource +aliases: + - /en/open_source/installation/installation --- - ## **Recommended Options** --- diff --git a/docs/content/get_started/open_source/running-in-production.md b/docs/content/get_started/open_source/running-in-production.md index ef96670d11b..e22e9b69516 100644 --- a/docs/content/get_started/open_source/running-in-production.md +++ b/docs/content/get_started/open_source/running-in-production.md @@ -4,8 +4,9 @@ description: "For use in Production environments, performance tweaks and backups draft: false weight: 4 audience: opensource +aliases: + - /en/open_source/installation/running-in-production --- - ## Production Use (with Docker compose) The docker-compose.yml file in this repository is fully functional to evaluate DefectDojo in your local environment. diff --git a/docs/content/get_started/pro/cloud/additional-cloud-instance.md b/docs/content/get_started/pro/cloud/additional-cloud-instance.md index 806fc9cb9b2..9921fede8ee 100644 --- a/docs/content/get_started/pro/cloud/additional-cloud-instance.md +++ b/docs/content/get_started/pro/cloud/additional-cloud-instance.md @@ -3,8 +3,9 @@ title: "Set up an additional Cloud instance" description: "Add a test, dev, or other DefectDojo instance to your account" weight: 3 audience: pro +aliases: + - /en/cloud_management/additional-cloud-instance --- - The process for adding a second Cloud instance is more or less the same as adding your first instance. This guide assumes you've already set up your initial DefectDojo server, and have an agreement with our Sales team to add another instance. If you have not already requested an additional Cloud instance, please contact [info@defectdojo.com](mailto:info@defectdojo.com) before proceeding. diff --git a/docs/content/get_started/pro/cloud/connectivity-troubleshooting.md b/docs/content/get_started/pro/cloud/connectivity-troubleshooting.md index ed38ce94939..384640f3893 100644 --- a/docs/content/get_started/pro/cloud/connectivity-troubleshooting.md +++ b/docs/content/get_started/pro/cloud/connectivity-troubleshooting.md @@ -3,8 +3,9 @@ title: "Connectivity Troubleshooting" description: "Reconnect to your DefectDojo Instance" weight: 2 audience: pro +aliases: + - /en/cloud_management/connectivity-troubleshooting --- - If you have difficulty accessing your DefectDojo instance, here are some steps you can follow to get reconnected: ## I can access the site, but I can't log in diff --git a/docs/content/get_started/pro/cloud/using-cloud-manager.md b/docs/content/get_started/pro/cloud/using-cloud-manager.md index 73fe4eca735..7eef9f8802b 100644 --- a/docs/content/get_started/pro/cloud/using-cloud-manager.md +++ b/docs/content/get_started/pro/cloud/using-cloud-manager.md @@ -4,8 +4,9 @@ description: "Manage your subscription and account settings" weight: 1 collapsed: true audience: pro +aliases: + - /en/cloud_management/using-cloud-manager --- - Logging into DefectDojo's Cloud Manager allows you to configure your account settings and manage your subscription with DefectDojo Cloud. ## **New Subscription** diff --git a/docs/content/get_started/pro/pro_features.md b/docs/content/get_started/pro/pro_features.md index afdacfb3e71..9d5d7600545 100644 --- a/docs/content/get_started/pro/pro_features.md +++ b/docs/content/get_started/pro/pro_features.md @@ -6,8 +6,9 @@ weight: 4 chapter: true exclude_search: true audience: pro +aliases: + - /en/about_defectdojo/pro_features --- - Here is a list of DefectDojo Pro’s many additional features, along with links to documentation to see them in action: ## Improved UX diff --git a/docs/content/help/contact_sales.md b/docs/content/help/contact_sales.md index 310b262528e..687b6d29ecc 100644 --- a/docs/content/help/contact_sales.md +++ b/docs/content/help/contact_sales.md @@ -4,8 +4,9 @@ description: "How to request and work with a trial of DefectDojo Cloud" draft: "false" weight: 6 pro-feature: true +aliases: + - /en/about_defectdojo/request_a_trial --- - If your team requires an on-premise DefectDojo installation, please connect with our Sales team by emailing → [hello@defectdojo.com](mailto:hello@defectdojo.com) . This trial setup process only applies to DefectDojo Cloud users. All DefectDojo plans include a free 2-week trial, which you can use to evaluate our software. DefectDojo Trial instances are fully-featured and can be immediately converted into paid instances by our team; no need to set everything up again, or reupload any data when your trial period ends. diff --git a/docs/content/help/contact_support.md b/docs/content/help/contact_support.md index 02d8d8c8d9d..89af196c0c4 100644 --- a/docs/content/help/contact_support.md +++ b/docs/content/help/contact_support.md @@ -4,8 +4,9 @@ description: "For Pro users: support@defectdojo.com + other options" draft: "false" pro-feature: true weight: 7 +aliases: + - /en/about_defectdojo/contact_defectdojo_support --- - Need help with DefectDojo? Here are some ways to get assistance. ## Open-Source Support diff --git a/docs/content/import_data/import_intro/comparison.md b/docs/content/import_data/import_intro/comparison.md index 3135fc227e5..3a1cdb2d042 100644 --- a/docs/content/import_data/import_intro/comparison.md +++ b/docs/content/import_data/import_intro/comparison.md @@ -2,8 +2,9 @@ title: "Import Method Comparison" description: "Learn how to import data manually, through the API, or via a connector" weight: 1 +aliases: + - /en/connecting_your_tools/import_intro --- - One of the things we understand at DefectDojo is that every company’s security needs are completely different. There is no one-size-fits-all approach. As your organization changes, having a flexible approach is key, and DefectDojo allows you to connect your security tools in a flexible way to match those changes. ## Scan Upload Methods diff --git a/docs/content/import_data/import_intro/import_vs_reimport.md b/docs/content/import_data/import_intro/import_vs_reimport.md index c73e84c86dd..8b21ce9d2a2 100644 --- a/docs/content/import_data/import_intro/import_vs_reimport.md +++ b/docs/content/import_data/import_intro/import_vs_reimport.md @@ -2,8 +2,9 @@ title: "Import vs Reimport" description: "Learn how to import data manually, through the API, or via a connector" weight: 2 +aliases: + - /en/connecting_your_tools/import_scan_files/using_reimport --- - When a Test is created in DefectDojo (either in advance or by importing a scan file), the Test can be extended with new Finding data. For example, let’s say you have a CI/CD pipeline, which is designed to send a new report to DefectDojo every day. Rather than create a new Test or Engagement for each ‘run’ of the pipeline, you could have each report flow into the same Test using **Reimport**. diff --git a/docs/content/import_data/import_scan_files/PRO__import_scan_ui.md b/docs/content/import_data/import_scan_files/PRO__import_scan_ui.md index 741f850c6fa..bf4058ecb17 100644 --- a/docs/content/import_data/import_scan_files/PRO__import_scan_ui.md +++ b/docs/content/import_data/import_scan_files/PRO__import_scan_ui.md @@ -3,8 +3,9 @@ title: "Add Findings form" description: "" weight: 1 audience: pro +aliases: + - /en/connecting_your_tools/import_scan_files/import_scan_ui --- - If you have a brand new DefectDojo instance, the Import Scan Form is a logical first step to learn the software and set up your environment. From this form, you upload a scan file from a supported tool, which will create Findings to represent those vulnerabilities. While filling out the form, you can decide whether to: * Store these Findings under an existing Product Type / Product / Engagement **or** diff --git a/docs/content/import_data/import_scan_files/api_pipeline_modelling.md b/docs/content/import_data/import_scan_files/api_pipeline_modelling.md index dd8e01ed410..f415727df17 100644 --- a/docs/content/import_data/import_scan_files/api_pipeline_modelling.md +++ b/docs/content/import_data/import_scan_files/api_pipeline_modelling.md @@ -1,8 +1,9 @@ --- title: "Import from API" description: "" +aliases: + - /en/connecting_your_tools/import_scan_files/api_pipeline_modelling --- - DefectDojo’s API allows for robust pipeline solutions, which automatically ingest new scans to your instance. Automation like this can take a few different forms: * A daily import which scans your environment on a daily basis, and then imports the results of the scan to DefectDojo (similar to our **Connectors** feature) diff --git a/docs/content/import_data/pro/connectors/about_connectors.md b/docs/content/import_data/pro/connectors/about_connectors.md index b1502a2c714..f3ddf75b540 100644 --- a/docs/content/import_data/pro/connectors/about_connectors.md +++ b/docs/content/import_data/pro/connectors/about_connectors.md @@ -15,8 +15,9 @@ seo: canonical: "" # custom canonical URL (optional) robots: "" # custom robot tags (optional) pro-feature: true +aliases: + - /en/connecting_your_tools/connectors/about_connectors --- - Note: Connectors are a DefectDojo Pro-only feature. DefectDojo allows users to build sophisticated API integrations, and gives users full control over how their vulnerability data is organized. diff --git a/docs/content/import_data/pro/connectors/add_edit_connectors.md b/docs/content/import_data/pro/connectors/add_edit_connectors.md index 1d067e59a51..78f9d3a6263 100644 --- a/docs/content/import_data/pro/connectors/add_edit_connectors.md +++ b/docs/content/import_data/pro/connectors/add_edit_connectors.md @@ -1,8 +1,9 @@ --- title: "Add or Edit a Connector" description: "Connect to a supported security tool" +aliases: + - /en/connecting_your_tools/connectors/add_edit_connectors --- - Note: Connectors are a DefectDojo Pro-only feature. The process for adding and configuring a connector is similar, regardless of the tool you’re trying to connect. However, certain tools may require you to create API keys or complete additional steps. diff --git a/docs/content/import_data/pro/connectors/connectors_tool_reference.md b/docs/content/import_data/pro/connectors/connectors_tool_reference.md index 67c6b892e0c..89198061147 100644 --- a/docs/content/import_data/pro/connectors/connectors_tool_reference.md +++ b/docs/content/import_data/pro/connectors/connectors_tool_reference.md @@ -1,8 +1,9 @@ --- title: "Tool-Specific Connector Setup" description: "Our list of supported Connector tools, and how to set them up with DefectDojo" +aliases: + - /en/connecting_your_tools/connectors/connectors_tool_reference --- - Note: Connectors are a DefectDojo Pro-only feature. When setting up a Connector for a supported tool, you'll need to give DefectDojo specific information related to the tool's API. At a base level, you'll need: diff --git a/docs/content/import_data/pro/connectors/manage_operations.md b/docs/content/import_data/pro/connectors/manage_operations.md index a5652aed310..c965fad55ea 100644 --- a/docs/content/import_data/pro/connectors/manage_operations.md +++ b/docs/content/import_data/pro/connectors/manage_operations.md @@ -1,8 +1,9 @@ --- title: "Managing Operations" description: "Check the status of your Connector's Discover & Sync Operations" +aliases: + - /en/connecting_your_tools/connectors/manage_operations --- - Note: Connectors are a DefectDojo Pro-only feature. Once an API connector is set up, it will run two Operations on a recurring basis: diff --git a/docs/content/import_data/pro/connectors/manage_records.md b/docs/content/import_data/pro/connectors/manage_records.md index 8da74053483..2b605ee3cb2 100644 --- a/docs/content/import_data/pro/connectors/manage_records.md +++ b/docs/content/import_data/pro/connectors/manage_records.md @@ -1,8 +1,9 @@ --- title: "Managing Records" description: "Direct the flow of data from your tool into DefectDojo" +aliases: + - /en/connecting_your_tools/connectors/manage_records --- - Note: Connectors are a DefectDojo Pro-only feature. Once you have run your first Discover operation, you should see a list of Mapped or Unmapped records on the **Manage Records and Operations** page. diff --git a/docs/content/import_data/pro/specialized_import/external_tools.md b/docs/content/import_data/pro/specialized_import/external_tools.md index 625d12e5070..78b012193db 100644 --- a/docs/content/import_data/pro/specialized_import/external_tools.md +++ b/docs/content/import_data/pro/specialized_import/external_tools.md @@ -4,8 +4,9 @@ description: "Import files to DefectDojo from the command line" draft: false weight: 2 audience: pro +aliases: + - /en/connecting_your_tools/external_tools --- - Note: The following external tools are DefectDojo Pro-only features. These binaries will not work unless they are connected to an instance with a DefectDojo Pro license. ## About External Tools diff --git a/docs/content/import_data/pro/specialized_import/smart_upload.md b/docs/content/import_data/pro/specialized_import/smart_upload.md index 97e6201ccb2..42061ab4269 100644 --- a/docs/content/import_data/pro/specialized_import/smart_upload.md +++ b/docs/content/import_data/pro/specialized_import/smart_upload.md @@ -3,8 +3,9 @@ title: "Infrastructure scans / Smart Upload" description: "Automatically route incoming Findings to the correct Product" weight: 3 audience: pro +aliases: + - /en/connecting_your_tools/import_scan_files/smart_upload --- - Note: Smart Upload is only available in DefectDojo Pro. Smart upload is a specialized importer that ingests reports from **infrastructure scanning tools**, including: diff --git a/docs/content/import_data/pro/specialized_import/universal_parser.md b/docs/content/import_data/pro/specialized_import/universal_parser.md index 24043d5de20..e5abd41bff0 100644 --- a/docs/content/import_data/pro/specialized_import/universal_parser.md +++ b/docs/content/import_data/pro/specialized_import/universal_parser.md @@ -4,8 +4,9 @@ description: "" draft: "false" weight: 1 audience: pro +aliases: + - /en/connecting_your_tools/universal_parser --- - Note: The Universal Parser is only available in DefectDojo Pro. The Universal Parser is currently in Beta. See our [announcement presentation](https://community.defectdojo.com/universalparser) for more information. diff --git a/docs/content/issue_tracking/jira/jira_guide.md b/docs/content/issue_tracking/jira/jira_guide.md index baeaca65094..9fcd50530be 100644 --- a/docs/content/issue_tracking/jira/jira_guide.md +++ b/docs/content/issue_tracking/jira/jira_guide.md @@ -2,8 +2,9 @@ title: "📋 Jira Integration Guide" description: "Work with the Jira integration" weight: 1 +aliases: + - /en/share_your_findings/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: * The AppSec team can selectively push Findings to a Jira Space used by developers, so that issue remediation can be appropriately prioritized alongside regular development. Developers on this board don't need to access DefectDojo - they can keep all their work in one place. diff --git a/docs/content/issue_tracking/jira/troubleshooting_jira.md b/docs/content/issue_tracking/jira/troubleshooting_jira.md index 2b671b9e12d..131bc4fbbe8 100644 --- a/docs/content/issue_tracking/jira/troubleshooting_jira.md +++ b/docs/content/issue_tracking/jira/troubleshooting_jira.md @@ -2,6 +2,8 @@ title: "Troubleshooting Jira errors" description: "Fixing issues with a Jira integration" weight: 2 +aliases: + - /en/share_your_findings/troubleshooting_jira/ --- Here are some common issues with the Jira integration, and ways to address them. diff --git a/docs/content/issue_tracking/pro_integration/integrations.md b/docs/content/issue_tracking/pro_integration/integrations.md index 28244d9bfa2..a52b35848fb 100644 --- a/docs/content/issue_tracking/pro_integration/integrations.md +++ b/docs/content/issue_tracking/pro_integration/integrations.md @@ -2,8 +2,9 @@ title: "Pro Integrations" weight: 1 audience: pro +aliases: + - /en/share_your_findings/integrations --- - DefectDojo Pro's Integrations let you push your Findings and Finding Groups to ticket tracking systems to easily integrate security remediation with your teams existing development workflow. Supported Integrations: diff --git a/docs/content/issue_tracking/pro_integration/integrations_toolreference.md b/docs/content/issue_tracking/pro_integration/integrations_toolreference.md index da74c650acd..1ed3c82bc67 100644 --- a/docs/content/issue_tracking/pro_integration/integrations_toolreference.md +++ b/docs/content/issue_tracking/pro_integration/integrations_toolreference.md @@ -3,8 +3,9 @@ title: "Integrators Tool Reference" description: "Detailed setup guides for Integrators" weight: 1 audience: pro +aliases: + - /en/share_your_findings/integrations_toolreference --- - Here are specific instructions detailing how to set up a DefectDojo Integration with a third party Issue Tracker. ## Azure DevOps Boards diff --git a/docs/content/metrics_reports/ai/mcp_server_pro.md b/docs/content/metrics_reports/ai/mcp_server_pro.md index fde352f9b5f..97516f19616 100644 --- a/docs/content/metrics_reports/ai/mcp_server_pro.md +++ b/docs/content/metrics_reports/ai/mcp_server_pro.md @@ -3,8 +3,9 @@ title: "MCP Server (Pro)" description: "DefectDojo's MCP Server allows you to use LLMs with DefectDojo Pro" draft: false weight: 2 +aliases: + - /en/ai/mcp_server_pro --- - Note: AI features are a DefectDojo Pro-only feature. The DefectDojo Model Context Protocol (MCP) Server enables Large Language Models (LLMs) to intelligently interact with DefectDojo's vulnerability management data. Unlike traditional API integrations that simply transfer data, the MCP server provides structured context and semantic meaning that enables AI assistants to perform sophisticated security analysis and generate actionable insights. diff --git a/docs/content/metrics_reports/dashboards/Introduction_dashboard.md b/docs/content/metrics_reports/dashboards/Introduction_dashboard.md index 62ed14c5421..783e1e57df9 100644 --- a/docs/content/metrics_reports/dashboards/Introduction_dashboard.md +++ b/docs/content/metrics_reports/dashboards/Introduction_dashboard.md @@ -2,8 +2,10 @@ title: "DefectDojo Main Dashboard" description: "Working with the front page of DefectDojo" weight: 1 +aliases: + - /en/customize_dojo/dashboards/Introduction_dashboard + - /en/customize_dojo/dashboards/pro_dashboards --- - The Dashboard is likely the first page you'll see when you open DefectDojo. It summarizes your team’s performance, and provides tracking tools to monitor specific areas of your vulnerability tracking environment. ![image](images/Introduction_to_Dashboard_Features.png) diff --git a/docs/content/metrics_reports/dashboards/about_custom_dashboard_tiles.md b/docs/content/metrics_reports/dashboards/about_custom_dashboard_tiles.md index 8dd7e0fa3b0..44750888055 100644 --- a/docs/content/metrics_reports/dashboards/about_custom_dashboard_tiles.md +++ b/docs/content/metrics_reports/dashboards/about_custom_dashboard_tiles.md @@ -2,8 +2,9 @@ title: "Custom Dashboard Tiles" description: "How to make Dashboard Tiles work for you, with examples" weight: 2 +aliases: + - /en/customize_dojo/dashboards/about_custom_dashboard_tiles --- - Dashboard Tiles are customizable sets of filters for your DefectDojo instance, which can be added to your 🏠 **Home** dashboard. Tiles are designed to provide relevant information and speed up navigation within DefectDojo. ![image](images/About_Custom_Dashboard_Tiles.png) diff --git a/docs/content/metrics_reports/reports/using_the_report_builder.md b/docs/content/metrics_reports/reports/using_the_report_builder.md index 70982a0dafb..b7f2c905f4e 100644 --- a/docs/content/metrics_reports/reports/using_the_report_builder.md +++ b/docs/content/metrics_reports/reports/using_the_report_builder.md @@ -2,8 +2,9 @@ title: "Using the Report Builder" description: "Build and publish custom reports for external audiences, or your own records" weight: 1 +aliases: + - /en/share_your_findings/pro_reports/using_the_report_builder --- - DefectDojo allows you to create Custom Reports for external audiences, which summarize the Findings or Endpoints that you wish to report on. Custom Reports can include branding and boilerplate text, and can also be used as **[Templates](https://docs.defectdojo.com/en/pro_reports/working-with-generated-reports/)** for future reports. ## Opening the Report Builder diff --git a/docs/content/metrics_reports/reports/working_with_generated_reports.md b/docs/content/metrics_reports/reports/working_with_generated_reports.md index a63f07cf01f..74f211f41a8 100644 --- a/docs/content/metrics_reports/reports/working_with_generated_reports.md +++ b/docs/content/metrics_reports/reports/working_with_generated_reports.md @@ -2,8 +2,9 @@ title: "Templates and Historical Reports" description: "Use a report as a template, or re-run an existing report with updated data" weight: 2 +aliases: + - /en/share_your_findings/pro_reports/working_with_generated_reports --- - Once you have created one or more **Reports** in DefectDojo you can take further actions, including: * Using a report as a template for subsequent reports diff --git a/docs/content/navigation/PRO__filter_index.md b/docs/content/navigation/PRO__filter_index.md index 168f25bb841..92f9b44c7ac 100644 --- a/docs/content/navigation/PRO__filter_index.md +++ b/docs/content/navigation/PRO__filter_index.md @@ -2,9 +2,9 @@ title: "Filter Index" description: "Reference for all filters in DefectDojo" weight: 5 - +aliases: + - /en/working_with_findings/organizing_engagements_tests/filter_index --- - **Note: Currently this article only covers Finding Filters available in the DefectDojo Pro UI, but this article will be expanded in the future to govern more object types, along with Open-Source filters.** Here is a list of filters that can be applied in the DefectDojo Pro UI to sort lists of Findings. DefectDojo Filters can be used to assist with navigating through lists of Objects, creating custom [Dashboard Tiles](/metrics_reports/dashboards/about_custom_dashboard_tiles/), or creating automation via [Rules Engine](/automation/rules_engine/about). diff --git a/docs/content/open_source/archived_docs/burp-plugin.md b/docs/content/open_source/archived_docs/burp-plugin.md index 874444b17da..5d8cf1f41a6 100644 --- a/docs/content/open_source/archived_docs/burp-plugin.md +++ b/docs/content/open_source/archived_docs/burp-plugin.md @@ -4,8 +4,9 @@ description: "Export findings directly from Burp to DefectDojo." draft: false weight: 9 exclude_search: true +aliases: + - /en/open_source/archived_docs/burp-plugin --- - **Please note: The DefectDojo Burp Plugin has been sunset and is no longer a supported feature.** Burp is still a supported tool, and all the results from it can be imported into DefectDojo. Burp can produce XML reports and these can be uploaded to DefectDojo using the graphical user interface or the API. Our documentation at https://documentation.defectdojo.com/integrations/parsers/file/burp/ describes this usage. diff --git a/docs/content/open_source/archived_docs/google-sheets-sync.md b/docs/content/open_source/archived_docs/google-sheets-sync.md index 8af6772e17d..7bb238b6ed2 100644 --- a/docs/content/open_source/archived_docs/google-sheets-sync.md +++ b/docs/content/open_source/archived_docs/google-sheets-sync.md @@ -4,8 +4,9 @@ description: "Export finding details to Google Sheets and upload changes from Go draft: false weight: 8 exclude_search: true +aliases: + - /en/open_source/archived_docs/google-sheets-sync --- - **Please note - the Google Sheets feature has been removed in DefectDojo version 2.21.0 - these documents are for reference only.** With the Google Sheets sync feature, DefectDojo allow the users to diff --git a/docs/content/open_source/archived_docs/usage/features.md b/docs/content/open_source/archived_docs/usage/features.md index f03d23100cb..0635177a8d3 100644 --- a/docs/content/open_source/archived_docs/usage/features.md +++ b/docs/content/open_source/archived_docs/usage/features.md @@ -4,8 +4,9 @@ description: "Various features help manage vulnerabilities." draft: false weight: 2 exclude_search: false +aliases: + - /en/open_source/archived_docs/usage/features --- - ## Tags In DefectDojo, tags are a first class citizen and are recognized as the facilitators diff --git a/docs/content/open_source/archived_docs/usage/questionnaires.md b/docs/content/open_source/archived_docs/usage/questionnaires.md index 36cc7c28501..bf39e369aa7 100644 --- a/docs/content/open_source/archived_docs/usage/questionnaires.md +++ b/docs/content/open_source/archived_docs/usage/questionnaires.md @@ -3,8 +3,9 @@ title: "Questionnaires" description: "Collect information from people internal or external to DefectDojo." weight: 3 draft: false +aliases: + - /en/open_source/archived_docs/usage/questionnaires --- - ## Questionnaires Questionnaires provide a means for collecting information from developers and respective stakeholders. DefectDojo includes functionality to create new questionnaires with custom questions, open questionnaires to receive responses for certain time periods from insiders or outsiders, and connect questionnaires with new or existing engagements. diff --git a/docs/content/open_source/contributing/branching-model.md b/docs/content/open_source/contributing/branching-model.md index 9fc0b817532..58dcf75a14c 100644 --- a/docs/content/open_source/contributing/branching-model.md +++ b/docs/content/open_source/contributing/branching-model.md @@ -3,8 +3,9 @@ title: "Open-Source Branching & Releases" description: "How we create releases" draft: false weight: 3 +aliases: + - /en/open_source/contributing/branching-model --- - ## Regular releases The DefectDojo team aims to maintain the following cadence: diff --git a/docs/content/open_source/contributing/documentation.md b/docs/content/open_source/contributing/documentation.md index fff04de6d29..aa99d3c65e7 100644 --- a/docs/content/open_source/contributing/documentation.md +++ b/docs/content/open_source/contributing/documentation.md @@ -3,8 +3,9 @@ title: "Amend Documentation" description: "How to amend the documentation" draft: false weight: 2 +aliases: + - /en/open_source/contributing/documentation --- - The documentation is built with [Hugo](https://gohugo.io/) and uses the theme [Docsy](https://www.docsy.dev). Static files for the webside are build with github actions and are publish in the gh-pages branch. diff --git a/docs/content/open_source/contributing/how-to-write-a-parser.md b/docs/content/open_source/contributing/how-to-write-a-parser.md index bd00c8abff5..c47e3cd8c41 100644 --- a/docs/content/open_source/contributing/how-to-write-a-parser.md +++ b/docs/content/open_source/contributing/how-to-write-a-parser.md @@ -3,8 +3,9 @@ title: "Contribute to Parsers" description: "How to contribute to parsers" draft: false weight: 1 +aliases: + - /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. ## Pre-requisites diff --git a/docs/content/open_source/contributing/parser-documentation-template.md b/docs/content/open_source/contributing/parser-documentation-template.md index 943da145349..ed3bfc0dce9 100644 --- a/docs/content/open_source/contributing/parser-documentation-template.md +++ b/docs/content/open_source/contributing/parser-documentation-template.md @@ -2,8 +2,9 @@ title: "Parser Documentation Template" toc_hide: true weight: 1 +aliases: + - /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. * Copy this .md file and add it to `/docs/content/supported_tools/file` in the GitHub repository. diff --git a/docs/content/open_source/exporting.md b/docs/content/open_source/exporting.md index b52f12989c3..c87163e0199 100644 --- a/docs/content/open_source/exporting.md +++ b/docs/content/open_source/exporting.md @@ -3,8 +3,9 @@ title: "Export Findings" description: "DefectDojo has the ability to export findings." draft: false weight: 12 +aliases: + - /en/open_source/exporting --- - ## Export Findings Pages that show a list of findings or a list of engagements have a CSV and Excel Export functionality in the top right dropdown menu. diff --git a/docs/content/open_source/languages.md b/docs/content/open_source/languages.md index 47929b7bfdc..c96f08a4381 100644 --- a/docs/content/open_source/languages.md +++ b/docs/content/open_source/languages.md @@ -3,8 +3,9 @@ title: "Languages and lines of code (Open-Source)" description: "You can import an analysis of languages used in a project, including lines of code." draft: false weight: 10 +aliases: + - /en/open_source/languages --- - ## Import of languages for a project You can import JSON reports generated by the [cloc tool](https://github.com/AlDanial/cloc) via the API: diff --git a/docs/content/open_source/ldap-authentication.md b/docs/content/open_source/ldap-authentication.md index e8db98ff232..d1d8f64a4cb 100644 --- a/docs/content/open_source/ldap-authentication.md +++ b/docs/content/open_source/ldap-authentication.md @@ -3,8 +3,9 @@ title: "Authentication via LDAP (Open-Source)" description: "Authenticate users using LDAP" draft: false weight: 4 +aliases: + - /en/open_source/ldap-authentication --- - ## LDAP Authentication Out of the box DefectDojo does not support LDAP authentication. diff --git a/docs/content/open_source/notification_webhooks/engagement_added.md b/docs/content/open_source/notification_webhooks/engagement_added.md index 2a782999034..ab9cce6e8e2 100644 --- a/docs/content/open_source/notification_webhooks/engagement_added.md +++ b/docs/content/open_source/notification_webhooks/engagement_added.md @@ -2,8 +2,9 @@ title: "Event: engagement_added" weight: 4 exclude_search: true +aliases: + - /en/open_source/notification_webhooks/engagement_added --- - ## Event HTTP header ```yaml X-DefectDojo-Event: engagement_added diff --git a/docs/content/open_source/notification_webhooks/how_to.md b/docs/content/open_source/notification_webhooks/how_to.md index e4caa61470b..5a1309d9330 100644 --- a/docs/content/open_source/notification_webhooks/how_to.md +++ b/docs/content/open_source/notification_webhooks/how_to.md @@ -2,8 +2,9 @@ title: "Notification Webhooks Setup" weight: 1 chapter: true +aliases: + - /en/open_source/notification_webhooks/how_to --- - Webhooks are HTTP requests coming from the DefectDojo instance towards a user-defined webserver which expects this kind of incoming traffic. ## Transition graph: diff --git a/docs/content/open_source/notification_webhooks/ping.md b/docs/content/open_source/notification_webhooks/ping.md index fcd1e9f93ae..9d2233bee04 100644 --- a/docs/content/open_source/notification_webhooks/ping.md +++ b/docs/content/open_source/notification_webhooks/ping.md @@ -3,8 +3,9 @@ title: "Event: ping" weight: 7 chapter: true exclude_search: true +aliases: + - /en/open_source/notification_webhooks/ping --- - An event `ping` is sent during Webhook setup to test whether the endpoint is up and responding with the expected status code. ## Event HTTP header diff --git a/docs/content/open_source/notification_webhooks/product_added.md b/docs/content/open_source/notification_webhooks/product_added.md index 0291fc56b07..b14fce04571 100644 --- a/docs/content/open_source/notification_webhooks/product_added.md +++ b/docs/content/open_source/notification_webhooks/product_added.md @@ -3,8 +3,9 @@ title: "Event: product_added" weight: 3 chapter: true exclude_search: true +aliases: + - /en/open_source/notification_webhooks/product_added --- - ## Event HTTP header ```yaml X-DefectDojo-Event: product_added diff --git a/docs/content/open_source/notification_webhooks/product_type_added.md b/docs/content/open_source/notification_webhooks/product_type_added.md index 5f76658a29b..223888e5f75 100644 --- a/docs/content/open_source/notification_webhooks/product_type_added.md +++ b/docs/content/open_source/notification_webhooks/product_type_added.md @@ -3,8 +3,9 @@ title: "Event: product_type_added" weight: 2 chapter: true exclude_search: true +aliases: + - /en/open_source/notification_webhooks/product_type_added --- - ## Event HTTP header ```yaml X-DefectDojo-Event: product_type_added diff --git a/docs/content/open_source/notification_webhooks/scan_added.md b/docs/content/open_source/notification_webhooks/scan_added.md index ea9dae28c40..e1950ac6312 100644 --- a/docs/content/open_source/notification_webhooks/scan_added.md +++ b/docs/content/open_source/notification_webhooks/scan_added.md @@ -3,8 +3,9 @@ title: "Event: scan_added and scan_added_empty" weight: 6 chapter: true exclude_search: true +aliases: + - /en/open_source/notification_webhooks/scan_added --- - Event `scan_added_empty` describes a situation when reimport did not affect the existing test (no finding has been created or closed). ## Event HTTP header for scan_added diff --git a/docs/content/open_source/notification_webhooks/test_added.md b/docs/content/open_source/notification_webhooks/test_added.md index f3b44a8a9a4..dba53ff5cda 100644 --- a/docs/content/open_source/notification_webhooks/test_added.md +++ b/docs/content/open_source/notification_webhooks/test_added.md @@ -3,8 +3,9 @@ title: "Event: test_added" weight: 5 chapter: true exclude_search: true +aliases: + - /en/open_source/notification_webhooks/test_added --- - ## Event HTTP header ```yaml X-DefectDojo-Event: test_added diff --git a/docs/content/open_source/rate_limiting.md b/docs/content/open_source/rate_limiting.md index 494a0371d6f..bbd9285a9ec 100644 --- a/docs/content/open_source/rate_limiting.md +++ b/docs/content/open_source/rate_limiting.md @@ -3,8 +3,9 @@ title: "Rate Limiting (Open-Source)" description: "Configurable rate limiting on the login page to mitigate brute force attacks" draft: false weight: 11 +aliases: + - /en/open_source/rate_limiting --- - DefectDojo has protection against brute force attacks through rate limiting. ## Configuration diff --git a/docs/content/releases/os_upgrading/upgrading_guide.md b/docs/content/releases/os_upgrading/upgrading_guide.md index 18a07166141..cd3ff2542c2 100644 --- a/docs/content/releases/os_upgrading/upgrading_guide.md +++ b/docs/content/releases/os_upgrading/upgrading_guide.md @@ -5,6 +5,8 @@ draft: false sidebar: collapsed: true weight: -900000000 +aliases: + - /en/open_source/upgrading/ --- ## Docker compose diff --git a/docs/content/releases/pro/changelog.md b/docs/content/releases/pro/changelog.md index d328fb1dcfc..5ca25645e75 100644 --- a/docs/content/releases/pro/changelog.md +++ b/docs/content/releases/pro/changelog.md @@ -2,6 +2,8 @@ title: "DefectDojo Pro Changelog" description: "DefectDojo Changelog" exclude_search: true +aliases: + - /changelog/pro_changelog/ --- Here are the release notes for **DefectDojo Pro (Cloud Version)**. These release notes are focused on UX, so will not include all code changes. diff --git a/docs/content/supported_tools/parsers/file/openreports.md b/docs/content/supported_tools/parsers/file/openreports.md index d19f81c1d4e..6c6a8d1d557 100644 --- a/docs/content/supported_tools/parsers/file/openreports.md +++ b/docs/content/supported_tools/parsers/file/openreports.md @@ -1,6 +1,8 @@ --- title: "OpenReports" toc_hide: true +aliases: + - /en/connecting_your_tools/parsers/file/openreports --- Import JSON reports from [OpenReports](https://github.com/openreports/reports-api). diff --git a/docs/content/triage_findings/finding_deduplication/OS__deduplication_tuning.md b/docs/content/triage_findings/finding_deduplication/OS__deduplication_tuning.md index f88b72ed562..82968cb87f5 100644 --- a/docs/content/triage_findings/finding_deduplication/OS__deduplication_tuning.md +++ b/docs/content/triage_findings/finding_deduplication/OS__deduplication_tuning.md @@ -3,8 +3,10 @@ title: "Deduplication Tuning" description: "Configure deduplication in DefectDojo Open Source: algorithms, hash fields, endpoints, and service" weight: 5 audience: opensource +aliases: + - /en/working_with_findings/finding_deduplication/deduplication_tuning_os + - /en/working_with_findings/finding_deduplication/deduplication_algorithms --- - The Open Source edition of DefectDojo uses settings files and environment variables tune deduplication. See also: [Open Source Configuration](/get_started/open_source/configuration/) for details on environment variables and `local_settings.py` overrides. diff --git a/docs/content/triage_findings/finding_deduplication/PRO__deduplication_tuning.md b/docs/content/triage_findings/finding_deduplication/PRO__deduplication_tuning.md index 9da8005d8a1..a3cbfa6dd03 100644 --- a/docs/content/triage_findings/finding_deduplication/PRO__deduplication_tuning.md +++ b/docs/content/triage_findings/finding_deduplication/PRO__deduplication_tuning.md @@ -3,8 +3,9 @@ title: "Deduplication Tuning" description: "Configure how DefectDojo identifies and manages duplicate findings" weight: 4 audience: pro +aliases: + - /en/working_with_findings/finding_deduplication/tune_deduplication --- - Deduplication Tuning is a DefectDojo Pro feature that gives you fine-grained control over how findings are deduplicated, allowing you to optimize duplicate detection for your specific security testing workflow. ## Deduplication Settings diff --git a/docs/content/triage_findings/finding_deduplication/PRO_enabling_product_deduplication.md b/docs/content/triage_findings/finding_deduplication/PRO_enabling_product_deduplication.md index 5f2f12e4abc..12b5ce3dfdd 100644 --- a/docs/content/triage_findings/finding_deduplication/PRO_enabling_product_deduplication.md +++ b/docs/content/triage_findings/finding_deduplication/PRO_enabling_product_deduplication.md @@ -3,8 +3,9 @@ title: "Enabling Deduplication" description: "How to enable Deduplication at the Product level" weight: 2 audience: pro +aliases: + - /en/working_with_findings/finding_deduplication/enabling_product_deduplication --- - Deduplication can be implemented at either a Product level or at a more narrow Engagement level. ## Deduplication for Products diff --git a/docs/content/triage_findings/finding_deduplication/about_deduplication.md b/docs/content/triage_findings/finding_deduplication/about_deduplication.md index 14f203a3afe..5e18a8c21cb 100644 --- a/docs/content/triage_findings/finding_deduplication/about_deduplication.md +++ b/docs/content/triage_findings/finding_deduplication/about_deduplication.md @@ -2,6 +2,10 @@ title: "About Deduplication" description: "Deduplication fundamentals and key concepts" weight: 1 +aliases: + - /en/working_with_findings/finding_deduplication/about_deduplication + - /en/working_with_findings/finding_deduplication/delete_deduplicates + - /en/working_with_findings/findings_workflows/manage_duplicate_findings --- DefectDojo is designed to ingest bulk reports from tools, creating one or more Findings based on the content of the report. When using DefectDojo, you’ll most likely be ingesting reports from the same tool on a regular basis, which means that duplicate Findings are highly likely. diff --git a/docs/content/triage_findings/finding_deduplication/avoid_excess_duplicates.md b/docs/content/triage_findings/finding_deduplication/avoid_excess_duplicates.md index bd144df6dd3..b30a187e098 100644 --- a/docs/content/triage_findings/finding_deduplication/avoid_excess_duplicates.md +++ b/docs/content/triage_findings/finding_deduplication/avoid_excess_duplicates.md @@ -2,8 +2,9 @@ title: "Avoiding Excess Duplicates" description: "" weight: 4 +aliases: + - /en/working_with_findings/finding_deduplication/avoiding_duplicates_via_reimport --- - One of DefectDojo’s strengths is that the data model can accommodate many different use\-cases and applications. You’ll likely change your approach as you master the software and discover ways to optimize your workflow. By default, DefectDojo does not delete any duplicate Findings that are created. Each Finding is considered to be a separate instance of a vulnerability. So in this case, **Duplicate Findings** can be an indicator that a process change is required to your workflow. diff --git a/docs/content/triage_findings/findings_workflows/PRO__risk_acceptance.md b/docs/content/triage_findings/findings_workflows/PRO__risk_acceptance.md index 8ddf6e6a1e5..04eeba030cd 100644 --- a/docs/content/triage_findings/findings_workflows/PRO__risk_acceptance.md +++ b/docs/content/triage_findings/findings_workflows/PRO__risk_acceptance.md @@ -3,6 +3,8 @@ title: "Risk Acceptances" description: "Leveraging Risk Acceptances in DefectDojo Pro" audience: pro weight: 2 +aliases: + - /en/working_with_findings/findings_workflows/risk_acceptances/ --- **Risk Acceptances** are a special status that can be applied to Findings using either **Full Risk Acceptance** objects or the **Simple Risk Acceptance** workflow. Risk Acceptances are used to formally document and operationalize the decision to acknowledge a vulnerable Finding without immediately remediating it. diff --git a/docs/content/triage_findings/findings_workflows/create_findings_manually.md b/docs/content/triage_findings/findings_workflows/create_findings_manually.md index 639ac411fd3..6bad932086c 100644 --- a/docs/content/triage_findings/findings_workflows/create_findings_manually.md +++ b/docs/content/triage_findings/findings_workflows/create_findings_manually.md @@ -2,8 +2,9 @@ title: "Creating Findings Manually" description: "Track vulnerability information without using a scan tool" weight: 2 +aliases: + - /en/working_with_findings/findings_workflows/create_findings_manually --- - Normally, most of the Findings in your environment will be imported from other security tools. If you wish, you can add manual Finding entries as well, if you have vulnerabilities or work you wish to manage that was not created from a scan tool. 1. From the DefectDojo Sidebar, open the New Finding link by clicking **Manage \> Findings \> New Finding**. diff --git a/docs/content/triage_findings/findings_workflows/editing_findings.md b/docs/content/triage_findings/findings_workflows/editing_findings.md index adece9325ff..368ade22a8d 100644 --- a/docs/content/triage_findings/findings_workflows/editing_findings.md +++ b/docs/content/triage_findings/findings_workflows/editing_findings.md @@ -2,8 +2,9 @@ title: "Editing Findings" description: "Change a Finding’s Status, or add more metadata as you resolve an issue" weight: 2 +aliases: + - /en/working_with_findings/findings_workflows/editing_findings --- - If you want to add notes or update the language on a Finding to be more relevant to the current situation, you can do so through the Edit Finding form. ## Open the Edit Finding Form diff --git a/docs/content/triage_findings/findings_workflows/finding_status_definitions.md b/docs/content/triage_findings/findings_workflows/finding_status_definitions.md index 6b680923ded..327f4f9aed8 100644 --- a/docs/content/triage_findings/findings_workflows/finding_status_definitions.md +++ b/docs/content/triage_findings/findings_workflows/finding_status_definitions.md @@ -2,8 +2,9 @@ title: "Finding Status Definitions" description: "A quick reference to Finding status: Open, Verified, Accepted.." weight: 2 +aliases: + - /en/working_with_findings/findings_workflows/finding_status_definitions --- - Each Finding created in DefectDojo has a Status which communicates relevant information. Statuses help your team keep track of their progress in resolving issues. Each Finding status has a context\-specific meaning which will need to be defined by your own team. These are our suggestions, but your team's usage may vary. diff --git a/docs/content/triage_findings/findings_workflows/intro_to_findings.md b/docs/content/triage_findings/findings_workflows/intro_to_findings.md index 8d455dd4150..70fd854ec15 100644 --- a/docs/content/triage_findings/findings_workflows/intro_to_findings.md +++ b/docs/content/triage_findings/findings_workflows/intro_to_findings.md @@ -2,8 +2,9 @@ title: "Introduction to Findings" description: "The main workflow and vulnerability tracking system of DefectDojo" weight: 1 +aliases: + - /en/working_with_findings/intro_to_findings --- - Findings are the main way that DefectDojo standardizes and guides the reporting and remediation process of your security tools. Regardless of whether a vulnerability was reported in SonarQube, Acunetix, or your team’s custom tool, Findings give you the ability to manage each vulnerability in the same way. ## What are Findings?