From 2cbfe93638f79fdd33dd4cc4e6e9fd27e08a70e7 Mon Sep 17 00:00:00 2001 From: Paul Osinski Date: Mon, 17 Aug 2026 16:45:20 -0400 Subject: [PATCH 1/2] add aliasing to avoid 404s --- docs/content/admin/notifications/_index.md | 2 ++ .../notifications/configure_system_notifs.md | 1 + .../admin/notifications/email_slack_teams.md | 1 + docs/content/admin/sso/PRO__ldap.md | 2 ++ docs/content/admin/sso/_index.md | 1 + .../user_management/OS__audit_logging.md | 1 + docs/content/admin/user_management/_index.md | 2 ++ docs/content/archived_docs/_index.md | 18 +++++++++++ .../OS_hierarchy/OS__asset_health_grade.md | 1 + .../OS_hierarchy/OS__asset_hierarchy.md | 1 + .../OS_hierarchy/OS__sla_configuration.md | 1 + .../OS__source-code-repositories.md | 1 + .../asset_modelling/OS_hierarchy/_index.md | 2 ++ .../OS_hierarchy/benchmarks.md | 2 ++ .../PRO_hierarchy/priority_sla.md | 5 +-- .../engagements_tests/PRO__organizations.md | 2 ++ .../engagements_tests/_index.md | 2 ++ .../tags/OS__tagging_objects.md | 2 ++ docs/content/automation/api/_index.md | 2 ++ docs/content/automation/api/languages.md | 1 + .../automation/api/notification_webhooks.md | 13 ++++++++ docs/content/automation/api/rate_limiting.md | 1 + .../connectors/os_jira/os__jira_guide.md | 1 + .../get_started/about/about_defectdojo.md | Bin 7234 -> 7262 bytes docs/content/get_started/about/demo.md | 2 ++ docs/content/get_started/about/faq.de.md | 2 +- docs/content/get_started/about/faq.es.md | 2 +- docs/content/get_started/about/faq.fr.md | 2 +- docs/content/get_started/about/faq.ja.md | 2 +- docs/content/get_started/about/faq.md | 2 +- .../get_started/contributing/_index.md | 1 + .../contributing/branching-model.md | 1 + .../get_started/contributing/documentation.md | Bin 2859 -> 2906 bytes .../contributing/how-to-write-a-parser.md | 1 + .../parser-documentation-template.md | 1 + .../content/get_started/open_source/_index.md | 3 ++ .../get_started/open_source/architecture.md | 1 + .../get_started/open_source/installation.md | 1 + .../open_source/running-in-production.md | 1 + docs/content/get_started/pro/cloud/_index.md | 2 ++ docs/content/help/contact_sales.de.md | 2 +- docs/content/help/contact_sales.es.md | 2 +- docs/content/help/contact_sales.fr.md | 2 +- docs/content/help/contact_sales.ja.md | 2 +- docs/content/help/contact_sales.md | 2 +- .../import_data/import_intro/comparison.md | 1 + .../import_data/import_scan_files/_index.md | 2 ++ docs/content/metrics_reports/ai/_index.md | 2 ++ .../dashboards/Introduction_dashboard.md | 1 + .../metrics_reports/dashboards/_index.md | 2 ++ .../reports/OS__using_the_report_builder.md | 1 + .../content/metrics_reports/reports/_index.md | 2 ++ docs/content/releases/_index.md | 3 ++ docs/content/releases/os_upgrading/1.10.md | 2 ++ docs/content/releases/os_upgrading/1.11.md | 3 ++ docs/content/releases/os_upgrading/1.13.md | 2 ++ docs/content/releases/os_upgrading/1.14.md | 2 ++ docs/content/releases/os_upgrading/1.15.md | 3 ++ docs/content/releases/os_upgrading/1.2.2.md | 3 ++ docs/content/releases/os_upgrading/1.2.3.md | 3 ++ docs/content/releases/os_upgrading/1.2.4.md | 2 ++ docs/content/releases/os_upgrading/1.2.8.md | 3 ++ docs/content/releases/os_upgrading/1.2.9.md | 3 ++ docs/content/releases/os_upgrading/1.3.1.md | 2 ++ docs/content/releases/os_upgrading/1.7.0.md | 3 ++ docs/content/releases/os_upgrading/1.8.0.md | 3 ++ docs/content/releases/os_upgrading/1.9.3.md | 3 ++ docs/content/releases/os_upgrading/2.0.md | 3 ++ docs/content/releases/os_upgrading/2.10.md | 2 ++ docs/content/releases/os_upgrading/2.12.md | 2 ++ docs/content/releases/os_upgrading/2.13.md | 2 ++ docs/content/releases/os_upgrading/2.15.md | 2 ++ docs/content/releases/os_upgrading/2.16.md | 3 ++ docs/content/releases/os_upgrading/2.17.md | 3 ++ docs/content/releases/os_upgrading/2.18.md | 2 ++ docs/content/releases/os_upgrading/2.19.md | 3 ++ docs/content/releases/os_upgrading/2.2.md | 3 ++ docs/content/releases/os_upgrading/2.20.md | 2 ++ docs/content/releases/os_upgrading/2.21.md | 2 ++ docs/content/releases/os_upgrading/2.22.md | 2 ++ docs/content/releases/os_upgrading/2.23.md | 2 ++ docs/content/releases/os_upgrading/2.24.md | 2 ++ docs/content/releases/os_upgrading/2.25.md | 2 ++ docs/content/releases/os_upgrading/2.26.md | 2 ++ docs/content/releases/os_upgrading/2.27.md | 2 ++ docs/content/releases/os_upgrading/2.29.md | 2 ++ docs/content/releases/os_upgrading/2.3.md | 3 ++ docs/content/releases/os_upgrading/2.30.md | 3 ++ docs/content/releases/os_upgrading/2.31.md | 2 ++ docs/content/releases/os_upgrading/2.32.md | 2 ++ docs/content/releases/os_upgrading/2.33.md | 3 ++ docs/content/releases/os_upgrading/2.34.md | 2 ++ docs/content/releases/os_upgrading/2.35.md | 2 ++ docs/content/releases/os_upgrading/2.36.md | 2 ++ docs/content/releases/os_upgrading/2.37.md | 2 ++ docs/content/releases/os_upgrading/2.38.md | 2 ++ docs/content/releases/os_upgrading/2.39.md | 3 ++ docs/content/releases/os_upgrading/2.4.md | 3 ++ docs/content/releases/os_upgrading/2.40.md | 3 ++ docs/content/releases/os_upgrading/2.41.md | 3 ++ docs/content/releases/os_upgrading/2.42.md | 2 ++ docs/content/releases/os_upgrading/2.43.md | 2 ++ docs/content/releases/os_upgrading/2.44.1.md | 3 ++ docs/content/releases/os_upgrading/2.44.md | 2 ++ docs/content/releases/os_upgrading/2.45.md | 3 ++ docs/content/releases/os_upgrading/2.46.md | 2 ++ docs/content/releases/os_upgrading/2.47.md | 2 ++ docs/content/releases/os_upgrading/2.48.2.md | 2 ++ docs/content/releases/os_upgrading/2.48.md | 2 ++ docs/content/releases/os_upgrading/2.49.md | 3 ++ docs/content/releases/os_upgrading/2.5.md | 2 ++ docs/content/releases/os_upgrading/2.50.md | 2 ++ docs/content/releases/os_upgrading/2.51.md | 2 ++ docs/content/releases/os_upgrading/2.52.md | 2 ++ docs/content/releases/os_upgrading/2.53.md | 2 ++ docs/content/releases/os_upgrading/2.54.3.md | 2 ++ docs/content/releases/os_upgrading/2.54.md | 2 ++ docs/content/releases/os_upgrading/2.55.md | 2 ++ docs/content/releases/os_upgrading/2.56.md | 2 ++ docs/content/releases/os_upgrading/2.57.md | 2 ++ docs/content/releases/os_upgrading/2.6.md | 2 ++ docs/content/releases/os_upgrading/2.7.md | 3 ++ docs/content/releases/os_upgrading/2.8.md | 2 ++ docs/content/releases/os_upgrading/2.9.md | 2 ++ docs/content/releases/os_upgrading/_index.md | 3 ++ .../releases/os_upgrading/upgrading_guide.md | 4 +++ docs/content/releases/pro/changelog.md | 13 ++++---- docs/content/supported_tools/_index.md | 3 ++ .../content/supported_tools/parsers/_index.md | 2 ++ .../supported_tools/parsers/api/bugcrowd.md | 2 ++ .../supported_tools/parsers/api/sonarqube.md | 2 ++ .../supported_tools/parsers/file/_index.md | 2 ++ .../supported_tools/parsers/file/acunetix.md | 2 +- .../parsers/file/anchore_engine.md | 4 ++- .../parsers/file/anchore_enterprise.md | 2 +- .../parsers/file/anchore_grype.md | 4 ++- .../parsers/file/anchorectl_policies.md | 2 +- .../parsers/file/anchorectl_vulns.md | 2 +- .../file/appcheck_web_application_scanner.md | 2 +- .../supported_tools/parsers/file/appspider.md | 2 +- .../supported_tools/parsers/file/aqua.md | 2 +- .../supported_tools/parsers/file/arachni.md | 2 +- .../supported_tools/parsers/file/asff.md | 2 +- .../supported_tools/parsers/file/auditjs.md | 2 +- .../parsers/file/aws_inspector2.md | 4 ++- .../parsers/file/aws_prowler.md | 4 ++- .../parsers/file/aws_prowler_v3plus.md | 2 +- .../parsers/file/awssecurityhub.md | 4 ++- .../azure_security_center_recommendations.md | 2 +- .../supported_tools/parsers/file/bandit.md | 4 ++- .../parsers/file/bearer_cli.md | 2 +- .../supported_tools/parsers/file/blackduck.md | 2 +- .../parsers/file/blackduck_binary_analysis.md | 2 +- .../parsers/file/blackduck_component_risk.md | 2 +- .../supported_tools/parsers/file/brakeman.md | 2 +- .../supported_tools/parsers/file/bugcrowd.md | 2 +- .../parsers/file/bundler_audit.md | 2 +- .../supported_tools/parsers/file/burp.md | 5 ++- .../supported_tools/parsers/file/burp_api.md | 2 +- .../parsers/file/burp_dastardly.md | 2 +- .../parsers/file/burp_graphql.md | 2 +- .../parsers/file/burp_suite_dast.md | 2 +- .../parsers/file/cargo_audit.md | 2 +- .../supported_tools/parsers/file/checkmarx.md | 4 ++- .../parsers/file/checkmarx_cxflow_sast.md | 2 +- .../parsers/file/checkmarx_one.md | 4 ++- .../supported_tools/parsers/file/checkov.md | 4 ++- .../parsers/file/chefinspect.md | 2 +- .../supported_tools/parsers/file/clair.md | 2 +- .../parsers/file/cloudsploit.md | 2 +- .../supported_tools/parsers/file/cobalt.md | 2 +- .../parsers/file/codechecker.md | 2 +- .../supported_tools/parsers/file/codeql.md | 2 +- .../supported_tools/parsers/file/contrast.md | 2 +- .../parsers/file/coverity_api.md | 2 +- .../parsers/file/coverity_scan.md | 2 +- .../parsers/file/crashtest_security.md | 4 ++- .../supported_tools/parsers/file/cred_scan.md | 4 ++- .../supported_tools/parsers/file/crunch42.md | 2 +- .../parsers/file/cyberwatch_galeax.md | 2 +- .../supported_tools/parsers/file/cyclonedx.md | 4 ++- .../parsers/file/dawnscanner.md | 2 +- .../parsers/file/deepfence_threatmapper.md | 2 +- .../parsers/file/dependency_check.md | 4 ++- .../parsers/file/dependency_track.md | 4 ++- .../parsers/file/detect_secrets.md | 2 +- .../parsers/file/dockerbench.md | 2 +- .../supported_tools/parsers/file/dockle.md | 2 +- .../supported_tools/parsers/file/drheader.md | 2 +- .../supported_tools/parsers/file/dsop.md | 2 +- .../supported_tools/parsers/file/edgescan.md | 4 ++- .../supported_tools/parsers/file/eslint.md | 2 +- .../supported_tools/parsers/file/fortify.md | 4 ++- .../supported_tools/parsers/file/garak.md | 2 +- .../parsers/file/gcloud_artifact_scan.md | 2 +- .../supported_tools/parsers/file/generic.md | 4 ++- .../supported_tools/parsers/file/ggshield.md | 2 +- .../parsers/file/github_sast.md | 2 ++ .../parsers/file/github_vulnerability.md | 4 ++- .../parsers/file/gitlab_api_fuzzing.md | 2 +- .../parsers/file/gitlab_container_scan.md | 2 +- .../parsers/file/gitlab_dast.md | 2 +- .../parsers/file/gitlab_dep_scan.md | 2 +- .../parsers/file/gitlab_sast.md | 2 +- .../file/gitlab_secret_detection_report.md | 2 +- .../supported_tools/parsers/file/gitleaks.md | 4 ++- .../supported_tools/parsers/file/gosec.md | 2 +- .../parsers/file/govulncheck.md | 2 +- .../supported_tools/parsers/file/h1.md | 2 +- .../supported_tools/parsers/file/hadolint.md | 2 +- .../parsers/file/harbor_vulnerability.md | 4 ++- .../parsers/file/hcl_appscan.md | 4 ++- .../parsers/file/hcl_asoc_sast.md | 2 +- .../supported_tools/parsers/file/horusec.md | 2 +- .../supported_tools/parsers/file/humble.md | 2 +- .../supported_tools/parsers/file/huskyci.md | 2 +- .../supported_tools/parsers/file/hydra.md | 2 +- .../supported_tools/parsers/file/ibm_app.md | 2 +- .../supported_tools/parsers/file/immuniweb.md | 2 +- .../supported_tools/parsers/file/intsights.md | 2 +- .../supported_tools/parsers/file/invicti.md | 4 ++- .../supported_tools/parsers/file/iriusrisk.md | 2 +- .../file/jfrog_xray_api_summary_artifact.md | 2 +- .../file/jfrog_xray_on_demand_binary_scan.md | 2 +- .../parsers/file/jfrog_xray_unified.md | 4 ++- .../supported_tools/parsers/file/jfrogxray.md | 2 +- .../supported_tools/parsers/file/kics.md | 2 +- .../supported_tools/parsers/file/kiuwan.md | 2 +- .../parsers/file/kiuwan_sca.md | 4 ++- .../parsers/file/krakend_audit.md | 2 +- .../supported_tools/parsers/file/kubeaudit.md | 2 +- .../supported_tools/parsers/file/kubebench.md | 2 +- .../parsers/file/kubehunter.md | 4 ++- .../supported_tools/parsers/file/kubescape.md | 2 +- .../supported_tools/parsers/file/legitify.md | 2 +- .../supported_tools/parsers/file/mend.md | 2 +- .../supported_tools/parsers/file/meterian.md | 2 +- .../parsers/file/microfocus_webinspect.md | 2 +- .../supported_tools/parsers/file/mobsf.md | 2 +- .../parsers/file/mobsf_scorecard.md | 2 +- .../parsers/file/mozilla_observatory.md | 2 +- .../parsers/file/ms_defender.md | 4 ++- .../supported_tools/parsers/file/n0s1.md | 2 +- .../supported_tools/parsers/file/nancy.md | 2 +- .../parsers/file/netsparker.md | 2 +- .../supported_tools/parsers/file/neuvector.md | 2 +- .../parsers/file/neuvector_compliance.md | 2 +- .../supported_tools/parsers/file/nexpose.md | 4 ++- .../supported_tools/parsers/file/nikto.md | 2 +- .../supported_tools/parsers/file/nmap.md | 4 ++- .../parsers/file/noseyparker.md | 2 +- .../supported_tools/parsers/file/npm_audit.md | 2 +- .../parsers/file/npm_audit_7_plus.md | 2 +- .../supported_tools/parsers/file/nsp.md | 4 ++- .../supported_tools/parsers/file/nuclei.md | 4 ++- .../supported_tools/parsers/file/openscap.md | 2 +- .../supported_tools/parsers/file/openvas.md | 4 ++- .../parsers/file/orca_security.md | 2 +- .../supported_tools/parsers/file/ort.md | 2 +- .../parsers/file/ossindex_devaudit.md | 2 +- .../parsers/file/osv_scanner.md | 2 +- .../supported_tools/parsers/file/outpost24.md | 2 +- .../parsers/file/php_security_audit_v2.md | 2 +- .../file/php_symfony_security_check.md | 2 +- .../supported_tools/parsers/file/picus.md | 2 +- .../supported_tools/parsers/file/pip_audit.md | 2 +- .../supported_tools/parsers/file/pmd.md | 2 +- .../supported_tools/parsers/file/popeye.md | 2 +- .../supported_tools/parsers/file/progpilot.md | 4 ++- .../supported_tools/parsers/file/prowler.md | 2 +- .../supported_tools/parsers/file/ptart.md | 2 +- .../supported_tools/parsers/file/pwn_sast.md | 4 ++- .../supported_tools/parsers/file/qualys.md | 4 ++- .../parsers/file/qualys_hacker_guardian.md | 2 +- .../parsers/file/qualys_infrascan_webgui.md | 2 +- .../parsers/file/qualys_vmdr.md | 2 +- .../parsers/file/qualys_webapp.md | 2 +- .../supported_tools/parsers/file/rapplex.md | 2 +- .../parsers/file/redhatsatellite.md | 2 +- .../supported_tools/parsers/file/retirejs.md | 2 +- .../parsers/file/risk_recon.md | 2 +- .../supported_tools/parsers/file/rubocop.md | 2 +- .../supported_tools/parsers/file/rusty_hog.md | 2 +- .../supported_tools/parsers/file/sarif.md | 2 ++ .../supported_tools/parsers/file/scantist.md | 2 +- .../parsers/file/scout_suite.md | 2 +- .../supported_tools/parsers/file/semgrep.md | 4 ++- .../supported_tools/parsers/file/skf.md | 2 +- .../supported_tools/parsers/file/snyk.md | 2 +- .../supported_tools/parsers/file/snyk_code.md | 4 ++- .../parsers/file/snyk_issue_api.md | 2 +- .../parsers/file/solar_appscreener.md | 2 +- .../supported_tools/parsers/file/sonarqube.md | 4 ++- .../supported_tools/parsers/file/sonatype.md | 2 +- .../supported_tools/parsers/file/spotbugs.md | 2 +- .../supported_tools/parsers/file/ssh_audit.md | 2 +- .../supported_tools/parsers/file/ssl_labs.md | 2 +- .../supported_tools/parsers/file/sslscan.md | 2 +- .../supported_tools/parsers/file/sslyze.md | 2 +- .../supported_tools/parsers/file/stackhawk.md | 2 +- .../parsers/file/sysdig_cli.md | 2 +- .../parsers/file/sysdig_reports.md | 2 +- .../supported_tools/parsers/file/talisman.md | 2 +- .../supported_tools/parsers/file/tenable.md | 4 ++- .../supported_tools/parsers/file/terrascan.md | 2 +- .../supported_tools/parsers/file/testssl.md | 2 +- .../supported_tools/parsers/file/tfsec.md | 2 +- .../supported_tools/parsers/file/threagile.md | 2 +- .../parsers/file/threat_composer.md | 2 +- .../supported_tools/parsers/file/trivy.md | 4 ++- .../parsers/file/trivy_operator.md | 2 +- .../parsers/file/trufflehog.md | 4 ++- .../parsers/file/trufflehog3.md | 2 +- .../supported_tools/parsers/file/trustwave.md | 2 +- .../parsers/file/trustwave_fusion_api.md | 2 +- .../supported_tools/parsers/file/twistlock.md | 2 +- .../supported_tools/parsers/file/vcg.md | 2 +- .../supported_tools/parsers/file/veracode.md | 2 +- .../parsers/file/veracode_sca.md | 4 ++- .../supported_tools/parsers/file/wapiti.md | 2 +- .../supported_tools/parsers/file/wazuh.md | 4 ++- .../supported_tools/parsers/file/wfuzz.md | 2 +- .../supported_tools/parsers/file/whispers.md | 2 +- .../parsers/file/whitehat_sentinel.md | 2 +- .../supported_tools/parsers/file/wiz.md | 4 ++- .../parsers/file/wizcli_dir.md | 4 ++- .../parsers/file/wizcli_iac.md | 4 ++- .../parsers/file/wizcli_img.md | 2 +- .../supported_tools/parsers/file/wpscan.md | 2 +- .../supported_tools/parsers/file/xanitizer.md | 2 +- .../parsers/file/yarn_audit.md | 2 +- .../supported_tools/parsers/file/zap.md | 2 +- .../parsers/generic_findings_import.md | 2 ++ .../parsers/universal_parser.md | 2 ++ .../finding_deduplication/_index.md | 2 ++ .../finding_scoring/cvss_support.md | 2 ++ .../findings_workflows/OS__risk_acceptance.md | 3 ++ .../findings_workflows/_index.md | 2 ++ .../findings_workflows/exporting.md | 1 + docs/netlify.toml | 30 ++++++++++++++++++ 340 files changed, 632 insertions(+), 216 deletions(-) diff --git a/docs/content/admin/notifications/_index.md b/docs/content/admin/notifications/_index.md index 3c6eb3a19d5..af7e6ce732a 100644 --- a/docs/content/admin/notifications/_index.md +++ b/docs/content/admin/notifications/_index.md @@ -13,4 +13,6 @@ seo: robots: "" # custom robot tags (optional) pro-feature: true exclude_search: true +aliases: + - "/en/customize_dojo/notifications/" --- \ No newline at end of file diff --git a/docs/content/admin/notifications/configure_system_notifs.md b/docs/content/admin/notifications/configure_system_notifs.md index 1479049e959..3e1d3e8d8c5 100644 --- a/docs/content/admin/notifications/configure_system_notifs.md +++ b/docs/content/admin/notifications/configure_system_notifs.md @@ -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). diff --git a/docs/content/admin/notifications/email_slack_teams.md b/docs/content/admin/notifications/email_slack_teams.md index 18fd5f266da..51bc12533fc 100644 --- a/docs/content/admin/notifications/email_slack_teams.md +++ b/docs/content/admin/notifications/email_slack_teams.md @@ -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.** diff --git a/docs/content/admin/sso/PRO__ldap.md b/docs/content/admin/sso/PRO__ldap.md index 5010361a083..3becadfa3e9 100644 --- a/docs/content/admin/sso/PRO__ldap.md +++ b/docs/content/admin/sso/PRO__ldap.md @@ -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 --- diff --git a/docs/content/admin/sso/_index.md b/docs/content/admin/sso/_index.md index 37107b6e150..facfd62a271 100644 --- a/docs/content/admin/sso/_index.md +++ b/docs/content/admin/sso/_index.md @@ -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/ diff --git a/docs/content/admin/user_management/OS__audit_logging.md b/docs/content/admin/user_management/OS__audit_logging.md index 9262707ebf0..6d9c85f5d77 100644 --- a/docs/content/admin/user_management/OS__audit_logging.md +++ b/docs/content/admin/user_management/OS__audit_logging.md @@ -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. diff --git a/docs/content/admin/user_management/_index.md b/docs/content/admin/user_management/_index.md index 824ba2cc5a9..0ab530d1ffa 100644 --- a/docs/content/admin/user_management/_index.md +++ b/docs/content/admin/user_management/_index.md @@ -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. diff --git a/docs/content/archived_docs/_index.md b/docs/content/archived_docs/_index.md index 2e5a854b27e..6d965027dd7 100644 --- a/docs/content/archived_docs/_index.md +++ b/docs/content/archived_docs/_index.md @@ -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/" --- \ No newline at end of file diff --git a/docs/content/asset_modelling/OS_hierarchy/OS__asset_health_grade.md b/docs/content/asset_modelling/OS_hierarchy/OS__asset_health_grade.md index ba47d9a2530..8f468a399a3 100644 --- a/docs/content/asset_modelling/OS_hierarchy/OS__asset_health_grade.md +++ b/docs/content/asset_modelling/OS_hierarchy/OS__asset_health_grade.md @@ -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/ --- diff --git a/docs/content/asset_modelling/OS_hierarchy/OS__asset_hierarchy.md b/docs/content/asset_modelling/OS_hierarchy/OS__asset_hierarchy.md index 908ccf3a3c6..0e799ba39e0 100644 --- a/docs/content/asset_modelling/OS_hierarchy/OS__asset_hierarchy.md +++ b/docs/content/asset_modelling/OS_hierarchy/OS__asset_hierarchy.md @@ -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/ diff --git a/docs/content/asset_modelling/OS_hierarchy/OS__sla_configuration.md b/docs/content/asset_modelling/OS_hierarchy/OS__sla_configuration.md index 679affc439a..312811c9c33 100644 --- a/docs/content/asset_modelling/OS_hierarchy/OS__sla_configuration.md +++ b/docs/content/asset_modelling/OS_hierarchy/OS__sla_configuration.md @@ -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. diff --git a/docs/content/asset_modelling/OS_hierarchy/OS__source-code-repositories.md b/docs/content/asset_modelling/OS_hierarchy/OS__source-code-repositories.md index 4d6f560de07..989b5a5cf07 100644 --- a/docs/content/asset_modelling/OS_hierarchy/OS__source-code-repositories.md +++ b/docs/content/asset_modelling/OS_hierarchy/OS__source-code-repositories.md @@ -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. diff --git a/docs/content/asset_modelling/OS_hierarchy/_index.md b/docs/content/asset_modelling/OS_hierarchy/_index.md index a5302b58fac..ef917121d88 100644 --- a/docs/content/asset_modelling/OS_hierarchy/_index.md +++ b/docs/content/asset_modelling/OS_hierarchy/_index.md @@ -8,4 +8,6 @@ weight: 3 sidebar: collapsed: false exclude_search: true +aliases: + - "/asset_modelling/hierarchy/" --- diff --git a/docs/content/asset_modelling/OS_hierarchy/benchmarks.md b/docs/content/asset_modelling/OS_hierarchy/benchmarks.md index 61dc3043952..d38f41a0070 100644 --- a/docs/content/asset_modelling/OS_hierarchy/benchmarks.md +++ b/docs/content/asset_modelling/OS_hierarchy/benchmarks.md @@ -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. diff --git a/docs/content/asset_modelling/PRO_hierarchy/priority_sla.md b/docs/content/asset_modelling/PRO_hierarchy/priority_sla.md index 2b1bc980e1a..f2b6b7007be 100644 --- a/docs/content/asset_modelling/PRO_hierarchy/priority_sla.md +++ b/docs/content/asset_modelling/PRO_hierarchy/priority_sla.md @@ -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) diff --git a/docs/content/asset_modelling/engagements_tests/PRO__organizations.md b/docs/content/asset_modelling/engagements_tests/PRO__organizations.md index bd66b1e1361..638f6a6525d 100644 --- a/docs/content/asset_modelling/engagements_tests/PRO__organizations.md +++ b/docs/content/asset_modelling/engagements_tests/PRO__organizations.md @@ -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 diff --git a/docs/content/asset_modelling/engagements_tests/_index.md b/docs/content/asset_modelling/engagements_tests/_index.md index 913e3b7ae79..4d99812fef6 100644 --- a/docs/content/asset_modelling/engagements_tests/_index.md +++ b/docs/content/asset_modelling/engagements_tests/_index.md @@ -5,4 +5,6 @@ draft: false type: docs weight: 1 exclude_search: true +aliases: + - "/en/working_with_findings/organizing_engagements_tests/" --- diff --git a/docs/content/asset_modelling/tags/OS__tagging_objects.md b/docs/content/asset_modelling/tags/OS__tagging_objects.md index 56e108f0570..156f762f835 100644 --- a/docs/content/asset_modelling/tags/OS__tagging_objects.md +++ b/docs/content/asset_modelling/tags/OS__tagging_objects.md @@ -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. diff --git a/docs/content/automation/api/_index.md b/docs/content/automation/api/_index.md index c415210e8d4..9007f64251d 100644 --- a/docs/content/automation/api/_index.md +++ b/docs/content/automation/api/_index.md @@ -13,4 +13,6 @@ seo: canonical: "" # custom canonical URL (optional) robots: "" # custom robot tags (optional) exclude_search: true +aliases: + - "/en/api/" --- \ No newline at end of file diff --git a/docs/content/automation/api/languages.md b/docs/content/automation/api/languages.md index 65c9a98b31c..cee2da06e0d 100644 --- a/docs/content/automation/api/languages.md +++ b/docs/content/automation/api/languages.md @@ -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 --- diff --git a/docs/content/automation/api/notification_webhooks.md b/docs/content/automation/api/notification_webhooks.md index b4db89082e9..e3a50f86291 100644 --- a/docs/content/automation/api/notification_webhooks.md +++ b/docs/content/automation/api/notification_webhooks.md @@ -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 --- diff --git a/docs/content/automation/api/rate_limiting.md b/docs/content/automation/api/rate_limiting.md index f782e790b75..ab884e712f3 100644 --- a/docs/content/automation/api/rate_limiting.md +++ b/docs/content/automation/api/rate_limiting.md @@ -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 --- diff --git a/docs/content/connectors/os_jira/os__jira_guide.md b/docs/content/connectors/os_jira/os__jira_guide.md index b0269c0bbc9..65a8281513d 100644 --- a/docs/content/connectors/os_jira/os__jira_guide.md +++ b/docs/content/connectors/os_jira/os__jira_guide.md @@ -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: diff --git a/docs/content/get_started/about/about_defectdojo.md b/docs/content/get_started/about/about_defectdojo.md index 499f6120c62698a940ef39748f0b16386f34d57a..efad1ef35b5ae941266b6f2d044f75a727cbdf74 100644 GIT binary patch delta 34 pcmX?PanE8xuDFtZYMy>#QhsSkd`fCsYH~?RepbG|(#DKi(g5m?4QK!W delta 10 Rcmca-amZpq?#9lm(f}Rn1vmfz diff --git a/docs/content/get_started/about/demo.md b/docs/content/get_started/about/demo.md index f0b82c7e5ea..1a27a88e77c 100644 --- a/docs/content/get_started/about/demo.md +++ b/docs/content/get_started/about/demo.md @@ -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. diff --git a/docs/content/get_started/about/faq.de.md b/docs/content/get_started/about/faq.de.md index 2ff4f4df200..2b3a2bd8c94 100644 --- a/docs/content/get_started/about/faq.de.md +++ b/docs/content/get_started/about/faq.de.md @@ -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. diff --git a/docs/content/get_started/about/faq.es.md b/docs/content/get_started/about/faq.es.md index 3b11b248632..f0c9e0ef478 100644 --- a/docs/content/get_started/about/faq.es.md +++ b/docs/content/get_started/about/faq.es.md @@ -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. diff --git a/docs/content/get_started/about/faq.fr.md b/docs/content/get_started/about/faq.fr.md index 422158a096f..cbd2c4d197c 100644 --- a/docs/content/get_started/about/faq.fr.md +++ b/docs/content/get_started/about/faq.fr.md @@ -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. diff --git a/docs/content/get_started/about/faq.ja.md b/docs/content/get_started/about/faq.ja.md index be1b19ff744..73966ba4c88 100644 --- a/docs/content/get_started/about/faq.ja.md +++ b/docs/content/get_started/about/faq.ja.md @@ -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/)と判断した検出事項を作成しません。 一般的に言えば、単一時点のレポートが必要な場合はインポートが最適な方法です。ツールからレポートを継続的に実行・取り込んでいる場合は、物事を整理しておくために再インポートの方が適しています。 diff --git a/docs/content/get_started/about/faq.md b/docs/content/get_started/about/faq.md index 3e7443a77bc..407a3516007 100644 --- a/docs/content/get_started/about/faq.md +++ b/docs/content/get_started/about/faq.md @@ -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. diff --git a/docs/content/get_started/contributing/_index.md b/docs/content/get_started/contributing/_index.md index bfa0542cf5d..31a156343dd 100644 --- a/docs/content/get_started/contributing/_index.md +++ b/docs/content/get_started/contributing/_index.md @@ -5,6 +5,7 @@ weight: 5 chapter: true audience: opensource aliases: + - "/open_source/contributing/" - /en/open_source/contributing --- diff --git a/docs/content/get_started/contributing/branching-model.md b/docs/content/get_started/contributing/branching-model.md index b548d7b43fb..374725e3306 100644 --- a/docs/content/get_started/contributing/branching-model.md +++ b/docs/content/get_started/contributing/branching-model.md @@ -5,6 +5,7 @@ draft: false weight: 3 audience: opensource aliases: + - "/open_source/contributing/branching-model/" - /en/open_source/contributing/branching-model --- ## Regular releases diff --git a/docs/content/get_started/contributing/documentation.md b/docs/content/get_started/contributing/documentation.md index bdfb70cc4cf6d63442edf1c5c1026a7a627b6c1b..445308ca90314becdb5a061c4ad46607c110f94f 100644 GIT binary patch delta 18 ZcmZ22c1vtR2cy!&ZgnPorH#!ixBx%^25A5Q delta 10 Rcmca5wpwgL$Hwi8xd0o71m6Gv diff --git a/docs/content/get_started/contributing/how-to-write-a-parser.md b/docs/content/get_started/contributing/how-to-write-a-parser.md index e2a61110505..72be528fe68 100644 --- a/docs/content/get_started/contributing/how-to-write-a-parser.md +++ b/docs/content/get_started/contributing/how-to-write-a-parser.md @@ -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. diff --git a/docs/content/get_started/contributing/parser-documentation-template.md b/docs/content/get_started/contributing/parser-documentation-template.md index 90e7b080671..ecf554fddf0 100644 --- a/docs/content/get_started/contributing/parser-documentation-template.md +++ b/docs/content/get_started/contributing/parser-documentation-template.md @@ -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. diff --git a/docs/content/get_started/open_source/_index.md b/docs/content/get_started/open_source/_index.md index c2a35d75419..1dbd395fabe 100644 --- a/docs/content/get_started/open_source/_index.md +++ b/docs/content/get_started/open_source/_index.md @@ -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/" --- diff --git a/docs/content/get_started/open_source/architecture.md b/docs/content/get_started/open_source/architecture.md index 971291a9afc..b826edd7dc9 100644 --- a/docs/content/get_started/open_source/architecture.md +++ b/docs/content/get_started/open_source/architecture.md @@ -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) diff --git a/docs/content/get_started/open_source/installation.md b/docs/content/get_started/open_source/installation.md index 8e44b92d74c..637dc7288cc 100644 --- a/docs/content/get_started/open_source/installation.md +++ b/docs/content/get_started/open_source/installation.md @@ -5,6 +5,7 @@ draft: false weight: 1 audience: opensource aliases: + - "/en/open_source/installation/" - /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 107751efe6d..0940f8ce07a 100644 --- a/docs/content/get_started/open_source/running-in-production.md +++ b/docs/content/get_started/open_source/running-in-production.md @@ -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) diff --git a/docs/content/get_started/pro/cloud/_index.md b/docs/content/get_started/pro/cloud/_index.md index 8cc4620d4a0..9a66b10e0a8 100644 --- a/docs/content/get_started/pro/cloud/_index.md +++ b/docs/content/get_started/pro/cloud/_index.md @@ -4,4 +4,6 @@ date: 2021-02-02T20:46:29+01:00 weight: 3 collapsed: true audience: pro +aliases: + - "/en/cloud_management/" --- diff --git a/docs/content/help/contact_sales.de.md b/docs/content/help/contact_sales.de.md index ccaf8b8ed76..81d1e0b98bc 100644 --- a/docs/content/help/contact_sales.de.md +++ b/docs/content/help/contact_sales.de.md @@ -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) diff --git a/docs/content/help/contact_sales.es.md b/docs/content/help/contact_sales.es.md index 7f0a77a3963..163caf2da6b 100644 --- a/docs/content/help/contact_sales.es.md +++ b/docs/content/help/contact_sales.es.md @@ -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) diff --git a/docs/content/help/contact_sales.fr.md b/docs/content/help/contact_sales.fr.md index a576cc21517..2b8aec1de6c 100644 --- a/docs/content/help/contact_sales.fr.md +++ b/docs/content/help/contact_sales.fr.md @@ -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) diff --git a/docs/content/help/contact_sales.ja.md b/docs/content/help/contact_sales.ja.md index 1bcf8e70bdc..ee2b6d7362a 100644 --- a/docs/content/help/contact_sales.ja.md +++ b/docs/content/help/contact_sales.ja.md @@ -55,7 +55,7 @@ DefectDojoで外部サービス（GitHubやJIRAなど）を使用したい場合 ## ステップ6：リクエストの確認と送信 -リクエストをもう一度確認するよう促されます。送信後、チームがサポートの支援なしに変更できるのはファイアウォールルールのみです。サポートに連絡するには、[support@defectdojo.com](mailto:support@defectdojo.com) にメールを送るか、[こちらの記事](/en/about_defectdojo/contact_defectdojo_support/)の手順に従ってください。 +リクエストをもう一度確認するよう促されます。送信後、チームがサポートの支援なしに変更できるのはファイアウォールルールのみです。サポートに連絡するには、[support@defectdojo.com](mailto:support@defectdojo.com) にメールを送るか、[こちらの記事](/help/contact_support/)の手順に従ってください。 ![image](images/request_a_trial_6.png) diff --git a/docs/content/help/contact_sales.md b/docs/content/help/contact_sales.md index 8cfab9df71f..58a3ce3110e 100644 --- a/docs/content/help/contact_sales.md +++ b/docs/content/help/contact_sales.md @@ -54,7 +54,7 @@ Before you complete the process, please confirm the plan you want to use along w ## Step 6: Review and Submit your Request -We'll prompt you to look over your request one more time. Once submitted, only Firewall rules can be changed by your team without assistance from Support. To contact Support, please email [support@defectdojo.com](mailto:support@defectdojo.com) or follow the instructions in [this article](/en/about_defectdojo/contact_defectdojo_support/). +We'll prompt you to look over your request one more time. Once submitted, only Firewall rules can be changed by your team without assistance from Support. To contact Support, please email [support@defectdojo.com](mailto:support@defectdojo.com) or follow the instructions in [this article](/help/contact_support/). ![image](images/request_a_trial_6.png) diff --git a/docs/content/import_data/import_intro/comparison.md b/docs/content/import_data/import_intro/comparison.md index 1dd6c4c4570..f89d4753137 100644 --- a/docs/content/import_data/import_intro/comparison.md +++ b/docs/content/import_data/import_intro/comparison.md @@ -3,6 +3,7 @@ title: "Import Method Comparison" description: "Learn how to import data manually, through the API, or via a connector" weight: 1 aliases: + - "/import_data/import_intro/import_vs_reimport/" - /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. diff --git a/docs/content/import_data/import_scan_files/_index.md b/docs/content/import_data/import_scan_files/_index.md index bff91782153..b040db6dade 100644 --- a/docs/content/import_data/import_scan_files/_index.md +++ b/docs/content/import_data/import_scan_files/_index.md @@ -13,4 +13,6 @@ seo: canonical: "" # custom canonical URL (optional) robots: "" # custom robot tags (optional) exclude_search: true +aliases: + - "/en/connecting_your_tools/import_scan_files/" --- \ No newline at end of file diff --git a/docs/content/metrics_reports/ai/_index.md b/docs/content/metrics_reports/ai/_index.md index 31440c0b0ae..60ad229206a 100644 --- a/docs/content/metrics_reports/ai/_index.md +++ b/docs/content/metrics_reports/ai/_index.md @@ -14,4 +14,6 @@ seo: canonical: "" # custom canonical URL (optional) robots: "" # custom robot tags (optional) exclude_search: true +aliases: + - "/en/ai/" --- diff --git a/docs/content/metrics_reports/dashboards/Introduction_dashboard.md b/docs/content/metrics_reports/dashboards/Introduction_dashboard.md index b56157b7714..0104cbd4788 100644 --- a/docs/content/metrics_reports/dashboards/Introduction_dashboard.md +++ b/docs/content/metrics_reports/dashboards/Introduction_dashboard.md @@ -4,6 +4,7 @@ description: "Working with the front page of DefectDojo" weight: 1 audience: opensource aliases: + - "/en/customize_dojo/dashboards/introduction_dashboard/" - /en/customize_dojo/dashboards/Introduction_dashboard - /en/customize_dojo/dashboards/pro_dashboards --- diff --git a/docs/content/metrics_reports/dashboards/_index.md b/docs/content/metrics_reports/dashboards/_index.md index a24b41a2d52..528844751c4 100644 --- a/docs/content/metrics_reports/dashboards/_index.md +++ b/docs/content/metrics_reports/dashboards/_index.md @@ -12,6 +12,8 @@ seo: canonical: "" # custom canonical URL (optional) robots: "" # custom robot tags (optional) exclude_search: true +aliases: + - "/en/customize_dojo/dashboards/" --- The Dashboard is the front page of DefectDojo — a summary of your team's performance and a launchpad for monitoring the areas that matter to you. diff --git a/docs/content/metrics_reports/reports/OS__using_the_report_builder.md b/docs/content/metrics_reports/reports/OS__using_the_report_builder.md index e7530a7bbf0..745392e3de3 100644 --- a/docs/content/metrics_reports/reports/OS__using_the_report_builder.md +++ b/docs/content/metrics_reports/reports/OS__using_the_report_builder.md @@ -6,6 +6,7 @@ audience: opensource weight: 24 slug: using-the-report-builder aliases: + - "/en/pro_reports/using-the-report-builder/" - /en/share_your_findings/pro_reports/working_with_generated_reports - /metrics_reports/reports/working_with_generated_reports --- diff --git a/docs/content/metrics_reports/reports/_index.md b/docs/content/metrics_reports/reports/_index.md index 8ec7b3923a4..4e533596c5b 100644 --- a/docs/content/metrics_reports/reports/_index.md +++ b/docs/content/metrics_reports/reports/_index.md @@ -13,6 +13,8 @@ seo: canonical: "" robots: "" exclude_search: true +aliases: + - "/en/share_your_findings/pro_reports/" --- The Report Builder lets you turn DefectDojo data into polished, shareable reports — executive summaries, compliance snapshots, POA&M packages, engineering detail, and more — for audiences inside and outside your security team. diff --git a/docs/content/releases/_index.md b/docs/content/releases/_index.md index 9f4ee0de7da..b3892685d66 100644 --- a/docs/content/releases/_index.md +++ b/docs/content/releases/_index.md @@ -1,3 +1,6 @@ --- title: "Release Information" +aliases: + - "/changelog/" + - "/en/changelog/" --- diff --git a/docs/content/releases/os_upgrading/1.10.md b/docs/content/releases/os_upgrading/1.10.md index d1626518474..91a62fe5d54 100644 --- a/docs/content/releases/os_upgrading/1.10.md +++ b/docs/content/releases/os_upgrading/1.10.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20201124 description: security release + breaking changes exclude_search: true +aliases: + - "/en/open_source/upgrading/1.10/" --- **1.10.4 is a security release** diff --git a/docs/content/releases/os_upgrading/1.11.md b/docs/content/releases/os_upgrading/1.11.md index b0622f79c07..a6dc8187129 100644 --- a/docs/content/releases/os_upgrading/1.11.md +++ b/docs/content/releases/os_upgrading/1.11.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20201229 description: security release exclude_search: true +aliases: + - "/changelog/os_upgrading/1.11/" + - "/en/open_source/upgrading/1.11/" --- - See release notes: https://github.com/DefectDojo/django-DefectDojo/releases/tag/1.11.0 - 1.11.1 is a security release https://github.com/DefectDojo/django-DefectDojo/releases/tag/1.11.1 diff --git a/docs/content/releases/os_upgrading/1.13.md b/docs/content/releases/os_upgrading/1.13.md index abccac3a8b0..a9aa6c5cda6 100644 --- a/docs/content/releases/os_upgrading/1.13.md +++ b/docs/content/releases/os_upgrading/1.13.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20210223 description: hashcode calculation logic has changed exclude_search: true +aliases: + - "/en/open_source/upgrading/1.13/" --- - See release notes: https://github.com/DefectDojo/django-DefectDojo/releases/tag/1.13.0 - Hashcode settings affecting deduplication have changed, to update existing findings run: diff --git a/docs/content/releases/os_upgrading/1.14.md b/docs/content/releases/os_upgrading/1.14.md index 161ad1e6fbc..d6ae56248fb 100644 --- a/docs/content/releases/os_upgrading/1.14.md +++ b/docs/content/releases/os_upgrading/1.14.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20210330 description: hashcode calculation logic has changed exclude_search: true +aliases: + - "/en/open_source/upgrading/1.14/" --- - See release notes: https://github.com/DefectDojo/django-DefectDojo/releases/tag/1.14.0 diff --git a/docs/content/releases/os_upgrading/1.15.md b/docs/content/releases/os_upgrading/1.15.md index e65ba345da1..3b23c1d9bbf 100644 --- a/docs/content/releases/os_upgrading/1.15.md +++ b/docs/content/releases/os_upgrading/1.15.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20210500 description: hashcode calculation logic has changed exclude_search: true +aliases: + - "/changelog/os_upgrading/1.15/" + - "/en/open_source/upgrading/1.15/" --- - See release notes: https://github.com/DefectDojo/django-DefectDojo/releases/tag/1.15.0 - If you have made changes to JIRA templates or the template config in the JIRA Project config for instances/products/engagements: diff --git a/docs/content/releases/os_upgrading/1.2.2.md b/docs/content/releases/os_upgrading/1.2.2.md index 095fada7ef0..1b07200d7e9 100644 --- a/docs/content/releases/os_upgrading/1.2.2.md +++ b/docs/content/releases/os_upgrading/1.2.2.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20200202 description: multiple instructions exclude_search: true +aliases: + - "/changelog/os_upgrading/1.2.2/" + - "/en/open_source/upgrading/1.2.2/" --- Upgrading to 1.2.2 requires: diff --git a/docs/content/releases/os_upgrading/1.2.3.md b/docs/content/releases/os_upgrading/1.2.3.md index cb03f39e4cc..bb6836fee2c 100644 --- a/docs/content/releases/os_upgrading/1.2.3.md +++ b/docs/content/releases/os_upgrading/1.2.3.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20200203 description: multiple instructions exclude_search: true +aliases: + - "/changelog/os_upgrading/1.2.3/" + - "/en/open_source/upgrading/1.2.3/" --- Upgrading to 1.2.3 requires: diff --git a/docs/content/releases/os_upgrading/1.2.4.md b/docs/content/releases/os_upgrading/1.2.4.md index 19d4466db4f..2cf0104c41f 100644 --- a/docs/content/releases/os_upgrading/1.2.4.md +++ b/docs/content/releases/os_upgrading/1.2.4.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20200204 description: multiple instructions exclude_search: true +aliases: + - "/en/open_source/upgrading/1.2.4/" --- Upgrading to 1.2.4 requires: diff --git a/docs/content/releases/os_upgrading/1.2.8.md b/docs/content/releases/os_upgrading/1.2.8.md index 38e250ccb7b..e47bcbf2ed4 100644 --- a/docs/content/releases/os_upgrading/1.2.8.md +++ b/docs/content/releases/os_upgrading/1.2.8.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20200208 description: multiple instructions exclude_search: true +aliases: + - "/changelog/os_upgrading/1.2.8/" + - "/en/open_source/upgrading/1.2.8/" --- New feature: Product Grading (Overall Product Health) Upgrading to 1.2.8 requires: diff --git a/docs/content/releases/os_upgrading/1.2.9.md b/docs/content/releases/os_upgrading/1.2.9.md index 6efeb747634..72f70d3fb2a 100644 --- a/docs/content/releases/os_upgrading/1.2.9.md +++ b/docs/content/releases/os_upgrading/1.2.9.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20200209 description: multiple instructions exclude_search: true +aliases: + - "/changelog/os_upgrading/1.2.9/" + - "/en/open_source/upgrading/1.2.9/" --- **What\'s New:** New feature: Benchmarks (OWASP ASVS) diff --git a/docs/content/releases/os_upgrading/1.3.1.md b/docs/content/releases/os_upgrading/1.3.1.md index b087bdd0dbf..5424c380937 100644 --- a/docs/content/releases/os_upgrading/1.3.1.md +++ b/docs/content/releases/os_upgrading/1.3.1.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20200301 description: multiple instructions exclude_search: true +aliases: + - "/en/open_source/upgrading/1.3.1/" --- **What\'s New:** diff --git a/docs/content/releases/os_upgrading/1.7.0.md b/docs/content/releases/os_upgrading/1.7.0.md index 40f653acc75..bb847908041 100644 --- a/docs/content/releases/os_upgrading/1.7.0.md +++ b/docs/content/releases/os_upgrading/1.7.0.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20200700 description: multiple instructions exclude_search: true +aliases: + - "/changelog/os_upgrading/1.7.0/" + - "/en/open_source/upgrading/1.7.0/" --- **What\'s New:** diff --git a/docs/content/releases/os_upgrading/1.8.0.md b/docs/content/releases/os_upgrading/1.8.0.md index 55db2fcc1f2..277d8971bca 100644 --- a/docs/content/releases/os_upgrading/1.8.0.md +++ b/docs/content/releases/os_upgrading/1.8.0.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20200800 description: fix buildwatson create_endpoint_status exclude_search: true +aliases: + - "/changelog/os_upgrading/1.8.0/" + - "/en/open_source/upgrading/1.8.0/" --- **What\'s New:** diff --git a/docs/content/releases/os_upgrading/1.9.3.md b/docs/content/releases/os_upgrading/1.9.3.md index 49baa560925..bfd172b228e 100644 --- a/docs/content/releases/os_upgrading/1.9.3.md +++ b/docs/content/releases/os_upgrading/1.9.3.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20201115 description: security release exclude_search: true +aliases: + - "/changelog/os_upgrading/1.9.3/" + - "/en/open_source/upgrading/1.9.3/" --- **This is a security release** diff --git a/docs/content/releases/os_upgrading/2.0.md b/docs/content/releases/os_upgrading/2.0.md index 788ee81d1b1..2fb3de08df8 100644 --- a/docs/content/releases/os_upgrading/2.0.md +++ b/docs/content/releases/os_upgrading/2.0.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20210629 description: breaking changes exclude_search: true +aliases: + - "/en/open_source/upgrading/2.0/" + - "/open_source/upgrading/2.0/" --- Follow the usual steps to upgrade as described above. diff --git a/docs/content/releases/os_upgrading/2.10.md b/docs/content/releases/os_upgrading/2.10.md index 2e5571d4fa1..d6c9adf2c08 100644 --- a/docs/content/releases/os_upgrading/2.10.md +++ b/docs/content/releases/os_upgrading/2.10.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20220503 description: breaking change exclude_search: true +aliases: + - "/en/open_source/upgrading/2.10/" --- **Breaking change for Findings:** The field `cve` will be replaced by a list of Vulnerability Ids, which can store references to security advisories associated with this finding. These can be Common Vulnerabilities and Exposures (CVE) or from other sources, eg. GitHub Security Advisories. Although the field does still exist in the code, the API and the UI have already been changed to use the list of Vulnerability Ids. Other areas like hash code calculation, search and parsers will be migrated step by step in later stages. diff --git a/docs/content/releases/os_upgrading/2.12.md b/docs/content/releases/os_upgrading/2.12.md index 94c7f8923c9..b8c92ac30ff 100644 --- a/docs/content/releases/os_upgrading/2.12.md +++ b/docs/content/releases/os_upgrading/2.12.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20220705 description: breaking change exclude_search: true +aliases: + - "/en/open_source/upgrading/2.12/" --- **Breaking change for search:** The field `cve` has been removed from the search index for Findings and the Vulnerability Ids have been added to the search index. With this the syntax to search explicitly for vulnerability ids have been changed from `cve:` to `vulnerability_id:`, e.g. `vulnerability_id:CVE-2020-27619`. diff --git a/docs/content/releases/os_upgrading/2.13.md b/docs/content/releases/os_upgrading/2.13.md index ea41340585f..09139bc9bc1 100644 --- a/docs/content/releases/os_upgrading/2.13.md +++ b/docs/content/releases/os_upgrading/2.13.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20220802 description: instructions for helm chart and others exclude_search: true +aliases: + - "/en/open_source/upgrading/2.13/" --- The last release implemented the search for vulnerability ids, but the search database was not initialized. To populate the database table of the vulnerability ids, execute this django command from the defect dojo installation directory or from a shell of the Docker container or Kubernetes pod: diff --git a/docs/content/releases/os_upgrading/2.15.md b/docs/content/releases/os_upgrading/2.15.md index a9ef9b15393..0c3a037f254 100644 --- a/docs/content/releases/os_upgrading/2.15.md +++ b/docs/content/releases/os_upgrading/2.15.md @@ -4,5 +4,7 @@ toc_hide: true weight: -20221004 description: No special instructions. exclude_search: true +aliases: + - "/en/open_source/upgrading/2.15/" --- There are no special instructions for upgrading to 2.15.0. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.15.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.16.md b/docs/content/releases/os_upgrading/2.16.md index 2ad696f9be1..c9dc8c6f691 100644 --- a/docs/content/releases/os_upgrading/2.16.md +++ b/docs/content/releases/os_upgrading/2.16.md @@ -4,5 +4,8 @@ toc_hide: true weight: -20221102 description: No special instructions. exclude_search: true +aliases: + - "/changelog/os_upgrading/2.16/" + - "/en/open_source/upgrading/2.16/" --- There are no special instructions for upgrading to 2.16.0. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.16.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.17.md b/docs/content/releases/os_upgrading/2.17.md index ad0801a50d0..331b270fcd3 100644 --- a/docs/content/releases/os_upgrading/2.17.md +++ b/docs/content/releases/os_upgrading/2.17.md @@ -4,5 +4,8 @@ toc_hide: true weight: -20221206 description: No special instructions. exclude_search: true +aliases: + - "/changelog/os_upgrading/2.17/" + - "/en/open_source/upgrading/2.17/" --- There are no special instructions for upgrading to 2.17.0. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.17.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.18.md b/docs/content/releases/os_upgrading/2.18.md index 01281472bf1..3923476e930 100644 --- a/docs/content/releases/os_upgrading/2.18.md +++ b/docs/content/releases/os_upgrading/2.18.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20230103 description: instructions for helm chart exclude_search: true +aliases: + - "/en/open_source/upgrading/2.18/" --- **Upgrade instructions for helm chart with rabbitMQ enabled**: The rabbitMQ uses a statefulset by default. Before upgrading the helm chart we have to ensure that all queues are empty: diff --git a/docs/content/releases/os_upgrading/2.19.md b/docs/content/releases/os_upgrading/2.19.md index da0c73c3482..3947d78a6ca 100644 --- a/docs/content/releases/os_upgrading/2.19.md +++ b/docs/content/releases/os_upgrading/2.19.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20230206 description: breaking change exclude_search: true +aliases: + - "/changelog/os_upgrading/2.19/" + - "/en/open_source/upgrading/2.19/" --- There are new docker images based on alpine with fewer third party dependencies. Related to the new images the current docker files had to be renamed and have a "-debian" or the new images a "-alpine" at the end. Furthermore there are new docker tags [DefectdojoVersion]-[OS]. For example 2.19.0-alpine or 2.19.0-debian. The currend tags (latest and [DefectdojoVersion]) are still based on the "old" images. Be aware that the new alpine images are not heavily tested and may contain bugs. diff --git a/docs/content/releases/os_upgrading/2.2.md b/docs/content/releases/os_upgrading/2.2.md index 04125b04b5a..4c939c99e8e 100644 --- a/docs/content/releases/os_upgrading/2.2.md +++ b/docs/content/releases/os_upgrading/2.2.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20210831 description: No special instructions. exclude_search: true +aliases: + - "/changelog/os_upgrading/2.2/" + - "/en/open_source/upgrading/2.2/" --- Upgrade to 2.0.0 contained migration of endpoints. Some parts of migration haven't been done properly. This deficiency may manifest as a doubled slash in endpoint URLs (like `http://foo.bar:8080//test`) or as a problem with deduplication diff --git a/docs/content/releases/os_upgrading/2.20.md b/docs/content/releases/os_upgrading/2.20.md index 487cc5f61d5..b70b1b80aa3 100644 --- a/docs/content/releases/os_upgrading/2.20.md +++ b/docs/content/releases/os_upgrading/2.20.md @@ -4,5 +4,7 @@ toc_hide: true weight: -20230306 description: No special instructions. exclude_search: true +aliases: + - "/en/open_source/upgrading/2.20/" --- There are no special instructions for upgrading to 2.20.0. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.20.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.21.md b/docs/content/releases/os_upgrading/2.21.md index b1bc1226ba6..aedf4a6d861 100644 --- a/docs/content/releases/os_upgrading/2.21.md +++ b/docs/content/releases/os_upgrading/2.21.md @@ -4,5 +4,7 @@ toc_hide: true weight: -20230403 description: No special instructions. exclude_search: true +aliases: + - "/en/open_source/upgrading/2.21/" --- There are no special instructions for upgrading to 2.21.0. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.21.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.22.md b/docs/content/releases/os_upgrading/2.22.md index 4cd1e6f1010..62463160c78 100644 --- a/docs/content/releases/os_upgrading/2.22.md +++ b/docs/content/releases/os_upgrading/2.22.md @@ -4,5 +4,7 @@ toc_hide: true weight: -20230501 description: No special instructions. exclude_search: true +aliases: + - "/en/open_source/upgrading/2.22/" --- There are no special instructions for upgrading to 2.22.0. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.22.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.23.md b/docs/content/releases/os_upgrading/2.23.md index 21de2d4347a..b40911f4b59 100644 --- a/docs/content/releases/os_upgrading/2.23.md +++ b/docs/content/releases/os_upgrading/2.23.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20230605 description: breaking change exclude_search: true +aliases: + - "/en/open_source/upgrading/2.23/" --- There is a migration from the legacy Nessus and Nessus WAS parsers to a single Tenable parser. The updated Tenable parser simply merges existing support for Nessus and Nessus WAS without introducing new functionality that could create instability diff --git a/docs/content/releases/os_upgrading/2.24.md b/docs/content/releases/os_upgrading/2.24.md index 33d89c253fa..9467fc61f27 100644 --- a/docs/content/releases/os_upgrading/2.24.md +++ b/docs/content/releases/os_upgrading/2.24.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20230703 description: No special instructions. exclude_search: true +aliases: + - "/en/open_source/upgrading/2.24/" --- There are no special instructions for upgrading to 2.24.0. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.24.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.25.md b/docs/content/releases/os_upgrading/2.25.md index c0865742162..59eb47c96f6 100644 --- a/docs/content/releases/os_upgrading/2.25.md +++ b/docs/content/releases/os_upgrading/2.25.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20230807 description: No special instructions. exclude_search: true +aliases: + - "/en/open_source/upgrading/2.25/" --- There are no special instructions for upgrading to 2.25.0. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.25.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.26.md b/docs/content/releases/os_upgrading/2.26.md index 76c435ec1d6..4500de02b40 100644 --- a/docs/content/releases/os_upgrading/2.26.md +++ b/docs/content/releases/os_upgrading/2.26.md @@ -4,5 +4,7 @@ toc_hide: true weight: -20230905 description: No special instructions. exclude_search: true +aliases: + - "/en/open_source/upgrading/2.26/" --- There are no special instructions for upgrading to 2.26.0. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.26.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.27.md b/docs/content/releases/os_upgrading/2.27.md index 6f77b69feee..c68a30de708 100644 --- a/docs/content/releases/os_upgrading/2.27.md +++ b/docs/content/releases/os_upgrading/2.27.md @@ -4,5 +4,7 @@ toc_hide: true weight: -20231002 description: No special instructions. exclude_search: true +aliases: + - "/en/open_source/upgrading/2.27/" --- There are no special instructions for upgrading to 2.27.0. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.27.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.29.md b/docs/content/releases/os_upgrading/2.29.md index ef0c45f61e2..d726db42d53 100644 --- a/docs/content/releases/os_upgrading/2.29.md +++ b/docs/content/releases/os_upgrading/2.29.md @@ -4,5 +4,7 @@ toc_hide: true weight: -20231110 description: No special instructions. exclude_search: true +aliases: + - "/en/open_source/upgrading/2.29/" --- There are no special instructions for upgrading to 2.29.0. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.29.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.3.md b/docs/content/releases/os_upgrading/2.3.md index 52cccb257a4..627ebcb2053 100644 --- a/docs/content/releases/os_upgrading/2.3.md +++ b/docs/content/releases/os_upgrading/2.3.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20211005 description: No special instructions. exclude_search: true +aliases: + - "/changelog/os_upgrading/2.3/" + - "/en/open_source/upgrading/2.3/" --- There are no special instructions for upgrading to 2.3.0. In 2.3.0 we [changed the default password hashing algorithm to Argon2 (from PBKDF2)](https://github.com/DefectDojo/django-DefectDojo/pull/5205). diff --git a/docs/content/releases/os_upgrading/2.30.md b/docs/content/releases/os_upgrading/2.30.md index 0dbce70253c..49db2506b72 100644 --- a/docs/content/releases/os_upgrading/2.30.md +++ b/docs/content/releases/os_upgrading/2.30.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20231211 description: Breaking Change for Auditlog. exclude_search: true +aliases: + - "/changelog/os_upgrading/2.30/" + - "/en/open_source/upgrading/2.30/" --- There are instructions for upgrading to 2.30.0 if you disabled `enable_auditlog` before (read below). Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.30.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.31.md b/docs/content/releases/os_upgrading/2.31.md index ec5dc9e0635..263d063221e 100644 --- a/docs/content/releases/os_upgrading/2.31.md +++ b/docs/content/releases/os_upgrading/2.31.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20240102 description: breaking change exclude_search: true +aliases: + - "/en/open_source/upgrading/2.31/" --- To continue maintaining the most up to date list of parsers, the following actions have been taken: diff --git a/docs/content/releases/os_upgrading/2.32.md b/docs/content/releases/os_upgrading/2.32.md index adc3f2f29d5..78200a5527e 100644 --- a/docs/content/releases/os_upgrading/2.32.md +++ b/docs/content/releases/os_upgrading/2.32.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20240205 description: Breaking change for Removal of OpenAPI 2.0 Swagger exclude_search: true +aliases: + - "/en/open_source/upgrading/2.32/" --- There are no special instructions for upgrading to 2.32.x. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.32.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.33.md b/docs/content/releases/os_upgrading/2.33.md index 935974da7a2..11382162c3e 100644 --- a/docs/content/releases/os_upgrading/2.33.md +++ b/docs/content/releases/os_upgrading/2.33.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20240304 description: breaking change exclude_search: true +aliases: + - "/changelog/os_upgrading/2.33/" + - "/en/open_source/upgrading/2.33/" --- To continue maintaining the most up to date list of parsers, the following actions have been taken: diff --git a/docs/content/releases/os_upgrading/2.34.md b/docs/content/releases/os_upgrading/2.34.md index 402dd3ba380..2608407a5cf 100644 --- a/docs/content/releases/os_upgrading/2.34.md +++ b/docs/content/releases/os_upgrading/2.34.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20240402 description: Breaking Change for AWS_Scout2. exclude_search: true +aliases: + - "/en/open_source/upgrading/2.34/" --- **Breaking Change** diff --git a/docs/content/releases/os_upgrading/2.35.md b/docs/content/releases/os_upgrading/2.35.md index 3dec987e04e..6980879557e 100644 --- a/docs/content/releases/os_upgrading/2.35.md +++ b/docs/content/releases/os_upgrading/2.35.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20240506 description: Integrity checker announced exclude_search: true +aliases: + - "/en/open_source/upgrading/2.35/" --- From 2.35.0, DefectDojo will perform an integrity check of the `settings.dist.py` file to ensure it has not been modified. If the user changed this file (in the past or even now) the DefectDojo instance will not start until those changes have been reverted. diff --git a/docs/content/releases/os_upgrading/2.36.md b/docs/content/releases/os_upgrading/2.36.md index fd17e263ee2..329d4034ea0 100644 --- a/docs/content/releases/os_upgrading/2.36.md +++ b/docs/content/releases/os_upgrading/2.36.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20240603 description: Breaking Change for HELM deployments with PostgreSQL exclude_search: true +aliases: + - "/en/open_source/upgrading/2.36/" --- Previous HELM deployments (HELM chart `<=1.6.136`, DefectDojo `<=2.35.4`) used a pinned version of PostgreSQL in versions `11.x`. These are incompatible with Django in version `4.2` (used from DefectDojo version `2.36.0`; HELM chart `1.6.137`). Because of this, it is necessary to upgrade PostgreSQL to version `12.x` or higher. DefectDojo in version `2.36.1` (HELM chart `1.6.138`) uses this new version of PostgreSQL. diff --git a/docs/content/releases/os_upgrading/2.37.md b/docs/content/releases/os_upgrading/2.37.md index 9eb0026a5c1..34c8865f05b 100644 --- a/docs/content/releases/os_upgrading/2.37.md +++ b/docs/content/releases/os_upgrading/2.37.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20240701 description: Breaking Change for HELM deployments and MySQL / RabbitMQ users exclude_search: true +aliases: + - "/en/open_source/upgrading/2.37/" --- **Breaking Change** diff --git a/docs/content/releases/os_upgrading/2.38.md b/docs/content/releases/os_upgrading/2.38.md index 6795ff1a9fc..990bf475105 100644 --- a/docs/content/releases/os_upgrading/2.38.md +++ b/docs/content/releases/os_upgrading/2.38.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20240805 description: Breaking Change for HELM deployments exclude_search: true +aliases: + - "/en/open_source/upgrading/2.38/" --- **Breaking Change** diff --git a/docs/content/releases/os_upgrading/2.39.md b/docs/content/releases/os_upgrading/2.39.md index 23305729bc6..fd20391dbb6 100644 --- a/docs/content/releases/os_upgrading/2.39.md +++ b/docs/content/releases/os_upgrading/2.39.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20240903 description: Major upgrade of Postgres 16 to 17 exclude_search: true +aliases: + - "/changelog/os_upgrading/2.39/" + - "/en/open_source/upgrading/2.39/" --- # PostgreSQL Major Version Upgrade in Docker Compose diff --git a/docs/content/releases/os_upgrading/2.4.md b/docs/content/releases/os_upgrading/2.4.md index 0a8c4578e47..e94beea0f73 100644 --- a/docs/content/releases/os_upgrading/2.4.md +++ b/docs/content/releases/os_upgrading/2.4.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20211102 description: security Release exclude_search: true +aliases: + - "/changelog/os_upgrading/2.4/" + - "/en/open_source/upgrading/2.4/" --- This releases fixes a High severity vulnerability for which the details will be disclosed on November 16th in [GHSA-fwg9-752c-qh8w](https://github.com/DefectDojo/django-DefectDojo/security/advisories/GHSA-fwg9-752c-qh8w) diff --git a/docs/content/releases/os_upgrading/2.40.md b/docs/content/releases/os_upgrading/2.40.md index ca7039a13cd..ccd1981fd88 100644 --- a/docs/content/releases/os_upgrading/2.40.md +++ b/docs/content/releases/os_upgrading/2.40.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20241007 description: Breaking Change for Postgres 12. exclude_search: true +aliases: + - "/changelog/os_upgrading/2.40/" + - "/en/open_source/upgrading/2.40/" --- With the upgrade to Django 5.1.x, Posgres 12 will no longer be supported. Please make plans to upgrade to a later version of Postrges before upgrading to version 2.40.0 of DefectDojo. To determine which version of Postgres to target, please refer to the [end of life version schedule](https://endoflife.date/postgresql) diff --git a/docs/content/releases/os_upgrading/2.41.md b/docs/content/releases/os_upgrading/2.41.md index 24dfc066631..caf91b740f9 100644 --- a/docs/content/releases/os_upgrading/2.41.md +++ b/docs/content/releases/os_upgrading/2.41.md @@ -4,5 +4,8 @@ toc_hide: true weight: -20241104 description: No special instructions. exclude_search: true +aliases: + - "/changelog/os_upgrading/2.41/" + - "/en/open_source/upgrading/2.41/" --- There are no special instructions for upgrading to 2.41.x. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.41.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.42.md b/docs/content/releases/os_upgrading/2.42.md index 0a65108e96e..6ff4a10f11d 100644 --- a/docs/content/releases/os_upgrading/2.42.md +++ b/docs/content/releases/os_upgrading/2.42.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20241202 description: No special instructions. exclude_search: true +aliases: + - "/en/open_source/upgrading/2.42/" --- **Hash Code changes** diff --git a/docs/content/releases/os_upgrading/2.43.md b/docs/content/releases/os_upgrading/2.43.md index edeb2c3d132..074da7370bf 100644 --- a/docs/content/releases/os_upgrading/2.43.md +++ b/docs/content/releases/os_upgrading/2.43.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20250106 description: Disclaimer field renamed/split, removal of `dc-` scripts, audit log updates, and hash codes updates. exclude_search: true +aliases: + - "/en/open_source/upgrading/2.43/" --- ### Audit log migration diff --git a/docs/content/releases/os_upgrading/2.44.1.md b/docs/content/releases/os_upgrading/2.44.1.md index 97e2c6b28e3..622651f6bf2 100644 --- a/docs/content/releases/os_upgrading/2.44.1.md +++ b/docs/content/releases/os_upgrading/2.44.1.md @@ -3,6 +3,9 @@ title: 'Upgrading to DefectDojo Version 2.44.1' toc_hide: true weight: -20250203 description: No special instructions. +aliases: + - "/changelog/os_upgrading/2.44.1/" + - "/en/open_source/upgrading/2.44.1/" --- ### AWS Parser Endpoint Migrations diff --git a/docs/content/releases/os_upgrading/2.44.md b/docs/content/releases/os_upgrading/2.44.md index 2fd93827afb..53f54fd5c30 100644 --- a/docs/content/releases/os_upgrading/2.44.md +++ b/docs/content/releases/os_upgrading/2.44.md @@ -3,6 +3,8 @@ title: 'Upgrading to DefectDojo Version 2.44.0' toc_hide: true weight: -20250203 description: No special instructions. +aliases: + - "/changelog/os_upgrading/2.44/" --- ### Hash Code changes diff --git a/docs/content/releases/os_upgrading/2.45.md b/docs/content/releases/os_upgrading/2.45.md index 91d75e20110..cfed6170148 100644 --- a/docs/content/releases/os_upgrading/2.45.md +++ b/docs/content/releases/os_upgrading/2.45.md @@ -3,6 +3,9 @@ title: 'Upgrading to DefectDojo Version 2.45.x' toc_hide: true weight: -20250303 description: No special instructions. +aliases: + - "/changelog/os_upgrading/2.45/" + - "/en/open_source/upgrading/2.45/" --- There are no special instructions for upgrading to 2.45.x. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.45.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.46.md b/docs/content/releases/os_upgrading/2.46.md index 433bedaf9c2..4a851501660 100644 --- a/docs/content/releases/os_upgrading/2.46.md +++ b/docs/content/releases/os_upgrading/2.46.md @@ -3,6 +3,8 @@ title: 'Upgrading to DefectDojo Version 2.46.x' toc_hide: true weight: -20250407 description: Tag Formatting Changes + Import Payload Changes +aliases: + - "/en/open_source/upgrading/2.46/" --- diff --git a/docs/content/releases/os_upgrading/2.47.md b/docs/content/releases/os_upgrading/2.47.md index 9472ed1c6ea..affbcf4e9f8 100644 --- a/docs/content/releases/os_upgrading/2.47.md +++ b/docs/content/releases/os_upgrading/2.47.md @@ -3,6 +3,8 @@ title: 'Upgrading to DefectDojo Version 2.47.x' toc_hide: true weight: -20250505 description: Drop support for PostgreSQL-HA in HELM +aliases: + - "/en/open_source/upgrading/2.47/" --- ### Drop support for PostgreSQL-HA in HELM diff --git a/docs/content/releases/os_upgrading/2.48.2.md b/docs/content/releases/os_upgrading/2.48.2.md index 468fe636362..08713325b8a 100644 --- a/docs/content/releases/os_upgrading/2.48.2.md +++ b/docs/content/releases/os_upgrading/2.48.2.md @@ -3,6 +3,8 @@ title: 'Upgrading to DefectDojo Version 2.48.2' toc_hide: true weight: -20250602 description: Tag invalid character cleanup +aliases: + - "/en/open_source/upgrading/2.48.2/" --- ## Tag Formatting Update diff --git a/docs/content/releases/os_upgrading/2.48.md b/docs/content/releases/os_upgrading/2.48.md index 8d992f9d90a..b9c4e4de0fe 100644 --- a/docs/content/releases/os_upgrading/2.48.md +++ b/docs/content/releases/os_upgrading/2.48.md @@ -3,6 +3,8 @@ title: 'Upgrading to DefectDojo Version 2.48.x' toc_hide: true weight: -20250602 description: Better pushing to JIRA for Finding Groups +aliases: + - "/en/open_source/upgrading/2.48/" --- ## Finding Group JIRA Issue template changes diff --git a/docs/content/releases/os_upgrading/2.49.md b/docs/content/releases/os_upgrading/2.49.md index 188201bbb88..30d52b6682d 100644 --- a/docs/content/releases/os_upgrading/2.49.md +++ b/docs/content/releases/os_upgrading/2.49.md @@ -3,5 +3,8 @@ title: 'Upgrading to DefectDojo Version 2.49.x' toc_hide: true weight: -20250707 description: No special instructions. +aliases: + - "/changelog/os_upgrading/2.49/" + - "/en/open_source/upgrading/2.49/" --- There are no special instructions for upgrading to 2.49.x. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.49.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.5.md b/docs/content/releases/os_upgrading/2.5.md index 64ec398127e..7e2e4007142 100644 --- a/docs/content/releases/os_upgrading/2.5.md +++ b/docs/content/releases/os_upgrading/2.5.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20211208 description: legacy authorization removed exclude_search: true +aliases: + - "/en/open_source/upgrading/2.5/" --- Legacy authorization has been completely removed with version 2.5.0. This includes removal of the migration of users to the new authorization as described in https://documentation.defectdojo.com/getting_started/upgrading/#authorization. diff --git a/docs/content/releases/os_upgrading/2.50.md b/docs/content/releases/os_upgrading/2.50.md index 289f833a03f..d8c19e4d89d 100644 --- a/docs/content/releases/os_upgrading/2.50.md +++ b/docs/content/releases/os_upgrading/2.50.md @@ -3,6 +3,8 @@ title: 'Upgrading to DefectDojo Version 2.50.x' toc_hide: true weight: -20250804 description: Dropped support for time_zone in System settings. +aliases: + - "/en/open_source/upgrading/2.50/" --- To simplify the management of the DefectDojo application, it is not necessary to set the time zone in two places (environmental variables and system settings). From now on, environmental variable is supported. diff --git a/docs/content/releases/os_upgrading/2.51.md b/docs/content/releases/os_upgrading/2.51.md index af056256798..14f08452269 100644 --- a/docs/content/releases/os_upgrading/2.51.md +++ b/docs/content/releases/os_upgrading/2.51.md @@ -3,6 +3,8 @@ title: "Upgrading to DefectDojo Version 2.51.x" toc_hide: true weight: -20250902 description: Helm chart changes and Postgres major version updates. +aliases: + - "/en/open_source/upgrading/2.51/" --- ## Performance improvements diff --git a/docs/content/releases/os_upgrading/2.52.md b/docs/content/releases/os_upgrading/2.52.md index 8ed5e6f3c9e..650e6226792 100644 --- a/docs/content/releases/os_upgrading/2.52.md +++ b/docs/content/releases/os_upgrading/2.52.md @@ -3,6 +3,8 @@ title: 'Upgrading to DefectDojo Version 2.52.x' toc_hide: true weight: -20251006 description: Replaced Redis with Valkey & Helm chart changes & MobSF parser merge +aliases: + - "/en/open_source/upgrading/2.52/" --- ## Fix UI overwriting service field from parsers diff --git a/docs/content/releases/os_upgrading/2.53.md b/docs/content/releases/os_upgrading/2.53.md index 13f07f2f5dc..18f45b68f4d 100644 --- a/docs/content/releases/os_upgrading/2.53.md +++ b/docs/content/releases/os_upgrading/2.53.md @@ -3,6 +3,8 @@ title: "Upgrading to DefectDojo Version 2.53.x" toc_hide: true weight: -20251103 description: "Helm chart: changes for initializer annotations + Replaced Redis with Valkey + HPA & PDB support + Batch Deduplication" +aliases: + - "/changelog/os_upgrading/2.53/" --- ## Helm Chart Changes diff --git a/docs/content/releases/os_upgrading/2.54.3.md b/docs/content/releases/os_upgrading/2.54.3.md index 515192579a4..16164cb68e4 100644 --- a/docs/content/releases/os_upgrading/2.54.3.md +++ b/docs/content/releases/os_upgrading/2.54.3.md @@ -3,6 +3,8 @@ title: 'Upgrading to DefectDojo Version 2.54.3' toc_hide: true weight: -20250602 description: Trivy parser deduplication +aliases: + - "/changelog/os_upgrading/2.54.3/" --- ## Trivy parser deduplication diff --git a/docs/content/releases/os_upgrading/2.54.md b/docs/content/releases/os_upgrading/2.54.md index 3992fab2c4b..0c5670125cc 100644 --- a/docs/content/releases/os_upgrading/2.54.md +++ b/docs/content/releases/os_upgrading/2.54.md @@ -3,6 +3,8 @@ title: 'Upgrading to DefectDojo Version 2.54.x' toc_hide: true weight: -20251226 description: Removal of django-auditlog & Dropped support for DD_PARSER_EXCLUDE & Reimport performance improvements & Removal of Finding Template Matching +aliases: + - "/en/open_source/upgrading/2.54/" --- ## Breaking Change: Removal of django-auditlog diff --git a/docs/content/releases/os_upgrading/2.55.md b/docs/content/releases/os_upgrading/2.55.md index 90df965950d..414e42755ee 100644 --- a/docs/content/releases/os_upgrading/2.55.md +++ b/docs/content/releases/os_upgrading/2.55.md @@ -3,6 +3,8 @@ title: 'Upgrading to DefectDojo Version 2.55.x' toc_hide: true weight: -20260105 description: Authorization related optimizations +aliases: + - "/en/open_source/upgrading/2.55/" --- ## Authorization related optimizations diff --git a/docs/content/releases/os_upgrading/2.56.md b/docs/content/releases/os_upgrading/2.56.md index 59d3171af47..80f0e76fc38 100644 --- a/docs/content/releases/os_upgrading/2.56.md +++ b/docs/content/releases/os_upgrading/2.56.md @@ -3,6 +3,8 @@ title: 'Upgrading to DefectDojo Version 2.56.x' toc_hide: true weight: -20260215 description: Deprecation of Questionnaire API Endpoints +aliases: + - "/en/open_source/upgrading/2.56/" --- ## Deprecation: Questionnaire API Endpoints diff --git a/docs/content/releases/os_upgrading/2.57.md b/docs/content/releases/os_upgrading/2.57.md index a7956a0900d..0cda3350208 100644 --- a/docs/content/releases/os_upgrading/2.57.md +++ b/docs/content/releases/os_upgrading/2.57.md @@ -3,6 +3,8 @@ title: 'Upgrading to DefectDojo Version 2.57.x' toc_hide: true weight: -20260406 description: Deprecation of Credential Manager and Stub Findings +aliases: + - "/en/open_source/upgrading/2.57/" --- ## Deprecation: Credential Manager diff --git a/docs/content/releases/os_upgrading/2.6.md b/docs/content/releases/os_upgrading/2.6.md index bc27707a929..5abeece6d5a 100644 --- a/docs/content/releases/os_upgrading/2.6.md +++ b/docs/content/releases/os_upgrading/2.6.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20220104 description: No special instructions. exclude_search: true +aliases: + - "/en/open_source/upgrading/2.6/" --- There are no special instructions for upgrading to 2.6.0. Check the [Release Notes](https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.6.0) for the contents of the release. diff --git a/docs/content/releases/os_upgrading/2.7.md b/docs/content/releases/os_upgrading/2.7.md index aa1ef6cba96..5a44d16dd25 100644 --- a/docs/content/releases/os_upgrading/2.7.md +++ b/docs/content/releases/os_upgrading/2.7.md @@ -4,6 +4,9 @@ toc_hide: true weight: -20220201 description: breaking change exclude_search: true +aliases: + - "/changelog/os_upgrading/2.7/" + - "/en/open_source/upgrading/2.7/" --- This release is a breaking change regarding the Choctaw Hog parser. As the maintainers of this project unified multiple parsers under the RustyHog parser, we now support the parsing of Choctaw Hog JSON output files through the Rusty Hog parser. Furthermore, we also support Gottingen Hog and Essex Hog JSON output files with the RustyHog parser. diff --git a/docs/content/releases/os_upgrading/2.8.md b/docs/content/releases/os_upgrading/2.8.md index bbc826c6042..d62cd258aa0 100644 --- a/docs/content/releases/os_upgrading/2.8.md +++ b/docs/content/releases/os_upgrading/2.8.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20220301 description: breaking changes exclude_search: true +aliases: + - "/en/open_source/upgrading/2.8/" --- **Breaking change for Docker Compose:** Starting DefectDojo with Docker Compose now supports 2 databases (MySQL and PostgreSQL) and 2 celery brokers (RabbitMQ and Redis). To make this possible, docker-compose needs to be started with the parameters `--profile` and `--env-file`. You can get more information in [Setup via Docker Compose - Profiles](https://github.com/DefectDojo/django-DefectDojo/blob/master/readme-docs/DOCKER.md#setup-via-docker-compose---profiles). The profile `mysql-rabbitmq` provides the same configuration as in previous releases. With this the prerequisites have changed as well: Docker requires at least version 19.03.0 and Docker Compose 1.28.0. diff --git a/docs/content/releases/os_upgrading/2.9.md b/docs/content/releases/os_upgrading/2.9.md index 06951ecf528..4c727d86fba 100644 --- a/docs/content/releases/os_upgrading/2.9.md +++ b/docs/content/releases/os_upgrading/2.9.md @@ -4,6 +4,8 @@ toc_hide: true weight: -20220406 description: breaking change for APIv2 exclude_search: true +aliases: + - "/en/open_source/upgrading/2.9/" --- **Breaking change for APIv2:** `configuration_url` was removed from API endpoint `/api/v2/tool_configurations/` due to redundancy. diff --git a/docs/content/releases/os_upgrading/_index.md b/docs/content/releases/os_upgrading/_index.md index 54683be09d2..35301736d20 100644 --- a/docs/content/releases/os_upgrading/_index.md +++ b/docs/content/releases/os_upgrading/_index.md @@ -4,4 +4,7 @@ description: "Release specific upgrading instructions" draft: false weight: 2 audience: opensource +aliases: + - "/changelog/os_upgrading/" + - "/releases/os_upgrading/2.59/" --- diff --git a/docs/content/releases/os_upgrading/upgrading_guide.md b/docs/content/releases/os_upgrading/upgrading_guide.md index cd3ff2542c2..e27f4efe8eb 100644 --- a/docs/content/releases/os_upgrading/upgrading_guide.md +++ b/docs/content/releases/os_upgrading/upgrading_guide.md @@ -6,6 +6,10 @@ sidebar: collapsed: true weight: -900000000 aliases: + - "/changelog/os_upgrading/upgrading_guide/" + - "/en/open_source/upgrading/upgrading_guide" + - "/en/open_source/upgrading/upgrading_guide/" + - "/releases/os_upgrading/2.52/upgrading_guide" - /en/open_source/upgrading/ --- diff --git a/docs/content/releases/pro/changelog.md b/docs/content/releases/pro/changelog.md index 1d432986b7b..37b28b26797 100644 --- a/docs/content/releases/pro/changelog.md +++ b/docs/content/releases/pro/changelog.md @@ -3,7 +3,8 @@ title: "DefectDojo Pro Changelog" description: "DefectDojo Changelog" exclude_search: true aliases: - - /changelog/pro_changelog/ + - "/en/changelog/changelog/" + - "/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. @@ -366,7 +367,7 @@ Additional features: ### Mar 5, 2026: v2.56.0 * **(API)** Restricted Note Types are now accessible via the API. -* **(Connectors)** Added **IriusRisk** connector: see [tools reference](/en/connecting_your_tools/connectors/connectors_tool_reference/) for configuration instructions. +* **(Connectors)** Added **IriusRisk** connector: see [tools reference](/connectors/upstream/toolreference/) for configuration instructions. * **(SAML)** SAML settings now support optional group attributes, allowing configurations that don't provide group mappings to work without errors. * **(SMTP)** Fixed an issue where DefectDojo would attempt SMTP authentication even when no credentials were configured, which could cause email delivery failures. * **(Universal Parser)** The Universal Parser now falls back to `clevercsv` for non-standard or malformed CSV files, improving compatibility with edge-case scanner outputs. @@ -689,7 +690,7 @@ The Priority Insights dashboard can quickly render a list of all SOC or AppSec F - **(Calendar)** New filters have been added to Calendar view: Unassigned Lead, and Engagement/Test Type. - **(Dashboard)** Added Finding Status filter for Dashboard tiles. -- **(Engagements)** A repository URI can be added to an Engagement via **Edit Engagement > Optional Fields > Repo**. If this field is set, Findings under that Engagement will automatically generate clickable links to the source code if File Path is set on the Finding. See [docs](/en/working_with_findings/organizing_engagements_tests/source-code-repositories/) for more details. +- **(Engagements)** A repository URI can be added to an Engagement via **Edit Engagement > Optional Fields > Repo**. If this field is set, Findings under that Engagement will automatically generate clickable links to the source code if File Path is set on the Finding. See [docs](/asset_modelling/OS_hierarchy/OS__source-code-repositories/) for more details. - **(Findings)** Added "Jira Issue URL" column to the CSV export of Finding tables. - **(Metrics)** Priority Dashboard has been added to Metrics, to display your organization's risk profile at a glance. ![image](images/pro_dashboard_priority.png) @@ -732,7 +733,7 @@ Hotfix release - no significant feature changes. #### Apr 14, 2025: v2.45.1 -- **(Connectors)** Added a Connector for Wiz: see [tools reference](/en/connecting_your_tools/connectors/connectors_tool_reference/) for configuration instructions. +- **(Connectors)** Added a Connector for Wiz: see [tools reference](/connectors/upstream/toolreference/) for configuration instructions. #### Apr 7, 2025: v2.45.0 @@ -744,7 +745,7 @@ Hotfix release - no significant feature changes. #### Mar 31, 2025: v2.44.4 -- **(Pro UI)** Group and Configuration permissions can now be assigned quickly from a User page. For more information, see [DefectDojo Pro Permissions](/en/customize_dojo/user_management/pro_permissions_overhaul/). +- **(Pro UI)** Group and Configuration permissions can now be assigned quickly from a User page. For more information, see [DefectDojo Pro Permissions](/admin/user_management/pro_permissions_overhaul/). #### Mar 24, 2025: v2.44.3 @@ -752,7 +753,7 @@ Hotfix release - no significant feature changes. #### Mar 17, 2025: v2.44.2 -- **(Pro UI)** Added a new method to quickly assign permissions to Products or Product Types. See our [Pro Permissions](/en/customize_dojo/user_management/pro_permissions_overhaul/) for more details. +- **(Pro UI)** Added a new method to quickly assign permissions to Products or Product Types. See our [Pro Permissions](/admin/user_management/pro_permissions_overhaul/) for more details. ![image](images/pro_permissions_2.png) diff --git a/docs/content/supported_tools/_index.md b/docs/content/supported_tools/_index.md index 39ca7631241..b5687251050 100644 --- a/docs/content/supported_tools/_index.md +++ b/docs/content/supported_tools/_index.md @@ -14,6 +14,9 @@ cascade: _target: path: "/**" exclude_search: true +aliases: + - "/en/connecting_your_tools" + - "/en/connecting_your_tools/" --- DefectDojo can parse data from 500+ security reports and counting. diff --git a/docs/content/supported_tools/parsers/_index.md b/docs/content/supported_tools/parsers/_index.md index e3890b6e60e..037d1831fce 100644 --- a/docs/content/supported_tools/parsers/_index.md +++ b/docs/content/supported_tools/parsers/_index.md @@ -14,6 +14,8 @@ cascade: _target: path: "/**" exclude_search: true +aliases: + - "/en/connecting_your_tools/parsers/" --- DefectDojo can parse data from 500+ security reports and counting. diff --git a/docs/content/supported_tools/parsers/api/bugcrowd.md b/docs/content/supported_tools/parsers/api/bugcrowd.md index 2e6c4b919cb..5e5e9667210 100644 --- a/docs/content/supported_tools/parsers/api/bugcrowd.md +++ b/docs/content/supported_tools/parsers/api/bugcrowd.md @@ -1,6 +1,8 @@ --- title: "Bugcrowd API" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/api/bugcrowd/" --- > **⚠️ Deprecated — removed in DefectDojo 3.5.0.** > diff --git a/docs/content/supported_tools/parsers/api/sonarqube.md b/docs/content/supported_tools/parsers/api/sonarqube.md index b415eea3d9b..a7005ebeb91 100644 --- a/docs/content/supported_tools/parsers/api/sonarqube.md +++ b/docs/content/supported_tools/parsers/api/sonarqube.md @@ -1,6 +1,8 @@ --- title: "SonarQube API Import" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/api/sonarqube/" --- > **⚠️ Deprecated — removed in DefectDojo 3.5.0.** > diff --git a/docs/content/supported_tools/parsers/file/_index.md b/docs/content/supported_tools/parsers/file/_index.md index e57a364319e..02035fca51a 100644 --- a/docs/content/supported_tools/parsers/file/_index.md +++ b/docs/content/supported_tools/parsers/file/_index.md @@ -6,4 +6,6 @@ chapter: true sidebar: collapsed: true exclude_search: true +aliases: + - "/en/connecting_your_tools/parsers/file/" --- diff --git a/docs/content/supported_tools/parsers/file/acunetix.md b/docs/content/supported_tools/parsers/file/acunetix.md index 4c325e5699d..fb0062a0b3f 100644 --- a/docs/content/supported_tools/parsers/file/acunetix.md +++ b/docs/content/supported_tools/parsers/file/acunetix.md @@ -8,7 +8,7 @@ This parser imports the Acunetix Scanner with xml output or Acunetix 360 Scanner Sample Acunetix Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/acunetix). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/anchore_engine.md b/docs/content/supported_tools/parsers/file/anchore_engine.md index b029cbf7c47..3e200921bbe 100644 --- a/docs/content/supported_tools/parsers/file/anchore_engine.md +++ b/docs/content/supported_tools/parsers/file/anchore_engine.md @@ -1,6 +1,8 @@ --- title: "Anchore Enterprise Vulnerability" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/anchore_engine/" --- ### File Types @@ -43,7 +45,7 @@ All properties are strings and are required by the parser. As the parser evolved Sample Anchore-Engine scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/anchore_engine) ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/anchore_enterprise.md b/docs/content/supported_tools/parsers/file/anchore_enterprise.md index c03de42f4a7..c6467840435 100644 --- a/docs/content/supported_tools/parsers/file/anchore_enterprise.md +++ b/docs/content/supported_tools/parsers/file/anchore_enterprise.md @@ -8,7 +8,7 @@ Anchore-CLI JSON policy check report format. Sample Anchore Enterprise Policy Check scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/anchore_enterprise). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/anchore_grype.md b/docs/content/supported_tools/parsers/file/anchore_grype.md index 5bc9da148ff..5e80da5293a 100644 --- a/docs/content/supported_tools/parsers/file/anchore_grype.md +++ b/docs/content/supported_tools/parsers/file/anchore_grype.md @@ -1,6 +1,8 @@ --- title: "Anchore Grype" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/anchore_grype/" --- ### File Types DefectDojo parser accepts a .json file. @@ -197,7 +199,7 @@ All properties are expected as strings and are required by the parser. Sample Grype scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/anchore_grype). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/anchorectl_policies.md b/docs/content/supported_tools/parsers/file/anchorectl_policies.md index 98c131fcde2..3b7294dd39b 100644 --- a/docs/content/supported_tools/parsers/file/anchorectl_policies.md +++ b/docs/content/supported_tools/parsers/file/anchorectl_policies.md @@ -17,7 +17,7 @@ anchorectl policy evaluate -o json > policy_report.json Sample AnchoreCTL Policies Report scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/anchorectl_policies). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/anchorectl_vulns.md b/docs/content/supported_tools/parsers/file/anchorectl_vulns.md index 0f7f851a32f..49fc561d269 100644 --- a/docs/content/supported_tools/parsers/file/anchorectl_vulns.md +++ b/docs/content/supported_tools/parsers/file/anchorectl_vulns.md @@ -8,7 +8,7 @@ AnchoreCTLs JSON vulnerability report format Sample AnchoreCTL Vuln Report scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/anchorectl_vulns). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/appcheck_web_application_scanner.md b/docs/content/supported_tools/parsers/file/appcheck_web_application_scanner.md index 2ae5431594b..a10e8412130 100644 --- a/docs/content/supported_tools/parsers/file/appcheck_web_application_scanner.md +++ b/docs/content/supported_tools/parsers/file/appcheck_web_application_scanner.md @@ -8,7 +8,7 @@ Accepts AppCheck Web Application Scanner output in .json format. Sample AppCheck Web Application Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/appcheck_web_application_scanner). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/appspider.md b/docs/content/supported_tools/parsers/file/appspider.md index 26485369d00..c2e208486a4 100644 --- a/docs/content/supported_tools/parsers/file/appspider.md +++ b/docs/content/supported_tools/parsers/file/appspider.md @@ -9,7 +9,7 @@ download. Sample AppSpider (Rapid7) scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/appspider). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/aqua.md b/docs/content/supported_tools/parsers/file/aqua.md index c2d48757d34..e6127df1e6f 100644 --- a/docs/content/supported_tools/parsers/file/aqua.md +++ b/docs/content/supported_tools/parsers/file/aqua.md @@ -38,7 +38,7 @@ Those JSON files will only list vulnerabilities. Thus, DefectDojo parser will no Sample Aqua scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/aqua). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - severity - vulnerability ids diff --git a/docs/content/supported_tools/parsers/file/arachni.md b/docs/content/supported_tools/parsers/file/arachni.md index 1f76e78af8a..008a0bb564d 100644 --- a/docs/content/supported_tools/parsers/file/arachni.md +++ b/docs/content/supported_tools/parsers/file/arachni.md @@ -13,7 +13,7 @@ arachni_reporter --reporter 'json' js.com.afr ### Sample Scan Data Sample Arachni Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/arachni). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/asff.md b/docs/content/supported_tools/parsers/file/asff.md index 9c6c27d3e6d..6756b42730e 100644 --- a/docs/content/supported_tools/parsers/file/asff.md +++ b/docs/content/supported_tools/parsers/file/asff.md @@ -13,7 +13,7 @@ Prowler tool can generate this format with option `-M json-asff`. Sample AWS Security Finding Format (ASFF) scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/asff). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/auditjs.md b/docs/content/supported_tools/parsers/file/auditjs.md index d3fcd3843f1..45dbe009aca 100644 --- a/docs/content/supported_tools/parsers/file/auditjs.md +++ b/docs/content/supported_tools/parsers/file/auditjs.md @@ -12,7 +12,7 @@ auditjs ossi --json > auditjs_report.json Sample AuditJS (OSSIndex) scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/auditjs). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/aws_inspector2.md b/docs/content/supported_tools/parsers/file/aws_inspector2.md index c53685e79b3..eadea8af5db 100644 --- a/docs/content/supported_tools/parsers/file/aws_inspector2.md +++ b/docs/content/supported_tools/parsers/file/aws_inspector2.md @@ -1,6 +1,8 @@ --- title: "AWS Inspector2 Scanner" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/aws_inspector2/" --- ### File Types @@ -24,7 +26,7 @@ Detailed API response format can be obtained [here](https://docs.aws.amazon.com/ Sample AWS Inspector2 findings can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/aws_inspector2). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/aws_prowler.md b/docs/content/supported_tools/parsers/file/aws_prowler.md index b501d37bc80..263b5f24f46 100644 --- a/docs/content/supported_tools/parsers/file/aws_prowler.md +++ b/docs/content/supported_tools/parsers/file/aws_prowler.md @@ -1,6 +1,8 @@ --- title: "AWS Prowler Scanner" toc_hide: true +aliases: + - "/supported_tools/file/aws_prowler/" --- Prowler file can be imported as a CSV (`-M csv`) or JSON (`-M json`) file. @@ -8,7 +10,7 @@ Prowler file can be imported as a CSV (`-M csv`) or JSON (`-M json`) file. Sample AWS Prowler Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/aws_prowler). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/aws_prowler_v3plus.md b/docs/content/supported_tools/parsers/file/aws_prowler_v3plus.md index 262cca650a0..6b2437eb6f0 100644 --- a/docs/content/supported_tools/parsers/file/aws_prowler_v3plus.md +++ b/docs/content/supported_tools/parsers/file/aws_prowler_v3plus.md @@ -163,7 +163,7 @@ The parser expects an array of assessments. All properties are strings and are r Unit tests of AWS Prowler v3 JSON and Prowler v4 JSON-OCSF can be found at https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/aws_prowler_v3. ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/awssecurityhub.md b/docs/content/supported_tools/parsers/file/awssecurityhub.md index 454394e75da..105e04e2824 100644 --- a/docs/content/supported_tools/parsers/file/awssecurityhub.md +++ b/docs/content/supported_tools/parsers/file/awssecurityhub.md @@ -1,6 +1,8 @@ --- title: "AWS Security Hub" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/awssecurityhub/" --- ### File Types This DefectDojo parser accepts JSON files from AWS Security Hub. The JSON reports can be created from the [AWS Security Hub CLI](https://docs.aws.amazon.com/cli/latest/reference/securityhub/get-findings.html) using the following command: `aws securityhub get-findings`. @@ -22,7 +24,7 @@ AWS Security Hub Parser does import the affected service ARNs as hosts to Defect Sample scan data for testing purposes can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/awssecurityhub). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/azure_security_center_recommendations.md b/docs/content/supported_tools/parsers/file/azure_security_center_recommendations.md index 5d5aa295403..00f9189462d 100644 --- a/docs/content/supported_tools/parsers/file/azure_security_center_recommendations.md +++ b/docs/content/supported_tools/parsers/file/azure_security_center_recommendations.md @@ -8,7 +8,7 @@ Azure Security Center recommendations can be exported from the user interface in Sample Azure Security Center Recommendations Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/azure_security_center_recommendations). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/bandit.md b/docs/content/supported_tools/parsers/file/bandit.md index 282e0e84b55..3b065226b6f 100644 --- a/docs/content/supported_tools/parsers/file/bandit.md +++ b/docs/content/supported_tools/parsers/file/bandit.md @@ -1,6 +1,8 @@ --- title: "Bandit" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/bandit/" --- ### File Types @@ -67,7 +69,7 @@ All properties are expected as strings, except "metrics" properties, which are e Sample Bandit scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/bandit). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - file path - line diff --git a/docs/content/supported_tools/parsers/file/bearer_cli.md b/docs/content/supported_tools/parsers/file/bearer_cli.md index 458a89ae994..38a47f79c03 100644 --- a/docs/content/supported_tools/parsers/file/bearer_cli.md +++ b/docs/content/supported_tools/parsers/file/bearer_cli.md @@ -13,7 +13,7 @@ See Bearer documentation: https://docs.bearer.com/reference/commands/ Sample Bearer scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/bearer). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/blackduck.md b/docs/content/supported_tools/parsers/file/blackduck.md index d358fdfd330..fa16d116147 100644 --- a/docs/content/supported_tools/parsers/file/blackduck.md +++ b/docs/content/supported_tools/parsers/file/blackduck.md @@ -14,7 +14,7 @@ information. Sample Blackduck Hub scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/blackduck). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - vulnerability ids diff --git a/docs/content/supported_tools/parsers/file/blackduck_binary_analysis.md b/docs/content/supported_tools/parsers/file/blackduck_binary_analysis.md index 6206f08ae68..01cfa661977 100644 --- a/docs/content/supported_tools/parsers/file/blackduck_binary_analysis.md +++ b/docs/content/supported_tools/parsers/file/blackduck_binary_analysis.md @@ -23,7 +23,7 @@ Black Duck Binary Analysis can also detect if sensitive information like email a Sample Blackduck Binary Analysis scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/blackduck_binary_analysis). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/blackduck_component_risk.md b/docs/content/supported_tools/parsers/file/blackduck_component_risk.md index 64787c4fa6c..0846de0ce45 100644 --- a/docs/content/supported_tools/parsers/file/blackduck_component_risk.md +++ b/docs/content/supported_tools/parsers/file/blackduck_component_risk.md @@ -8,7 +8,7 @@ Upload the zip file containing the security.csv and files.csv. Sample Blackduck Component Risk scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/blackduck_component_risk). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/brakeman.md b/docs/content/supported_tools/parsers/file/brakeman.md index 0c247c8f631..287e6e25d62 100644 --- a/docs/content/supported_tools/parsers/file/brakeman.md +++ b/docs/content/supported_tools/parsers/file/brakeman.md @@ -8,7 +8,7 @@ Import Brakeman Scanner findings in JSON format. Sample Brakeman Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/brakeman). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/bugcrowd.md b/docs/content/supported_tools/parsers/file/bugcrowd.md index 4339d6a9874..4abe7843df9 100644 --- a/docs/content/supported_tools/parsers/file/bugcrowd.md +++ b/docs/content/supported_tools/parsers/file/bugcrowd.md @@ -8,7 +8,7 @@ Import Bugcrowd results in CSV format. Sample Bugcrowd scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/bugcrowd). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/bundler_audit.md b/docs/content/supported_tools/parsers/file/bundler_audit.md index 92e6e50519a..bff8d41075d 100644 --- a/docs/content/supported_tools/parsers/file/bundler_audit.md +++ b/docs/content/supported_tools/parsers/file/bundler_audit.md @@ -8,7 +8,7 @@ Import the text output generated with bundle-audit check Sample Bundler-Audit scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/bundler_audit). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/burp.md b/docs/content/supported_tools/parsers/file/burp.md index 8491d1a0cef..71a6fa0938e 100644 --- a/docs/content/supported_tools/parsers/file/burp.md +++ b/docs/content/supported_tools/parsers/file/burp.md @@ -1,6 +1,9 @@ --- title: "Burp XML" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/burp/" + - "/supported_tools/file/burp/" --- ### File Types DefectDojo parser accepts Burp Issue data as an .xml file. @@ -44,7 +47,7 @@ All XML elements are required and will be parsed as strings. Sample Burp scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/burp). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/burp_api.md b/docs/content/supported_tools/parsers/file/burp_api.md index 55fdfe15705..c2a48517a8e 100644 --- a/docs/content/supported_tools/parsers/file/burp_api.md +++ b/docs/content/supported_tools/parsers/file/burp_api.md @@ -8,7 +8,7 @@ Import Burp REST API scan data in JSON format (/scan/[task_id] endpoint). Sample Burp REST API scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/burp_api). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/burp_dastardly.md b/docs/content/supported_tools/parsers/file/burp_dastardly.md index 74d158dfff5..e96eb5a98fb 100644 --- a/docs/content/supported_tools/parsers/file/burp_dastardly.md +++ b/docs/content/supported_tools/parsers/file/burp_dastardly.md @@ -11,7 +11,7 @@ Dastardly is a free, lightweight web application security scanner for your CI/CD Sample Burp Dastardly scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/burp_dastardly). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/burp_graphql.md b/docs/content/supported_tools/parsers/file/burp_graphql.md index 519f21ee548..ecda79457cf 100644 --- a/docs/content/supported_tools/parsers/file/burp_graphql.md +++ b/docs/content/supported_tools/parsers/file/burp_graphql.md @@ -108,7 +108,7 @@ Example GraphQL query to get issue details: Sample Burp GraphQL scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/burp_graphql). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/burp_suite_dast.md b/docs/content/supported_tools/parsers/file/burp_suite_dast.md index 60794f53611..af9b8c71166 100644 --- a/docs/content/supported_tools/parsers/file/burp_suite_dast.md +++ b/docs/content/supported_tools/parsers/file/burp_suite_dast.md @@ -107,7 +107,7 @@ Sample Burp Suite DAST Scan scans can be found [here](https://github.com/DefectD [Burp Suite DAST](https://portswigger.net/burp/dast) ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/cargo_audit.md b/docs/content/supported_tools/parsers/file/cargo_audit.md index 7203e812b0f..6155c4642c8 100644 --- a/docs/content/supported_tools/parsers/file/cargo_audit.md +++ b/docs/content/supported_tools/parsers/file/cargo_audit.md @@ -12,7 +12,7 @@ CVSS vector fall back to a severity of "High". Sample CargoAudit Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/cargo_audit). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - vulnerability ids - severity diff --git a/docs/content/supported_tools/parsers/file/checkmarx.md b/docs/content/supported_tools/parsers/file/checkmarx.md index 5657a44502d..ba6571994cc 100644 --- a/docs/content/supported_tools/parsers/file/checkmarx.md +++ b/docs/content/supported_tools/parsers/file/checkmarx.md @@ -1,6 +1,8 @@ --- title: "Checkmarx" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/checkmarx/" --- - `Checkmarx Scan`, `Checkmarx Scan detailed`: XML report from Checkmarx SAST (source code analysis) - `Checkmarx OSA`: json report from Checkmarx Open Source Analysis (dependencies analysis) @@ -17,7 +19,7 @@ Data for SAST, SCA and KICS are supported. Sample Checkmarx scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/checkmarx). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - cwe - severity diff --git a/docs/content/supported_tools/parsers/file/checkmarx_cxflow_sast.md b/docs/content/supported_tools/parsers/file/checkmarx_cxflow_sast.md index d8e408f4fce..91e13aae952 100644 --- a/docs/content/supported_tools/parsers/file/checkmarx_cxflow_sast.md +++ b/docs/content/supported_tools/parsers/file/checkmarx_cxflow_sast.md @@ -22,7 +22,7 @@ cx-flow: Sample Checkmarx CxFlow SAST scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/checkmarx_cxflow_sast). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - vuln id from tool - file path diff --git a/docs/content/supported_tools/parsers/file/checkmarx_one.md b/docs/content/supported_tools/parsers/file/checkmarx_one.md index 8d7ee5e9edf..7c63570c5a6 100644 --- a/docs/content/supported_tools/parsers/file/checkmarx_one.md +++ b/docs/content/supported_tools/parsers/file/checkmarx_one.md @@ -1,6 +1,8 @@ --- title: "Checkmarx One Scan" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/checkmarx_one/" --- Import JSON Checkmarx One scanner reports @@ -150,7 +152,7 @@ Sample Checkmarx One scans can be found [here](https://github.com/DefectDojo/dja - [Checkmarx One Documentation](https://checkmarx.com/resource/documents/en/34965-68516-checkmarx-one-documentation-portal.html) ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - vulnerability ids - component name diff --git a/docs/content/supported_tools/parsers/file/checkov.md b/docs/content/supported_tools/parsers/file/checkov.md index 76c1beb6970..958ba6115a4 100644 --- a/docs/content/supported_tools/parsers/file/checkov.md +++ b/docs/content/supported_tools/parsers/file/checkov.md @@ -1,6 +1,8 @@ --- title: "Checkov Report" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/checkov/" --- ### File Types DefectDojo parser accepts Checkov scan data as a .JSON file. @@ -52,7 +54,7 @@ JSON files can be created from the Checkov CLI: https://www.checkov.io/2.Basics/ Sample Checkov scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/checkov). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/chefinspect.md b/docs/content/supported_tools/parsers/file/chefinspect.md index 9fc59c6ad6e..cc73d29661d 100644 --- a/docs/content/supported_tools/parsers/file/chefinspect.md +++ b/docs/content/supported_tools/parsers/file/chefinspect.md @@ -11,7 +11,7 @@ DefectDojo parser accepts Chef Inspect log scan data as a .log or .txt file. Sample Chef Inspect logs can be found at https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/chefinspect ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/clair.md b/docs/content/supported_tools/parsers/file/clair.md index f11f279998f..e514cbd3c94 100644 --- a/docs/content/supported_tools/parsers/file/clair.md +++ b/docs/content/supported_tools/parsers/file/clair.md @@ -8,7 +8,7 @@ You can import JSON reports of Docker image vulnerabilities found by a Clair sca Sample Clair Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/clair). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - vulnerability ids diff --git a/docs/content/supported_tools/parsers/file/cloudsploit.md b/docs/content/supported_tools/parsers/file/cloudsploit.md index 56b8a4814a8..b12bebd9ed2 100644 --- a/docs/content/supported_tools/parsers/file/cloudsploit.md +++ b/docs/content/supported_tools/parsers/file/cloudsploit.md @@ -8,7 +8,7 @@ From: https://github.com/aquasecurity/cloudsploit . Import the JSON output. Sample Cloudsploit (AquaSecurity) scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/cloudsploit). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/cobalt.md b/docs/content/supported_tools/parsers/file/cobalt.md index 672d734ac07..ab70fd59771 100644 --- a/docs/content/supported_tools/parsers/file/cobalt.md +++ b/docs/content/supported_tools/parsers/file/cobalt.md @@ -8,7 +8,7 @@ CSV Report Sample Cobalt.io Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/cobalt). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/codechecker.md b/docs/content/supported_tools/parsers/file/codechecker.md index 6879d98ca59..fb6c0095da4 100644 --- a/docs/content/supported_tools/parsers/file/codechecker.md +++ b/docs/content/supported_tools/parsers/file/codechecker.md @@ -24,7 +24,7 @@ CodeChecker analyze ./codechecker.log -o /path/to/codechecker/analyzer/output/di Sample Codechecker Report native scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/codechecker). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/codeql.md b/docs/content/supported_tools/parsers/file/codeql.md index 824e4147ca7..ddd1a598668 100644 --- a/docs/content/supported_tools/parsers/file/codeql.md +++ b/docs/content/supported_tools/parsers/file/codeql.md @@ -12,7 +12,7 @@ The same can be achieved by running the CodeQL GitHub action with the `add-snipp ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/contrast.md b/docs/content/supported_tools/parsers/file/contrast.md index 5c85a5de06e..c6af1b77944 100644 --- a/docs/content/supported_tools/parsers/file/contrast.md +++ b/docs/content/supported_tools/parsers/file/contrast.md @@ -8,7 +8,7 @@ CSV Report Sample Contrast Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/contrast). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/coverity_api.md b/docs/content/supported_tools/parsers/file/coverity_api.md index b9c6a17297f..44243d278ab 100644 --- a/docs/content/supported_tools/parsers/file/coverity_api.md +++ b/docs/content/supported_tools/parsers/file/coverity_api.md @@ -16,7 +16,7 @@ Other supported attributes: `cwe`, `displayFile`, `occurrenceCount` and `firstDe Sample Coverity API scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/coverity_api). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/coverity_scan.md b/docs/content/supported_tools/parsers/file/coverity_scan.md index 5b502ee0e4e..d353b9fbe93 100644 --- a/docs/content/supported_tools/parsers/file/coverity_scan.md +++ b/docs/content/supported_tools/parsers/file/coverity_scan.md @@ -14,7 +14,7 @@ Run `coverity scan --project-dir --local --local-for Sample Coverity scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/coverity_scan). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/crashtest_security.md b/docs/content/supported_tools/parsers/file/crashtest_security.md index ea919c6f582..48f54842eba 100644 --- a/docs/content/supported_tools/parsers/file/crashtest_security.md +++ b/docs/content/supported_tools/parsers/file/crashtest_security.md @@ -1,6 +1,8 @@ --- title: "Crashtest Security" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/crashtest_security/" --- Import JSON Report Import XML Report in JUnit Format @@ -8,7 +10,7 @@ Import JSON Report Import XML Report in JUnit Format Sample Crashtest Security scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/crashtest_security). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/cred_scan.md b/docs/content/supported_tools/parsers/file/cred_scan.md index fc4a0121ef1..a9f6898a8bd 100644 --- a/docs/content/supported_tools/parsers/file/cred_scan.md +++ b/docs/content/supported_tools/parsers/file/cred_scan.md @@ -1,6 +1,8 @@ --- title: "CredScan Report" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/cred_scan/" --- Import CSV credential scanner reports @@ -8,7 +10,7 @@ Import CSV credential scanner reports Sample CredScan Report scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/cred_scan). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/crunch42.md b/docs/content/supported_tools/parsers/file/crunch42.md index 603ad5bc466..bafa33bbe6e 100644 --- a/docs/content/supported_tools/parsers/file/crunch42.md +++ b/docs/content/supported_tools/parsers/file/crunch42.md @@ -8,7 +8,7 @@ Import JSON findings from Crunch42 vulnerability scan tool. Sample Crunch42 Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/crunch42). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/cyberwatch_galeax.md b/docs/content/supported_tools/parsers/file/cyberwatch_galeax.md index 2275b08517a..c8306690050 100644 --- a/docs/content/supported_tools/parsers/file/cyberwatch_galeax.md +++ b/docs/content/supported_tools/parsers/file/cyberwatch_galeax.md @@ -14,7 +14,7 @@ For each CVE and security issue found in the JSON input, the parser creates a co Sample Cybwerwatch Galeax Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/cyberwatch). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/cyclonedx.md b/docs/content/supported_tools/parsers/file/cyclonedx.md index af9ac33c691..80ed07aedbd 100644 --- a/docs/content/supported_tools/parsers/file/cyclonedx.md +++ b/docs/content/supported_tools/parsers/file/cyclonedx.md @@ -1,6 +1,8 @@ --- title: "CycloneDX" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/cyclonedx/" --- CycloneDX is a lightweight software bill of materials (SBOM) standard designed for use in application security contexts and supply chain component analysis. @@ -31,7 +33,7 @@ cyclonedx-py Sample CycloneDX scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/cyclonedx). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - vuln id from tool - component name diff --git a/docs/content/supported_tools/parsers/file/dawnscanner.md b/docs/content/supported_tools/parsers/file/dawnscanner.md index d8f10abb3f3..d236f874be7 100644 --- a/docs/content/supported_tools/parsers/file/dawnscanner.md +++ b/docs/content/supported_tools/parsers/file/dawnscanner.md @@ -8,7 +8,7 @@ Import report in JSON generated with -j option Sample DawnScanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/dawnscanner). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/deepfence_threatmapper.md b/docs/content/supported_tools/parsers/file/deepfence_threatmapper.md index 14224893e0f..5ad95a6df4c 100644 --- a/docs/content/supported_tools/parsers/file/deepfence_threatmapper.md +++ b/docs/content/supported_tools/parsers/file/deepfence_threatmapper.md @@ -8,7 +8,7 @@ Import compliance, malware, secret, vulnerability reports from [Deepfence Threat Sample Threatmapper scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/deepfence_threatmapper). In this link are both .xlsx and .csv listed. They contain the same content, but csv can be read in the Browser, but only xlsx is supported by the parser. ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/dependency_check.md b/docs/content/supported_tools/parsers/file/dependency_check.md index 5e2b28b47cb..11789bc3dca 100644 --- a/docs/content/supported_tools/parsers/file/dependency_check.md +++ b/docs/content/supported_tools/parsers/file/dependency_check.md @@ -1,6 +1,8 @@ --- title: "Dependency Check" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/dependency_check/" --- OWASP Dependency Check output can be imported in Xml format. This parser ingests the vulnerable dependencies and inherits the suppressions. @@ -27,7 +29,7 @@ DC bundles dependencies under five scenarios: Sample Dependency Check scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/dependency_check). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/dependency_track.md b/docs/content/supported_tools/parsers/file/dependency_track.md index 26d7f84343c..22971c3e2c8 100644 --- a/docs/content/supported_tools/parsers/file/dependency_track.md +++ b/docs/content/supported_tools/parsers/file/dependency_track.md @@ -1,6 +1,8 @@ --- title: "Dependency Track" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/dependency_track/" --- Dependency Track has implemented a DefectDojo integration. Information about how to configure the integration is documented here: @@ -14,7 +16,7 @@ imported in JSON format. See here for more info on this JSON format: Sample Dependency Track scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/dependency_track). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - component name - component version diff --git a/docs/content/supported_tools/parsers/file/detect_secrets.md b/docs/content/supported_tools/parsers/file/detect_secrets.md index 0d7f52cd60a..5ba7a81bfae 100644 --- a/docs/content/supported_tools/parsers/file/detect_secrets.md +++ b/docs/content/supported_tools/parsers/file/detect_secrets.md @@ -8,7 +8,7 @@ Import of JSON report from Sample Detect-secrets scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/detect_secrets). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/dockerbench.md b/docs/content/supported_tools/parsers/file/dockerbench.md index 906bb497ae4..b4c626ef69c 100644 --- a/docs/content/supported_tools/parsers/file/dockerbench.md +++ b/docs/content/supported_tools/parsers/file/dockerbench.md @@ -9,7 +9,7 @@ docker-bench-security is a script that make tests based on [CIS Docker Benchmark Sample docker-bench-security Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/dockerbench). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/dockle.md b/docs/content/supported_tools/parsers/file/dockle.md index d3b1b9092d5..cf5a3fe2437 100644 --- a/docs/content/supported_tools/parsers/file/dockle.md +++ b/docs/content/supported_tools/parsers/file/dockle.md @@ -9,7 +9,7 @@ Import JSON container image linter reports Sample Dockle Report scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/dockle). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/drheader.md b/docs/content/supported_tools/parsers/file/drheader.md index 1a34af86717..e1f138f366d 100644 --- a/docs/content/supported_tools/parsers/file/drheader.md +++ b/docs/content/supported_tools/parsers/file/drheader.md @@ -9,7 +9,7 @@ Import of JSON report from Sample DrHeader scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/drheader). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/dsop.md b/docs/content/supported_tools/parsers/file/dsop.md index 6d2ad22755f..aa9d49698dc 100644 --- a/docs/content/supported_tools/parsers/file/dsop.md +++ b/docs/content/supported_tools/parsers/file/dsop.md @@ -8,6 +8,6 @@ Import XLSX findings from DSOP vulnerability scan pipelines. Sample DSOP Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/dsop). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - vulnerability ids diff --git a/docs/content/supported_tools/parsers/file/edgescan.md b/docs/content/supported_tools/parsers/file/edgescan.md index 0d75fd22375..5721b561b6d 100644 --- a/docs/content/supported_tools/parsers/file/edgescan.md +++ b/docs/content/supported_tools/parsers/file/edgescan.md @@ -1,12 +1,14 @@ --- title: "Edgescan" toc_hide: true +aliases: + - "/supported_tools/file/edgescan" --- Import Edgescan vulnerabilities by JSON file or [API - no file required](../../api/edgescan) ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/eslint.md b/docs/content/supported_tools/parsers/file/eslint.md index 8e0c62b5310..6fd3684ed98 100644 --- a/docs/content/supported_tools/parsers/file/eslint.md +++ b/docs/content/supported_tools/parsers/file/eslint.md @@ -8,7 +8,7 @@ ESLint Json report format (-f json) Sample ESLint scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/eslint). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/fortify.md b/docs/content/supported_tools/parsers/file/fortify.md index 1d5443570b8..e0589ee1290 100644 --- a/docs/content/supported_tools/parsers/file/fortify.md +++ b/docs/content/supported_tools/parsers/file/fortify.md @@ -1,6 +1,8 @@ --- title: "Fortify" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/fortify/" --- You can either import the findings in .xml or in .fpr file format.
If you import a .fpr file, the parser will look for the file 'audit.fvdl' and analyze it. An extracted example can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/fortify/audit.fvdl). The optional `audit.xml` is also parsed. All vulnerabilities marked with `suppressed="true"` will be marked as false positive. @@ -31,7 +33,7 @@ required XML: ``` ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/garak.md b/docs/content/supported_tools/parsers/file/garak.md index 77a8fa96418..d617c546583 100644 --- a/docs/content/supported_tools/parsers/file/garak.md +++ b/docs/content/supported_tools/parsers/file/garak.md @@ -29,7 +29,7 @@ The parser accepts a `.jsonl` hit log. Each line is one hit record with fields i Sample scan data for testing purposes can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/garak). ### Deduplication -The "Garak Scan" scan type uses the `hash_code` [deduplication algorithm](/en/working_with_findings/finding_deduplication/about_deduplication/) with the following fields: +The "Garak Scan" scan type uses the `hash_code` [deduplication algorithm](/triage_findings/finding_deduplication/about_deduplication/) with the following fields: - title (the garak probe and its goal) - component_name (the scanned model / generator) diff --git a/docs/content/supported_tools/parsers/file/gcloud_artifact_scan.md b/docs/content/supported_tools/parsers/file/gcloud_artifact_scan.md index 6956f8a8cc4..a894e6475ed 100644 --- a/docs/content/supported_tools/parsers/file/gcloud_artifact_scan.md +++ b/docs/content/supported_tools/parsers/file/gcloud_artifact_scan.md @@ -14,7 +14,7 @@ DefectDojo parser accepts Google Cloud Artifact Vulnerability Scan data as a .js Sample reports can be found at https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/gcloud_artifact_scan ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/generic.md b/docs/content/supported_tools/parsers/file/generic.md index 48939167bd9..35db52fe9cf 100644 --- a/docs/content/supported_tools/parsers/file/generic.md +++ b/docs/content/supported_tools/parsers/file/generic.md @@ -1,6 +1,8 @@ --- title: 'Generic Findings Import' toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/generic/" --- Generic Findings Import can be used to import any report in CSV or JSON format. @@ -240,7 +242,7 @@ Sample Generic Findings Import scans can be found [here](https://github.com/Defe ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/ggshield.md b/docs/content/supported_tools/parsers/file/ggshield.md index a6f01414557..b985c3425cc 100644 --- a/docs/content/supported_tools/parsers/file/ggshield.md +++ b/docs/content/supported_tools/parsers/file/ggshield.md @@ -8,7 +8,7 @@ Import [Ggshield](https://github.com/GitGuardian/ggshield) findings in JSON form Sample Ggshield scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/ggshield). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/github_sast.md b/docs/content/supported_tools/parsers/file/github_sast.md index a551d9ea0ef..4c2b0f19272 100644 --- a/docs/content/supported_tools/parsers/file/github_sast.md +++ b/docs/content/supported_tools/parsers/file/github_sast.md @@ -1,6 +1,8 @@ --- title: "Github SAST Scan" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/github_sast/" --- Import findings in JSON format from Github Code Scanning REST API: diff --git a/docs/content/supported_tools/parsers/file/github_vulnerability.md b/docs/content/supported_tools/parsers/file/github_vulnerability.md index 58172be32e9..16ad0909818 100644 --- a/docs/content/supported_tools/parsers/file/github_vulnerability.md +++ b/docs/content/supported_tools/parsers/file/github_vulnerability.md @@ -1,6 +1,8 @@ --- title: "Github Vulnerability Scan" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/github_vulnerability/" --- Import findings from Github vulnerability scan (GraphQL Query): @@ -225,7 +227,7 @@ def get_dependabot_alerts_repository(repo, owner): Sample Github Vulnerability scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/github_vulnerability). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/gitlab_api_fuzzing.md b/docs/content/supported_tools/parsers/file/gitlab_api_fuzzing.md index 2bb0fcace28..4805e774a23 100644 --- a/docs/content/supported_tools/parsers/file/gitlab_api_fuzzing.md +++ b/docs/content/supported_tools/parsers/file/gitlab_api_fuzzing.md @@ -8,7 +8,7 @@ GitLab API Fuzzing Report report file can be imported in JSON format (option --j Sample GitLab API Fuzzing Report Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/gitlab_api_fuzzing). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/gitlab_container_scan.md b/docs/content/supported_tools/parsers/file/gitlab_container_scan.md index f3040e74010..0564794ce9f 100644 --- a/docs/content/supported_tools/parsers/file/gitlab_container_scan.md +++ b/docs/content/supported_tools/parsers/file/gitlab_container_scan.md @@ -8,7 +8,7 @@ GitLab Container Scan report file can be imported in JSON format (option --json) Sample GitLab Container Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/gitlab_container_scan). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/gitlab_dast.md b/docs/content/supported_tools/parsers/file/gitlab_dast.md index 6efd5664ffb..4c649bc883d 100644 --- a/docs/content/supported_tools/parsers/file/gitlab_dast.md +++ b/docs/content/supported_tools/parsers/file/gitlab_dast.md @@ -8,7 +8,7 @@ GitLab DAST Report in JSON format (option --json) Sample GitLab DAST Report scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/gitlab_dast). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/gitlab_dep_scan.md b/docs/content/supported_tools/parsers/file/gitlab_dep_scan.md index 3489ffb7951..279be410266 100644 --- a/docs/content/supported_tools/parsers/file/gitlab_dep_scan.md +++ b/docs/content/supported_tools/parsers/file/gitlab_dep_scan.md @@ -8,7 +8,7 @@ Import Dependency Scanning Report vulnerabilities in JSON format: https://docs.g Sample GitLab Dependency Scanning Report scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/gitlab_dep_scan). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - vulnerability ids diff --git a/docs/content/supported_tools/parsers/file/gitlab_sast.md b/docs/content/supported_tools/parsers/file/gitlab_sast.md index 2f224e1f4e2..ab03e474442 100644 --- a/docs/content/supported_tools/parsers/file/gitlab_sast.md +++ b/docs/content/supported_tools/parsers/file/gitlab_sast.md @@ -8,7 +8,7 @@ Import SAST Report vulnerabilities in JSON format: https://docs.gitlab.com/ee/us Sample GitLab SAST Report scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/gitlab_sast). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/gitlab_secret_detection_report.md b/docs/content/supported_tools/parsers/file/gitlab_secret_detection_report.md index ac6f6922351..b75844450cf 100644 --- a/docs/content/supported_tools/parsers/file/gitlab_secret_detection_report.md +++ b/docs/content/supported_tools/parsers/file/gitlab_secret_detection_report.md @@ -8,7 +8,7 @@ GitLab Secret Detection Report file can be imported in JSON format (option --jso Sample GitLab Secret Detection Report scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/gitlab_secret_detection_report). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/gitleaks.md b/docs/content/supported_tools/parsers/file/gitleaks.md index 1caec6a7169..b198a06bb6e 100644 --- a/docs/content/supported_tools/parsers/file/gitleaks.md +++ b/docs/content/supported_tools/parsers/file/gitleaks.md @@ -1,6 +1,8 @@ --- title: "Gitleaks" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/gitleaks/" --- Import Gitleaks findings in JSON format. @@ -8,7 +10,7 @@ Import Gitleaks findings in JSON format. Sample Gitleaks scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/gitleaks). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/gosec.md b/docs/content/supported_tools/parsers/file/gosec.md index 966d4d61eff..42a9c114d83 100644 --- a/docs/content/supported_tools/parsers/file/gosec.md +++ b/docs/content/supported_tools/parsers/file/gosec.md @@ -8,7 +8,7 @@ Import Gosec Scanner findings in JSON format. Sample Gosec Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/gosec). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/govulncheck.md b/docs/content/supported_tools/parsers/file/govulncheck.md index 3d7e0bd54ba..9d9e72d9174 100644 --- a/docs/content/supported_tools/parsers/file/govulncheck.md +++ b/docs/content/supported_tools/parsers/file/govulncheck.md @@ -39,7 +39,7 @@ Scanner parser fails with an error pointing you to the SARIF scan type. Sample Govulncheck scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/govulncheck). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/h1.md b/docs/content/supported_tools/parsers/file/h1.md index 12652a0a74f..1971cb5c931 100644 --- a/docs/content/supported_tools/parsers/file/h1.md +++ b/docs/content/supported_tools/parsers/file/h1.md @@ -8,7 +8,7 @@ Import HackerOne cases findings in JSON format (vulnerability disclosure parser) Sample HackerOne Cases scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/h1). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/hadolint.md b/docs/content/supported_tools/parsers/file/hadolint.md index 68b864b8923..7c7cd46ffcf 100644 --- a/docs/content/supported_tools/parsers/file/hadolint.md +++ b/docs/content/supported_tools/parsers/file/hadolint.md @@ -8,7 +8,7 @@ Hadolint Dockerfile scan in json format. Sample Hadolint scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/hadolint). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/harbor_vulnerability.md b/docs/content/supported_tools/parsers/file/harbor_vulnerability.md index 0d9a3e75d90..e0fed039c0c 100644 --- a/docs/content/supported_tools/parsers/file/harbor_vulnerability.md +++ b/docs/content/supported_tools/parsers/file/harbor_vulnerability.md @@ -1,6 +1,8 @@ --- title: "Harbor Vulnerability" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/harbor_vulnerability/" --- Import findings from Harbor registry container scan: @@ -9,7 +11,7 @@ Import findings from Harbor registry container scan: Sample Harbor Vulnerability scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/harbor_vulnerability). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/hcl_appscan.md b/docs/content/supported_tools/parsers/file/hcl_appscan.md index a3b5a9430f6..db7d744320d 100644 --- a/docs/content/supported_tools/parsers/file/hcl_appscan.md +++ b/docs/content/supported_tools/parsers/file/hcl_appscan.md @@ -1,6 +1,8 @@ --- title: "HCL Appscan" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/hcl_appscan/" --- The HCL Appscan has the possibility to export the results in PDF, XML and CSV formats within the portal. However, this parser only supports the import of XML generated from HCL Appscan on cloud. @@ -8,7 +10,7 @@ The HCL Appscan has the possibility to export the results in PDF, XML and CSV fo Sample HCL Appscan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/hcl_appscan). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/hcl_asoc_sast.md b/docs/content/supported_tools/parsers/file/hcl_asoc_sast.md index bfabea64196..19532b6be10 100644 --- a/docs/content/supported_tools/parsers/file/hcl_asoc_sast.md +++ b/docs/content/supported_tools/parsers/file/hcl_asoc_sast.md @@ -8,7 +8,7 @@ HCL Appscan on Cloud can export the results in PDF, XML and CSV formats but this Sample HCL AppScan on Cloud SAST scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/hcl_asoc_sast). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - file path diff --git a/docs/content/supported_tools/parsers/file/horusec.md b/docs/content/supported_tools/parsers/file/horusec.md index 9d636268188..87c1642dc30 100644 --- a/docs/content/supported_tools/parsers/file/horusec.md +++ b/docs/content/supported_tools/parsers/file/horusec.md @@ -15,7 +15,7 @@ References: Sample Horusec scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/horusec). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/humble.md b/docs/content/supported_tools/parsers/file/humble.md index 16bc7e43207..89e9cb7ac51 100644 --- a/docs/content/supported_tools/parsers/file/humble.md +++ b/docs/content/supported_tools/parsers/file/humble.md @@ -9,6 +9,6 @@ Import JSON report of the Humble scanner Sample Humble Report scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/humble). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title diff --git a/docs/content/supported_tools/parsers/file/huskyci.md b/docs/content/supported_tools/parsers/file/huskyci.md index 2f4c2465820..efb6dda5bda 100644 --- a/docs/content/supported_tools/parsers/file/huskyci.md +++ b/docs/content/supported_tools/parsers/file/huskyci.md @@ -9,7 +9,7 @@ Import JSON reports from Sample HuskyCI Report scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/huskyci). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/hydra.md b/docs/content/supported_tools/parsers/file/hydra.md index 86ecd0a963d..7e96eb4a22d 100644 --- a/docs/content/supported_tools/parsers/file/hydra.md +++ b/docs/content/supported_tools/parsers/file/hydra.md @@ -43,7 +43,7 @@ Sample JSON report: Sample Hydra scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/hydra). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/ibm_app.md b/docs/content/supported_tools/parsers/file/ibm_app.md index c9cdb18f226..8c0ec5f0bcc 100644 --- a/docs/content/supported_tools/parsers/file/ibm_app.md +++ b/docs/content/supported_tools/parsers/file/ibm_app.md @@ -8,7 +8,7 @@ XML file from IBM App Scanner. Sample IBM AppScan DAST scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/ibm_app). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/immuniweb.md b/docs/content/supported_tools/parsers/file/immuniweb.md index f93c1e59cc3..aee4ed357fa 100644 --- a/docs/content/supported_tools/parsers/file/immuniweb.md +++ b/docs/content/supported_tools/parsers/file/immuniweb.md @@ -8,7 +8,7 @@ XML or JSON Scan Result File from [Immuniweb Scan](https://www.immuniweb.com/). Sample Immuniweb Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/immuniweb). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/intsights.md b/docs/content/supported_tools/parsers/file/intsights.md index 415f9124b1d..aa6dae3925b 100644 --- a/docs/content/supported_tools/parsers/file/intsights.md +++ b/docs/content/supported_tools/parsers/file/intsights.md @@ -65,7 +65,7 @@ Example: Sample IntSights Report scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/intsights). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/invicti.md b/docs/content/supported_tools/parsers/file/invicti.md index e71c25a62f1..1766d44aa7d 100644 --- a/docs/content/supported_tools/parsers/file/invicti.md +++ b/docs/content/supported_tools/parsers/file/invicti.md @@ -1,6 +1,8 @@ --- title: "Invicti" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/invicti/" --- Vulnerabilities List - JSON report @@ -127,7 +129,7 @@ Sample Invicti scans can be found [here](https://github.com/DefectDojo/django-De ## Default Deduplication Hashcode Fields By default, DefectDojo identifies duplicate Findings using these -[hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +[hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/iriusrisk.md b/docs/content/supported_tools/parsers/file/iriusrisk.md index 1fd6766e19b..e85f45db3ec 100644 --- a/docs/content/supported_tools/parsers/file/iriusrisk.md +++ b/docs/content/supported_tools/parsers/file/iriusrisk.md @@ -17,7 +17,7 @@ The IriusRisk parser accepts CSV file format. To generate this file from IriusRi ## Default Deduplication Hashcode Fields -DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - component_name diff --git a/docs/content/supported_tools/parsers/file/jfrog_xray_api_summary_artifact.md b/docs/content/supported_tools/parsers/file/jfrog_xray_api_summary_artifact.md index b17b367fb42..b04ff6c057a 100644 --- a/docs/content/supported_tools/parsers/file/jfrog_xray_api_summary_artifact.md +++ b/docs/content/supported_tools/parsers/file/jfrog_xray_api_summary_artifact.md @@ -13,7 +13,7 @@ Sample JFrog Xray API Summary Artifact Scans can be found [here](https://github. See JFrog Documentation: https://jfrog.com/help/r/jfrog-rest-apis/summary ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/jfrog_xray_on_demand_binary_scan.md b/docs/content/supported_tools/parsers/file/jfrog_xray_on_demand_binary_scan.md index 4565bad77f8..0533bd69d15 100644 --- a/docs/content/supported_tools/parsers/file/jfrog_xray_on_demand_binary_scan.md +++ b/docs/content/supported_tools/parsers/file/jfrog_xray_on_demand_binary_scan.md @@ -12,7 +12,7 @@ https://jfrog.com/help/r/jfrog-cli/on-demand-binary-scan Sample JFrog Xray On Demand Binary Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/jfrog_xray_on_demand_binary_scan). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - component name diff --git a/docs/content/supported_tools/parsers/file/jfrog_xray_unified.md b/docs/content/supported_tools/parsers/file/jfrog_xray_unified.md index 6ec1b99d821..68c1178ee66 100644 --- a/docs/content/supported_tools/parsers/file/jfrog_xray_unified.md +++ b/docs/content/supported_tools/parsers/file/jfrog_xray_unified.md @@ -1,6 +1,8 @@ --- title: "JFrog XRay Unified" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/jfrog_xray_unified/" --- Import the JSON format for the \"Security & Compliance | Reports\" export. Jfrog's Xray tool is an add-on to their Artifactory repository that does Software Composition Analysis, see https://www.jfrog.com/confluence/display/JFROG/JFrog+Xray for more information. \"Xray Unified\" refers to Xray Version 3.0 and later. @@ -8,7 +10,7 @@ Import the JSON format for the \"Security & Compliance | Reports\" export. Jfrog Sample JFrog XRay Unified scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/jfrog_xray_unified). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - vulnerability ids - file path diff --git a/docs/content/supported_tools/parsers/file/jfrogxray.md b/docs/content/supported_tools/parsers/file/jfrogxray.md index e51d8511137..09a71215b91 100644 --- a/docs/content/supported_tools/parsers/file/jfrogxray.md +++ b/docs/content/supported_tools/parsers/file/jfrogxray.md @@ -8,7 +8,7 @@ Import the JSON format for the \"Security Export\" file. Use this importer for X Sample JFrogXRay scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/jfrogxray). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/kics.md b/docs/content/supported_tools/parsers/file/kics.md index df4b97a0b29..d42f09657dc 100644 --- a/docs/content/supported_tools/parsers/file/kics.md +++ b/docs/content/supported_tools/parsers/file/kics.md @@ -8,7 +8,7 @@ Import of JSON report from Sample KICS Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/kics). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - file path - line diff --git a/docs/content/supported_tools/parsers/file/kiuwan.md b/docs/content/supported_tools/parsers/file/kiuwan.md index 7d1aa03e495..7339dfd8b18 100644 --- a/docs/content/supported_tools/parsers/file/kiuwan.md +++ b/docs/content/supported_tools/parsers/file/kiuwan.md @@ -8,7 +8,7 @@ Import Kiuwan SAST Scan in CSV format. Export as CSV Results on Kiuwan, or via t Sample Kiuwan Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/kiuwan). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - description - severity diff --git a/docs/content/supported_tools/parsers/file/kiuwan_sca.md b/docs/content/supported_tools/parsers/file/kiuwan_sca.md index 29f7014676b..d1629252fe1 100644 --- a/docs/content/supported_tools/parsers/file/kiuwan_sca.md +++ b/docs/content/supported_tools/parsers/file/kiuwan_sca.md @@ -1,6 +1,8 @@ --- title: Kiuwan Scanner (SCA i.e. "Insights") toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/kiuwan_sca/" --- Import Kiuwan Insights Scan in JSON format. Export via API endpoint `insights/analysis/security` as json and create a file for importing to DefectDojo. @@ -26,7 +28,7 @@ saveFile("result.json", json.dumps(data, indent=2)) Sample Kiuwan Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/kiuwan_sca). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/krakend_audit.md b/docs/content/supported_tools/parsers/file/krakend_audit.md index 501e78526cf..4d757a35d78 100644 --- a/docs/content/supported_tools/parsers/file/krakend_audit.md +++ b/docs/content/supported_tools/parsers/file/krakend_audit.md @@ -11,7 +11,7 @@ krakend audit -c krakend.json -f "{{ marshal . }}" >> recommendations.json Sample KrakenD Audit scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/krakend_audit). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - description - mitigation diff --git a/docs/content/supported_tools/parsers/file/kubeaudit.md b/docs/content/supported_tools/parsers/file/kubeaudit.md index f04d178011e..a1b6c88121a 100644 --- a/docs/content/supported_tools/parsers/file/kubeaudit.md +++ b/docs/content/supported_tools/parsers/file/kubeaudit.md @@ -8,7 +8,7 @@ Kubeaudit is a command line tool and a Go package to audit Kubernetes clusters f Sample Kubeaudit scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/kubeaudit). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/kubebench.md b/docs/content/supported_tools/parsers/file/kubebench.md index 7c5a7297201..dfd38419be4 100644 --- a/docs/content/supported_tools/parsers/file/kubebench.md +++ b/docs/content/supported_tools/parsers/file/kubebench.md @@ -8,7 +8,7 @@ Import JSON reports of Kubernetes CIS benchmark scans. Sample kube-bench Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/kubebench). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - vuln id from tool diff --git a/docs/content/supported_tools/parsers/file/kubehunter.md b/docs/content/supported_tools/parsers/file/kubehunter.md index bd685b864a0..043cefb74b8 100644 --- a/docs/content/supported_tools/parsers/file/kubehunter.md +++ b/docs/content/supported_tools/parsers/file/kubehunter.md @@ -1,6 +1,8 @@ --- title: "kubeHunter Scanner" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/kubehunter/" --- Import JSON reports of kube-hunter scans. Use "kube-hunter --report json" to produce the report in json format. @@ -8,7 +10,7 @@ Import JSON reports of kube-hunter scans. Use "kube-hunter --report json" to pro Sample kubeHunter Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/kubehunter). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/kubescape.md b/docs/content/supported_tools/parsers/file/kubescape.md index b455b9841a8..7de45d3c169 100644 --- a/docs/content/supported_tools/parsers/file/kubescape.md +++ b/docs/content/supported_tools/parsers/file/kubescape.md @@ -10,7 +10,7 @@ The parser supports json output files Sample Kubescape scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/kubescape). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - component name diff --git a/docs/content/supported_tools/parsers/file/legitify.md b/docs/content/supported_tools/parsers/file/legitify.md index a68415f1985..f6b5e073084 100644 --- a/docs/content/supported_tools/parsers/file/legitify.md +++ b/docs/content/supported_tools/parsers/file/legitify.md @@ -9,7 +9,7 @@ This DefectDojo parser accepts JSON files (in flattened format) from Legitify. F Sample scan data for testing purposes can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/legitify). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - endpoints diff --git a/docs/content/supported_tools/parsers/file/mend.md b/docs/content/supported_tools/parsers/file/mend.md index b3e1a901039..70a6bc27d62 100644 --- a/docs/content/supported_tools/parsers/file/mend.md +++ b/docs/content/supported_tools/parsers/file/mend.md @@ -15,7 +15,7 @@ See documentation: https://docs.mend.io/bundle/unified_agent/page/example_of_a_u *Formerly known as Whitesource.* ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/meterian.md b/docs/content/supported_tools/parsers/file/meterian.md index 6d2793c8ba7..5676585bdc2 100644 --- a/docs/content/supported_tools/parsers/file/meterian.md +++ b/docs/content/supported_tools/parsers/file/meterian.md @@ -8,7 +8,7 @@ The Meterian JSON report output file can be imported. Sample Meterian Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/meterian). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - cwe - component name diff --git a/docs/content/supported_tools/parsers/file/microfocus_webinspect.md b/docs/content/supported_tools/parsers/file/microfocus_webinspect.md index 8a7bc68f499..406031fccdd 100644 --- a/docs/content/supported_tools/parsers/file/microfocus_webinspect.md +++ b/docs/content/supported_tools/parsers/file/microfocus_webinspect.md @@ -8,7 +8,7 @@ Import XML report Sample Microfocus Webinspect Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/microfocus_webinspect). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/mobsf.md b/docs/content/supported_tools/parsers/file/mobsf.md index 6237be639fa..256d4ae3ffa 100644 --- a/docs/content/supported_tools/parsers/file/mobsf.md +++ b/docs/content/supported_tools/parsers/file/mobsf.md @@ -10,7 +10,7 @@ Export a JSON file using the API, api/v1/report\_json and import it to Defectdoj Sample MobSF Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/mobsf). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/mobsf_scorecard.md b/docs/content/supported_tools/parsers/file/mobsf_scorecard.md index 824f2ea750b..248e15d7086 100644 --- a/docs/content/supported_tools/parsers/file/mobsf_scorecard.md +++ b/docs/content/supported_tools/parsers/file/mobsf_scorecard.md @@ -8,7 +8,7 @@ Export a JSON file using the API, api/v1/report_json. Sample MobSF Scorecard Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/mobsf_scorecard). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/mozilla_observatory.md b/docs/content/supported_tools/parsers/file/mozilla_observatory.md index 6e320bf1883..c61bacd38c8 100644 --- a/docs/content/supported_tools/parsers/file/mozilla_observatory.md +++ b/docs/content/supported_tools/parsers/file/mozilla_observatory.md @@ -8,7 +8,7 @@ Import JSON report. Sample Mozilla Observatory Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/mozilla_observatory). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/ms_defender.md b/docs/content/supported_tools/parsers/file/ms_defender.md index 11cabcfc378..6c2b588e791 100644 --- a/docs/content/supported_tools/parsers/file/ms_defender.md +++ b/docs/content/supported_tools/parsers/file/ms_defender.md @@ -1,6 +1,8 @@ --- title: "MS Defender Parser" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/ms_defender/" --- This parser helps to parse Microsoft Defender Findings and supports two types of imports: - You can import a JSON output file from the api/vulnerabilities/machinesVulnerabilities endpoint of Microsoft defender. @@ -11,7 +13,7 @@ This parser helps to parse Microsoft Defender Findings and supports two types of Sample MS Defender Parser scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/ms_defender). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/n0s1.md b/docs/content/supported_tools/parsers/file/n0s1.md index d9aaa8564d9..d528942ec02 100644 --- a/docs/content/supported_tools/parsers/file/n0s1.md +++ b/docs/content/supported_tools/parsers/file/n0s1.md @@ -13,6 +13,6 @@ Sample n0s1 scans can be found [here](https://github.com/DefectDojo/django-Defec See n0s1 on GitHub: https://github.com/spark1security/n0s1 ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - description diff --git a/docs/content/supported_tools/parsers/file/nancy.md b/docs/content/supported_tools/parsers/file/nancy.md index 468d3246b61..a2ba6fa62a8 100644 --- a/docs/content/supported_tools/parsers/file/nancy.md +++ b/docs/content/supported_tools/parsers/file/nancy.md @@ -19,7 +19,7 @@ Sample Nancy scans can be found [here](https://github.com/DefectDojo/django-Defe See Nancy on [Github](https://github.com/sonatype-nexus-community/nancy) ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - vuln id from tool diff --git a/docs/content/supported_tools/parsers/file/netsparker.md b/docs/content/supported_tools/parsers/file/netsparker.md index 4cd829e0468..df7e66ca449 100644 --- a/docs/content/supported_tools/parsers/file/netsparker.md +++ b/docs/content/supported_tools/parsers/file/netsparker.md @@ -12,7 +12,7 @@ Vulnerabilities List - JSON report Sample Netsparker scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/netsparker). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/neuvector.md b/docs/content/supported_tools/parsers/file/neuvector.md index b9f76eeca7a..9550f1fcb28 100644 --- a/docs/content/supported_tools/parsers/file/neuvector.md +++ b/docs/content/supported_tools/parsers/file/neuvector.md @@ -8,7 +8,7 @@ Imports compliance scans returned by REST API. Sample NeuVector (compliance) scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/neuvector). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/neuvector_compliance.md b/docs/content/supported_tools/parsers/file/neuvector_compliance.md index 0bb4f7b0bc1..8097162a00f 100644 --- a/docs/content/supported_tools/parsers/file/neuvector_compliance.md +++ b/docs/content/supported_tools/parsers/file/neuvector_compliance.md @@ -8,7 +8,7 @@ JSON output of /v1/scan/{entity}/{id} endpoint Sample NeuVector (REST) scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/neuvector_compliance). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - vuln id from tool diff --git a/docs/content/supported_tools/parsers/file/nexpose.md b/docs/content/supported_tools/parsers/file/nexpose.md index 0259c1709cb..69c1dd2ccc8 100644 --- a/docs/content/supported_tools/parsers/file/nexpose.md +++ b/docs/content/supported_tools/parsers/file/nexpose.md @@ -1,6 +1,8 @@ --- title: "Nexpose XML 2.0 (Rapid7)" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/nexpose/" --- # Nexpose XML 2.0 (Rapid7) Parser Documentation @@ -110,7 +112,7 @@ Sample Nexpose XML 2.0 (Rapid7) scans can be found in the [unit test example sca - [Nexpose Documentation](https://docs.rapid7.com/nexpose/) ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/nikto.md b/docs/content/supported_tools/parsers/file/nikto.md index 65c82b58b8d..34ecee1294f 100644 --- a/docs/content/supported_tools/parsers/file/nikto.md +++ b/docs/content/supported_tools/parsers/file/nikto.md @@ -15,7 +15,7 @@ See: https://github.com/sullo/nikto Sample Nikto scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/nikto). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/nmap.md b/docs/content/supported_tools/parsers/file/nmap.md index b2823963938..fa5defba123 100644 --- a/docs/content/supported_tools/parsers/file/nmap.md +++ b/docs/content/supported_tools/parsers/file/nmap.md @@ -1,6 +1,8 @@ --- title: "Nmap" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/nmap/" --- XML output (use -oX) @@ -8,7 +10,7 @@ XML output (use -oX) Sample Nmap scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/nmap). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/noseyparker.md b/docs/content/supported_tools/parsers/file/noseyparker.md index 6bfc613a960..1acbc957e97 100644 --- a/docs/content/supported_tools/parsers/file/noseyparker.md +++ b/docs/content/supported_tools/parsers/file/noseyparker.md @@ -31,7 +31,7 @@ The parser only accepts .jsonl reports. Each line of the JSON Lines file from No Sample scan data for testing purposes can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/noseyparker). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/npm_audit.md b/docs/content/supported_tools/parsers/file/npm_audit.md index d765fbebbc1..8ca5de54398 100644 --- a/docs/content/supported_tools/parsers/file/npm_audit.md +++ b/docs/content/supported_tools/parsers/file/npm_audit.md @@ -30,7 +30,7 @@ Sample NPM Audit scans can be found [here](https://github.com/DefectDojo/django- See NPM-Audit-Report on GitHub: https://github.com/npm/npm-audit-report/ ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/npm_audit_7_plus.md b/docs/content/supported_tools/parsers/file/npm_audit_7_plus.md index 1d7f1bf91dd..2cf910f17ff 100644 --- a/docs/content/supported_tools/parsers/file/npm_audit_7_plus.md +++ b/docs/content/supported_tools/parsers/file/npm_audit_7_plus.md @@ -26,7 +26,7 @@ Sample NPM Audit scans can be found [here](https://github.com/DefectDojo/django- See NPM-Audit-Report on GitHub: https://github.com/npm/npm-audit-report/ ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/nsp.md b/docs/content/supported_tools/parsers/file/nsp.md index cfeca99078c..9f93788b74d 100644 --- a/docs/content/supported_tools/parsers/file/nsp.md +++ b/docs/content/supported_tools/parsers/file/nsp.md @@ -1,6 +1,8 @@ --- title: "Node Security Platform" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/nsp/" --- Node Security Platform (NSP) output file can be imported in JSON format. @@ -8,7 +10,7 @@ Node Security Platform (NSP) output file can be imported in JSON format. Sample Node Security Platform scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/nsp). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/nuclei.md b/docs/content/supported_tools/parsers/file/nuclei.md index d4672a9efd1..f4c883f4b1d 100644 --- a/docs/content/supported_tools/parsers/file/nuclei.md +++ b/docs/content/supported_tools/parsers/file/nuclei.md @@ -1,6 +1,8 @@ --- title: "Nuclei" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/nuclei/" --- Import JSON output of nuclei scan report @@ -8,7 +10,7 @@ Import JSON output of nuclei scan report ). Sample OssIndex Devaudit scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/ossindex_devaudit). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/osv_scanner.md b/docs/content/supported_tools/parsers/file/osv_scanner.md index 66eb8bb882b..3b0a8da4ad3 100644 --- a/docs/content/supported_tools/parsers/file/osv_scanner.md +++ b/docs/content/supported_tools/parsers/file/osv_scanner.md @@ -8,7 +8,7 @@ Use [OSV-Scanner](https://github.com/google/osv-scanner) to find existing vulner Sample OSV Scanner output can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/osv_scanner). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/outpost24.md b/docs/content/supported_tools/parsers/file/outpost24.md index 8d56030c2f5..b662fc46d15 100644 --- a/docs/content/supported_tools/parsers/file/outpost24.md +++ b/docs/content/supported_tools/parsers/file/outpost24.md @@ -8,7 +8,7 @@ Import Outpost24 endpoint vulnerability scan in XML format. Sample Outpost24 Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/outpost24). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/php_security_audit_v2.md b/docs/content/supported_tools/parsers/file/php_security_audit_v2.md index 69454c6a143..a5375db8415 100644 --- a/docs/content/supported_tools/parsers/file/php_security_audit_v2.md +++ b/docs/content/supported_tools/parsers/file/php_security_audit_v2.md @@ -8,7 +8,7 @@ Import PHP Security Audit v2 Scan in JSON format. Sample PHP Security Audit v2 scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/php_security_audit_v2). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/php_symfony_security_check.md b/docs/content/supported_tools/parsers/file/php_symfony_security_check.md index dd15ca0b17b..9b88af5434c 100644 --- a/docs/content/supported_tools/parsers/file/php_symfony_security_check.md +++ b/docs/content/supported_tools/parsers/file/php_symfony_security_check.md @@ -8,7 +8,7 @@ Import results from the PHP Symfony Security Checker. Sample PHP Symfony Security Checker scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/php_symfony_security_check). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - vulnerability ids diff --git a/docs/content/supported_tools/parsers/file/picus.md b/docs/content/supported_tools/parsers/file/picus.md index 1b34592051f..0ffb470d636 100644 --- a/docs/content/supported_tools/parsers/file/picus.md +++ b/docs/content/supported_tools/parsers/file/picus.md @@ -21,7 +21,7 @@ DefectDojo imports a single scan file at a time and does not unpack archives. If ## Default Deduplication Hashcode Fields -Picus findings deduplicate using the hashcode algorithm on a single stable [hashcode field](/en/working_with_findings/finding_deduplication/about_deduplication/), the tool-native action identifier: +Picus findings deduplicate using the hashcode algorithm on a single stable [hashcode field](/triage_findings/finding_deduplication/about_deduplication/), the tool-native action identifier: - vuln_id_from_tool (populated from the Picus `actionId`) diff --git a/docs/content/supported_tools/parsers/file/pip_audit.md b/docs/content/supported_tools/parsers/file/pip_audit.md index b734fa34c3e..300e375aed8 100644 --- a/docs/content/supported_tools/parsers/file/pip_audit.md +++ b/docs/content/supported_tools/parsers/file/pip_audit.md @@ -42,7 +42,7 @@ Sample pip-audit Scan scans can be found [here](https://github.com/DefectDojo/dj [pip-audit](https://pypi.org/project/pip-audit/) ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - vuln id from tool - component name diff --git a/docs/content/supported_tools/parsers/file/pmd.md b/docs/content/supported_tools/parsers/file/pmd.md index cf77b78f180..b51007b8466 100644 --- a/docs/content/supported_tools/parsers/file/pmd.md +++ b/docs/content/supported_tools/parsers/file/pmd.md @@ -8,7 +8,7 @@ CSV Report Sample PMD Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/pmd). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/popeye.md b/docs/content/supported_tools/parsers/file/popeye.md index fe953f3e969..8c57cc97034 100644 --- a/docs/content/supported_tools/parsers/file/popeye.md +++ b/docs/content/supported_tools/parsers/file/popeye.md @@ -68,7 +68,7 @@ To match it to DefectDojo severity formula, Secerity 0 (Ok) findings from Popeye Sample Popeye scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/popeye). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/progpilot.md b/docs/content/supported_tools/parsers/file/progpilot.md index 586866b1db3..4d09f664bac 100644 --- a/docs/content/supported_tools/parsers/file/progpilot.md +++ b/docs/content/supported_tools/parsers/file/progpilot.md @@ -1,6 +1,8 @@ --- title: "Progpilot" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/progpilot/" --- This parser imports the Progpilot SAST JSON output. The scanner can be found [here](https://github.com/designsecurity/progpilot). @@ -8,7 +10,7 @@ This parser imports the Progpilot SAST JSON output. The scanner can be found [he Sample Progpilot Parser scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/progpilot). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/prowler.md b/docs/content/supported_tools/parsers/file/prowler.md index 4200f266375..1bf4d898dcc 100644 --- a/docs/content/supported_tools/parsers/file/prowler.md +++ b/docs/content/supported_tools/parsers/file/prowler.md @@ -8,7 +8,7 @@ This parser imports Prowler Scan files in JSON and CSV format. The AWS, GCP, Azu Sample Prowler scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/prowler). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/ptart.md b/docs/content/supported_tools/parsers/file/ptart.md index 15b7632a93b..f6e0fc6ddd8 100644 --- a/docs/content/supported_tools/parsers/file/ptart.md +++ b/docs/content/supported_tools/parsers/file/ptart.md @@ -13,7 +13,7 @@ Reports can be exported to JSON format from the PTART web UI, and imported into Sample scan data for testing purposes can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/ptart). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/pwn_sast.md b/docs/content/supported_tools/parsers/file/pwn_sast.md index bcd41dfa08d..449900a7dcd 100644 --- a/docs/content/supported_tools/parsers/file/pwn_sast.md +++ b/docs/content/supported_tools/parsers/file/pwn_sast.md @@ -1,6 +1,8 @@ --- title: "PWN Security Automation Framework" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/pwn_sast/" --- - (Main Page)\[\] - pwn_sast: Import the JSON results generated by the pwn_sast Driver. This driver scans source code repositories for security anti-patterns that may result in vulnerability identification. @@ -10,7 +12,7 @@ toc_hide: true Sample PWN Security Automation Framework scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/pwn_sast). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/qualys.md b/docs/content/supported_tools/parsers/file/qualys.md index 18c7d1558b6..fdb10e570e8 100644 --- a/docs/content/supported_tools/parsers/file/qualys.md +++ b/docs/content/supported_tools/parsers/file/qualys.md @@ -1,6 +1,8 @@ --- title: "Qualys Scan" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/qualys/" --- Qualys output files can be imported in API XML format. Qualys output files can be imported in WebGUI XML format. @@ -21,7 +23,7 @@ A CSV formatted Qualys Scan Report can also be used. Ensure the following values Sample Qualys Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/qualys). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/qualys_hacker_guardian.md b/docs/content/supported_tools/parsers/file/qualys_hacker_guardian.md index 99843c4a708..d0d48671579 100644 --- a/docs/content/supported_tools/parsers/file/qualys_hacker_guardian.md +++ b/docs/content/supported_tools/parsers/file/qualys_hacker_guardian.md @@ -9,7 +9,7 @@ Qualys Hacker Guardian CSV export Sample Qualys Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/qualys_hacker_guardian). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/qualys_infrascan_webgui.md b/docs/content/supported_tools/parsers/file/qualys_infrascan_webgui.md index 8cb0776f16d..ddb079b1f3f 100644 --- a/docs/content/supported_tools/parsers/file/qualys_infrascan_webgui.md +++ b/docs/content/supported_tools/parsers/file/qualys_infrascan_webgui.md @@ -8,7 +8,7 @@ Qualys WebGUI output files can be imported in XML format. Sample Qualys Infrastructure Scan (WebGUI XML) scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/qualys_infrascan_webgui). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/qualys_vmdr.md b/docs/content/supported_tools/parsers/file/qualys_vmdr.md index a2b76dcf132..24839569d7a 100644 --- a/docs/content/supported_tools/parsers/file/qualys_vmdr.md +++ b/docs/content/supported_tools/parsers/file/qualys_vmdr.md @@ -27,7 +27,7 @@ The parser uses `DEDUPE_ALGO_UNIQUE_ID_FROM_TOOL_OR_HASH_CODE`, which tries `uni **Hashcode fields:** `title`, `component_name`, `vuln_id_from_tool` -For more information, see [About Deduplication](/en/working_with_findings/finding_deduplication/about_deduplication/). +For more information, see [About Deduplication](/triage_findings/finding_deduplication/about_deduplication/). ### Sample Scan Data diff --git a/docs/content/supported_tools/parsers/file/qualys_webapp.md b/docs/content/supported_tools/parsers/file/qualys_webapp.md index 89bda9c36d1..af17acaeab4 100644 --- a/docs/content/supported_tools/parsers/file/qualys_webapp.md +++ b/docs/content/supported_tools/parsers/file/qualys_webapp.md @@ -8,7 +8,7 @@ Qualys WebScan output files can be imported in XML format. Sample Qualys Webapp Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/qualys_webapp). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/rapplex.md b/docs/content/supported_tools/parsers/file/rapplex.md index a9ef2c3e797..bc95a34d152 100644 --- a/docs/content/supported_tools/parsers/file/rapplex.md +++ b/docs/content/supported_tools/parsers/file/rapplex.md @@ -9,7 +9,7 @@ Import JSON report of [Rapplex - Web Application Security Scanner](https://rappl Sample Rapplex scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/rapplex). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - endpoints diff --git a/docs/content/supported_tools/parsers/file/redhatsatellite.md b/docs/content/supported_tools/parsers/file/redhatsatellite.md index 169037031f2..34b5380c665 100644 --- a/docs/content/supported_tools/parsers/file/redhatsatellite.md +++ b/docs/content/supported_tools/parsers/file/redhatsatellite.md @@ -8,7 +8,7 @@ You can import a JSON report which was retrieved through the REST API of Red Hat Sample Red Hat Satellite scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/redhatsatellite). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - description - severity diff --git a/docs/content/supported_tools/parsers/file/retirejs.md b/docs/content/supported_tools/parsers/file/retirejs.md index 54490c2ed81..2e64f628c78 100644 --- a/docs/content/supported_tools/parsers/file/retirejs.md +++ b/docs/content/supported_tools/parsers/file/retirejs.md @@ -8,7 +8,7 @@ Retire.js JavaScript scan (\--js) output file can be imported in JSON format. Sample Retire.js scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/retirejs). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/risk_recon.md b/docs/content/supported_tools/parsers/file/risk_recon.md index 10d919601ed..6eb5577673d 100644 --- a/docs/content/supported_tools/parsers/file/risk_recon.md +++ b/docs/content/supported_tools/parsers/file/risk_recon.md @@ -60,7 +60,7 @@ Import findings from Risk Recon via the API. Configure your own JSON report as f Sample Risk Recon API Importer scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/risk_recon). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/rubocop.md b/docs/content/supported_tools/parsers/file/rubocop.md index 628e86f0e79..77a4fa7fb68 100644 --- a/docs/content/supported_tools/parsers/file/rubocop.md +++ b/docs/content/supported_tools/parsers/file/rubocop.md @@ -8,7 +8,7 @@ Import Rubocop JSON scan report (with option -f json). Sample Rubocop Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/rubocop). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - vuln id from tool - file path diff --git a/docs/content/supported_tools/parsers/file/rusty_hog.md b/docs/content/supported_tools/parsers/file/rusty_hog.md index d2de23af1f7..13516b0888c 100644 --- a/docs/content/supported_tools/parsers/file/rusty_hog.md +++ b/docs/content/supported_tools/parsers/file/rusty_hog.md @@ -20,7 +20,7 @@ You can either select "Rusty Hog Scan" directly, or specify the sub scanner (e.g Sample Rusty Hog parser scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/rusty_hog). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - file path - payload diff --git a/docs/content/supported_tools/parsers/file/sarif.md b/docs/content/supported_tools/parsers/file/sarif.md index e9f5ebad0c4..2d9e1f427ae 100644 --- a/docs/content/supported_tools/parsers/file/sarif.md +++ b/docs/content/supported_tools/parsers/file/sarif.md @@ -1,6 +1,8 @@ --- title: "SARIF" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/sarif/" --- OASIS Static Analysis Results Interchange Format (SARIF). SARIF is supported by many tools. More details about the format here: diff --git a/docs/content/supported_tools/parsers/file/scantist.md b/docs/content/supported_tools/parsers/file/scantist.md index 6570bdcc35b..443657c4e1e 100644 --- a/docs/content/supported_tools/parsers/file/scantist.md +++ b/docs/content/supported_tools/parsers/file/scantist.md @@ -9,7 +9,7 @@ Here you can find more information: Sample Scantist Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/scantist). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/scout_suite.md b/docs/content/supported_tools/parsers/file/scout_suite.md index 424254b2078..2207b29e127 100644 --- a/docs/content/supported_tools/parsers/file/scout_suite.md +++ b/docs/content/supported_tools/parsers/file/scout_suite.md @@ -12,7 +12,7 @@ different Cloud projects. See Sample ScoutSuite scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/scout_suite). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - file path - vuln id from tool diff --git a/docs/content/supported_tools/parsers/file/semgrep.md b/docs/content/supported_tools/parsers/file/semgrep.md index b5fc4ade9c7..e421170ebe1 100644 --- a/docs/content/supported_tools/parsers/file/semgrep.md +++ b/docs/content/supported_tools/parsers/file/semgrep.md @@ -1,6 +1,8 @@ --- title: "Semgrep JSON Report" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/semgrep/" --- Import Semgrep output (--json) @@ -22,7 +24,7 @@ finding title reflects where the rule file lives. Sample Semgrep JSON Report scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/semgrep). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/skf.md b/docs/content/supported_tools/parsers/file/skf.md index 67f3a173751..3e29bbbc620 100644 --- a/docs/content/supported_tools/parsers/file/skf.md +++ b/docs/content/supported_tools/parsers/file/skf.md @@ -8,7 +8,7 @@ Output of SKF Sprint summary export. Sample SKF Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/skf). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/snyk.md b/docs/content/supported_tools/parsers/file/snyk.md index 1d6757a872a..ebe465ba4cd 100644 --- a/docs/content/supported_tools/parsers/file/snyk.md +++ b/docs/content/supported_tools/parsers/file/snyk.md @@ -105,7 +105,7 @@ For teams running Snyk across multiple applications and repositories: ## Default Deduplication Hashcode Fields By default, DefectDojo identifies duplicate Findings using these -[hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +[hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - vuln id from tool - file path diff --git a/docs/content/supported_tools/parsers/file/snyk_code.md b/docs/content/supported_tools/parsers/file/snyk_code.md index 31289e8ed6d..f7b1d989abf 100644 --- a/docs/content/supported_tools/parsers/file/snyk_code.md +++ b/docs/content/supported_tools/parsers/file/snyk_code.md @@ -1,6 +1,8 @@ --- title: "Snyk Code" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/snyk_code/" --- Snyk output file (snyk code test \--sarif \> snyk.json) can be imported in JSON SARIF format. @@ -8,7 +10,7 @@ Snyk output file (snyk code test \--sarif \> snyk.json) can be imported in JSON Sample Snyk Code scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/snyk_code). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - vuln id from tool - file path diff --git a/docs/content/supported_tools/parsers/file/snyk_issue_api.md b/docs/content/supported_tools/parsers/file/snyk_issue_api.md index ba4ba2a8b54..12fea53a205 100644 --- a/docs/content/supported_tools/parsers/file/snyk_issue_api.md +++ b/docs/content/supported_tools/parsers/file/snyk_issue_api.md @@ -61,7 +61,7 @@ The impact field combines multiple pieces of information: - Line numbers: Only the starting line is stored in the Finding model, but both start and end lines are included in the impact field for reference ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - unique id from tool - file path \ No newline at end of file diff --git a/docs/content/supported_tools/parsers/file/solar_appscreener.md b/docs/content/supported_tools/parsers/file/solar_appscreener.md index 373a41c9fc1..6af938dcb9e 100644 --- a/docs/content/supported_tools/parsers/file/solar_appscreener.md +++ b/docs/content/supported_tools/parsers/file/solar_appscreener.md @@ -8,7 +8,7 @@ Solar Appscreener report file can be imported in CSV format from Detailed_Result Sample Solar Appscreener Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/solar_appscreener). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - file path diff --git a/docs/content/supported_tools/parsers/file/sonarqube.md b/docs/content/supported_tools/parsers/file/sonarqube.md index add4d4199cb..082bbe12f52 100644 --- a/docs/content/supported_tools/parsers/file/sonarqube.md +++ b/docs/content/supported_tools/parsers/file/sonarqube.md @@ -1,6 +1,8 @@ --- title: "SonarQube" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/sonarqube/" --- # SonarQube Scan There are two ways to retrieve findings from SonarQube. You can either use the [soprasteria package](https://github.com/soprasteria/sonar-report) or the SonarQube REST API directly. @@ -42,7 +44,7 @@ Version: \>= 1.1.0. Recommend version for both format \>= 3.1.2 ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - cwe - severity diff --git a/docs/content/supported_tools/parsers/file/sonatype.md b/docs/content/supported_tools/parsers/file/sonatype.md index 26580f78884..d8d4a6bc28e 100644 --- a/docs/content/supported_tools/parsers/file/sonatype.md +++ b/docs/content/supported_tools/parsers/file/sonatype.md @@ -8,7 +8,7 @@ JSON output. Sample Sonatype scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/sonatype). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/spotbugs.md b/docs/content/supported_tools/parsers/file/spotbugs.md index 083ef422b87..566e53943be 100644 --- a/docs/content/supported_tools/parsers/file/spotbugs.md +++ b/docs/content/supported_tools/parsers/file/spotbugs.md @@ -8,7 +8,7 @@ XML report of textui cli. Sample SpotBugs scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/spotbugs). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - cwe - severity diff --git a/docs/content/supported_tools/parsers/file/ssh_audit.md b/docs/content/supported_tools/parsers/file/ssh_audit.md index 3910f9a6d29..86850cb4245 100644 --- a/docs/content/supported_tools/parsers/file/ssh_audit.md +++ b/docs/content/supported_tools/parsers/file/ssh_audit.md @@ -8,7 +8,7 @@ Import JSON output of ssh_audit report. See Sample TFSec scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/tfsec). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - severity - vuln id from tool diff --git a/docs/content/supported_tools/parsers/file/threagile.md b/docs/content/supported_tools/parsers/file/threagile.md index ff238fca928..c943d20d534 100644 --- a/docs/content/supported_tools/parsers/file/threagile.md +++ b/docs/content/supported_tools/parsers/file/threagile.md @@ -88,7 +88,7 @@ Parser expects an array of finding. All properties are strings. Required fields Sample Threagile scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/threagile). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/threat_composer.md b/docs/content/supported_tools/parsers/file/threat_composer.md index a6ba19957ae..77597607886 100644 --- a/docs/content/supported_tools/parsers/file/threat_composer.md +++ b/docs/content/supported_tools/parsers/file/threat_composer.md @@ -9,7 +9,7 @@ This DefectDojo parser accepts JSON files from Threat Composer. The tool support Sample scan data for testing purposes can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/threat_composer). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/trivy.md b/docs/content/supported_tools/parsers/file/trivy.md index 4f006bc6336..996fe9f607f 100644 --- a/docs/content/supported_tools/parsers/file/trivy.md +++ b/docs/content/supported_tools/parsers/file/trivy.md @@ -1,6 +1,8 @@ --- title: "Trivy" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/trivy/" --- JSON report of [trivy scanner](https://github.com/aquasecurity/trivy). @@ -25,7 +27,7 @@ If you want to exclude certain status from being imported into Defect Dojo, plea Sample Trivy scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/trivy). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/trivy_operator.md b/docs/content/supported_tools/parsers/file/trivy_operator.md index 4a628aa6627..7ff0f358355 100644 --- a/docs/content/supported_tools/parsers/file/trivy_operator.md +++ b/docs/content/supported_tools/parsers/file/trivy_operator.md @@ -10,7 +10,7 @@ To import the generated Vulnerability Reports, you can also use the [trivy-dojo- Sample Trivy Operator scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/trivy_operator). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/trufflehog.md b/docs/content/supported_tools/parsers/file/trufflehog.md index 25e87f78308..a7377dd3d0e 100644 --- a/docs/content/supported_tools/parsers/file/trufflehog.md +++ b/docs/content/supported_tools/parsers/file/trufflehog.md @@ -1,6 +1,8 @@ --- title: "Trufflehog" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/trufflehog/" --- JSON Output of Trufflehog. Supports version 2 and 3 of https://github.com/trufflesecurity/trufflehog @@ -8,7 +10,7 @@ JSON Output of Trufflehog. Supports version 2 and 3 of https://github.com/truffl Sample Trufflehog scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/trufflehog). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/trufflehog3.md b/docs/content/supported_tools/parsers/file/trufflehog3.md index 636619abd16..94238278d59 100644 --- a/docs/content/supported_tools/parsers/file/trufflehog3.md +++ b/docs/content/supported_tools/parsers/file/trufflehog3.md @@ -8,7 +8,7 @@ JSON Output of Trufflehog3, a fork of TruffleHog located at https://github.com/f Sample Trufflehog3 scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/trufflehog3). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/trustwave.md b/docs/content/supported_tools/parsers/file/trustwave.md index cca19d71331..c8e88d62420 100644 --- a/docs/content/supported_tools/parsers/file/trustwave.md +++ b/docs/content/supported_tools/parsers/file/trustwave.md @@ -41,7 +41,7 @@ Sample Trustwave scans can be found in the [unit tests folder](https://github.co [Trustwave](https://www.trustwave.com/en-us/) provides vulnerability scanning services through their SecureConnect platform. ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/trustwave_fusion_api.md b/docs/content/supported_tools/parsers/file/trustwave_fusion_api.md index 010a7b846d6..c26f79ff0f9 100644 --- a/docs/content/supported_tools/parsers/file/trustwave_fusion_api.md +++ b/docs/content/supported_tools/parsers/file/trustwave_fusion_api.md @@ -8,7 +8,7 @@ Trustwave Fusion API report file can be imported in JSON format Sample Trustwave Fusion API Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/trustwave_fusion_api). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/twistlock.md b/docs/content/supported_tools/parsers/file/twistlock.md index 85d27e64832..fa3a677f03b 100644 --- a/docs/content/supported_tools/parsers/file/twistlock.md +++ b/docs/content/supported_tools/parsers/file/twistlock.md @@ -14,7 +14,7 @@ The CSV output from the UI is now also accepted. Sample Twistlock scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/twistlock). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/vcg.md b/docs/content/supported_tools/parsers/file/vcg.md index 5382919da29..55f9788cb23 100644 --- a/docs/content/supported_tools/parsers/file/vcg.md +++ b/docs/content/supported_tools/parsers/file/vcg.md @@ -8,7 +8,7 @@ VCG output can be imported in CSV or Xml formats. Sample Visual Code Grepper (VCG) scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/vcg). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/veracode.md b/docs/content/supported_tools/parsers/file/veracode.md index 45e826fd2f2..93262297077 100644 --- a/docs/content/supported_tools/parsers/file/veracode.md +++ b/docs/content/supported_tools/parsers/file/veracode.md @@ -51,7 +51,7 @@ Veracode reports can be ingested in either XML or JSON Format Sample Veracode scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/veracode). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/veracode_sca.md b/docs/content/supported_tools/parsers/file/veracode_sca.md index ff56789eb11..dfc7b737888 100644 --- a/docs/content/supported_tools/parsers/file/veracode_sca.md +++ b/docs/content/supported_tools/parsers/file/veracode_sca.md @@ -1,6 +1,8 @@ --- title: "Veracode SourceClear" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/veracode_sca/" --- Import Project CSV or JSON report @@ -8,7 +10,7 @@ Import Project CSV or JSON report Sample Veracode SourceClear scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/veracode_sca). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - vulnerability ids diff --git a/docs/content/supported_tools/parsers/file/wapiti.md b/docs/content/supported_tools/parsers/file/wapiti.md index cf272f8ee4a..0e5d84776f0 100644 --- a/docs/content/supported_tools/parsers/file/wapiti.md +++ b/docs/content/supported_tools/parsers/file/wapiti.md @@ -8,7 +8,7 @@ Import XML report. Sample Wapiti Scan scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/wapiti). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/wazuh.md b/docs/content/supported_tools/parsers/file/wazuh.md index e53e8feb5df..1ae9b199fe0 100644 --- a/docs/content/supported_tools/parsers/file/wazuh.md +++ b/docs/content/supported_tools/parsers/file/wazuh.md @@ -1,6 +1,8 @@ --- title: "Wazuh Scanner" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/wazuh/" --- ### File Types @@ -52,7 +54,7 @@ Parser expects a .json file structured as below. Sample Wazuh Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/wazuh). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/wfuzz.md b/docs/content/supported_tools/parsers/file/wfuzz.md index 945ccd233ff..dd7aa1d2d90 100644 --- a/docs/content/supported_tools/parsers/file/wfuzz.md +++ b/docs/content/supported_tools/parsers/file/wfuzz.md @@ -18,7 +18,7 @@ missing | Low Sample Wfuzz JSON importer scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/wfuzz). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/whispers.md b/docs/content/supported_tools/parsers/file/whispers.md index da0be798be6..0c2f8c69db4 100644 --- a/docs/content/supported_tools/parsers/file/whispers.md +++ b/docs/content/supported_tools/parsers/file/whispers.md @@ -9,7 +9,7 @@ https://github.com/adeptex/whispers Sample Whispers scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/whispers). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - vuln id from tool - file path diff --git a/docs/content/supported_tools/parsers/file/whitehat_sentinel.md b/docs/content/supported_tools/parsers/file/whitehat_sentinel.md index 274f46d10ec..8110f4b534b 100644 --- a/docs/content/supported_tools/parsers/file/whitehat_sentinel.md +++ b/docs/content/supported_tools/parsers/file/whitehat_sentinel.md @@ -8,7 +8,7 @@ WhiteHat Sentinel output from api/vuln/query_site can be imported in JSON format Sample WhiteHat Sentinel scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/whitehat_sentinel). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/wiz.md b/docs/content/supported_tools/parsers/file/wiz.md index 43fd6818e15..71e768209b3 100644 --- a/docs/content/supported_tools/parsers/file/wiz.md +++ b/docs/content/supported_tools/parsers/file/wiz.md @@ -1,6 +1,8 @@ --- title: "Wiz Scanner Parser" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/wiz/" --- The [Wiz](https://www.wiz.io/) parser for DefectDojo supports imports from both Wiz Scanner Standard and SCA (Software Composition Analysis) .csv output from Wiz.io. This document details the parsing of both formats into DefectDojo field mappings, unmapped fields, and location of each field's parsing code for easier troubleshooting and analysis. @@ -29,7 +31,7 @@ To generate these files, export the findings from the Wiz platform by: Sample Wiz Scanner scans can be found in the [sample scan data folder](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/wiz). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/wizcli_dir.md b/docs/content/supported_tools/parsers/file/wizcli_dir.md index 2eb5e3aa204..67fcb5cb1b8 100644 --- a/docs/content/supported_tools/parsers/file/wizcli_dir.md +++ b/docs/content/supported_tools/parsers/file/wizcli_dir.md @@ -1,6 +1,8 @@ --- title: "Wiz-cli Dir Scanner" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/wizcli_dir/" --- This parser imports scan results from [wizcli](https://www.wiz.io/) IaC scan. You have to export scan results in JSON format so that it will be parsable within DefectDojo. `wizcli dir scan --path ./ -o scan_dir.json,json` @@ -9,7 +11,7 @@ This parser imports scan results from [wizcli](https://www.wiz.io/) IaC scan. Yo Sample Wizcli Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/wizcli_dir). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/wizcli_iac.md b/docs/content/supported_tools/parsers/file/wizcli_iac.md index f0794d82484..eda73c2abb0 100644 --- a/docs/content/supported_tools/parsers/file/wizcli_iac.md +++ b/docs/content/supported_tools/parsers/file/wizcli_iac.md @@ -1,6 +1,8 @@ --- title: "Wiz-cli IaC Scanner" toc_hide: true +aliases: + - "/en/connecting_your_tools/parsers/file/wizcli_iac/" --- This parser imports scan results from [wizcli](https://www.wiz.io/) IaC scan. You have to export scan results in JSON format so that it will be parsable within DefectDojo. `wizcli iac scan --path ./ -o scan_iac.json,json` @@ -9,7 +11,7 @@ This parser imports scan results from [wizcli](https://www.wiz.io/) IaC scan. Yo Sample Wizcli Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/wizcli_iac). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/wizcli_img.md b/docs/content/supported_tools/parsers/file/wizcli_img.md index 5311ef89148..b313ea7754e 100644 --- a/docs/content/supported_tools/parsers/file/wizcli_img.md +++ b/docs/content/supported_tools/parsers/file/wizcli_img.md @@ -9,7 +9,7 @@ This parser imports scan results from [wizcli](https://www.wiz.io/) IaC scan. Yo Sample Wizcli Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/wizcli_img). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/wpscan.md b/docs/content/supported_tools/parsers/file/wpscan.md index 2449d00cf15..534eec43cec 100644 --- a/docs/content/supported_tools/parsers/file/wpscan.md +++ b/docs/content/supported_tools/parsers/file/wpscan.md @@ -8,7 +8,7 @@ Import JSON report. Sample Wpscan Scanner scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/wpscan). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - description diff --git a/docs/content/supported_tools/parsers/file/xanitizer.md b/docs/content/supported_tools/parsers/file/xanitizer.md index 214008a35b6..4be53290d24 100644 --- a/docs/content/supported_tools/parsers/file/xanitizer.md +++ b/docs/content/supported_tools/parsers/file/xanitizer.md @@ -9,7 +9,7 @@ Import XML findings list report, preferably with parameter Sample Xanitizer scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/xanitizer). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/file/yarn_audit.md b/docs/content/supported_tools/parsers/file/yarn_audit.md index e1008c76406..d5cb410000a 100644 --- a/docs/content/supported_tools/parsers/file/yarn_audit.md +++ b/docs/content/supported_tools/parsers/file/yarn_audit.md @@ -8,7 +8,7 @@ Import Yarn Audit scan report in JSON format. Use something like `yarn audit --j Sample Yarn Audit scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/yarn_audit). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - severity diff --git a/docs/content/supported_tools/parsers/file/zap.md b/docs/content/supported_tools/parsers/file/zap.md index 87ccf9ca811..ced4a7c0e84 100644 --- a/docs/content/supported_tools/parsers/file/zap.md +++ b/docs/content/supported_tools/parsers/file/zap.md @@ -8,7 +8,7 @@ ZAP XML report format (with or without requests and responses). Sample Zed Attack Proxy scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/zap). ### Default Deduplication Hashcode Fields -By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/en/working_with_findings/finding_deduplication/about_deduplication/): +By default, DefectDojo identifies duplicate Findings using these [hashcode fields](/triage_findings/finding_deduplication/about_deduplication/): - title - cwe diff --git a/docs/content/supported_tools/parsers/generic_findings_import.md b/docs/content/supported_tools/parsers/generic_findings_import.md index 899ec666c18..bbf6883c52f 100644 --- a/docs/content/supported_tools/parsers/generic_findings_import.md +++ b/docs/content/supported_tools/parsers/generic_findings_import.md @@ -2,6 +2,8 @@ title: "Using Generic Findings Import" toc_hide: true weight: 2 +aliases: + - "/en/connecting_your_tools/parsers/generic_findings_import/" --- Open-source and Pro users can use Generic Findings Import as a method to ingest JSON or CSV files into DefectDojo which are not already in the supported Tools list. diff --git a/docs/content/supported_tools/parsers/universal_parser.md b/docs/content/supported_tools/parsers/universal_parser.md index ab9c15c4b8f..f3ea9fbd02e 100644 --- a/docs/content/supported_tools/parsers/universal_parser.md +++ b/docs/content/supported_tools/parsers/universal_parser.md @@ -5,6 +5,8 @@ draft: "false" audience: pro weight: 1 pro-feature: true +aliases: + - "/en/connecting_your_tools/parsers/universal_parser/" --- Note: The Universal Parser is only available in DefectDojo Pro. diff --git a/docs/content/triage_findings/finding_deduplication/_index.md b/docs/content/triage_findings/finding_deduplication/_index.md index 80844d5f735..3384ba12335 100644 --- a/docs/content/triage_findings/finding_deduplication/_index.md +++ b/docs/content/triage_findings/finding_deduplication/_index.md @@ -5,4 +5,6 @@ draft: false type: docs weight: 3 exclude_search: true +aliases: + - "/en/working_with_findings/finding_deduplication/" --- diff --git a/docs/content/triage_findings/finding_scoring/cvss_support.md b/docs/content/triage_findings/finding_scoring/cvss_support.md index 79a486be561..9ed9b02d178 100644 --- a/docs/content/triage_findings/finding_scoring/cvss_support.md +++ b/docs/content/triage_findings/finding_scoring/cvss_support.md @@ -2,6 +2,8 @@ title: "CVSS Version Support" description: "Which CVSS versions DefectDojo stores, displays, and accepts on Findings" weight: 1 +aliases: + - "/triage_findings/cvss_support/" --- DefectDojo supports CVSS metadata on Findings, including the CVSS 4.0 standard. This page describes which CVSS versions are stored end-to-end, where you can enter or view them, and what to expect from parser-side coverage. diff --git a/docs/content/triage_findings/findings_workflows/OS__risk_acceptance.md b/docs/content/triage_findings/findings_workflows/OS__risk_acceptance.md index 1d62519edae..6261422f275 100644 --- a/docs/content/triage_findings/findings_workflows/OS__risk_acceptance.md +++ b/docs/content/triage_findings/findings_workflows/OS__risk_acceptance.md @@ -3,6 +3,9 @@ title: "Risk Acceptances" description: "Leveraging Risk Acceptances in DefectDojo OS" audience: opensource weight: 2 +aliases: + - "/triage_findings/findings_workflows/risk_acceptances" + - "/triage_findings/findings_workflows/risk_acceptances/" --- **Risk Acceptances** are a special status that can be applied to Findings to formally document and operationalize the decision to acknowledge them without immediately remediating them. diff --git a/docs/content/triage_findings/findings_workflows/_index.md b/docs/content/triage_findings/findings_workflows/_index.md index bd2ab8e34aa..85443bfde84 100644 --- a/docs/content/triage_findings/findings_workflows/_index.md +++ b/docs/content/triage_findings/findings_workflows/_index.md @@ -5,4 +5,6 @@ draft: false weight: 1 type: docs exclude_search: true +aliases: + - "/en/working_with_findings/findings_workflows/" --- diff --git a/docs/content/triage_findings/findings_workflows/exporting.md b/docs/content/triage_findings/findings_workflows/exporting.md index dabd779d940..e95fabfc21b 100644 --- a/docs/content/triage_findings/findings_workflows/exporting.md +++ b/docs/content/triage_findings/findings_workflows/exporting.md @@ -4,6 +4,7 @@ description: "Export findings and engagements as CSV or Excel" weight: 4 audience: opensource aliases: + - "/open_source/exporting/" - /en/open_source/exporting --- diff --git a/docs/netlify.toml b/docs/netlify.toml index fbda65b7a4b..02ff38a9dc9 100644 --- a/docs/netlify.toml +++ b/docs/netlify.toml @@ -31,6 +31,36 @@ autoLaunch = false # Redirects and rewrites — https://docs.netlify.com/routing/redirects/#syntax-for-the-netlify-configuration-file +# +# Retired URLs are normally handled with Hugo `aliases:` in the target page's +# front matter. These four cannot be: +# +# - The SSO pages differ from their live URL only by case, and Hugo lowercases +# alias output, so an alias would collide with the page's own path. +# - /admin/ and /triage_findings/ are section list pages with no _index.md, so +# there is no front matter to carry an alias. + +[[redirects]] + from = "/admin/sso/PRO__auth0/" + to = "/admin/sso/pro__auth0/" + status = 301 + force = true + +[[redirects]] + from = "/admin/sso/PRO__google/" + to = "/admin/sso/pro__google/" + status = 301 + force = true + +[[redirects]] + from = "/en/customize_dojo/" + to = "/admin/" + status = 301 + +[[redirects]] + from = "/en/working_with_findings/" + to = "/triage_findings/" + status = 301 # Custom headers — https://docs.netlify.com/routing/headers/#syntax-for-the-netlify-configuration-file [[headers]] From 20213061fb8e012bc58d472e3a2060e5007a111d Mon Sep 17 00:00:00 2001 From: Paul Osinski Date: Mon, 17 Aug 2026 17:21:07 -0400 Subject: [PATCH 2/2] fix lychee error --- docs/content/releases/pro/changelog.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/releases/pro/changelog.md b/docs/content/releases/pro/changelog.md index 37b28b26797..206ca4785db 100644 --- a/docs/content/releases/pro/changelog.md +++ b/docs/content/releases/pro/changelog.md @@ -690,7 +690,7 @@ The Priority Insights dashboard can quickly render a list of all SOC or AppSec F - **(Calendar)** New filters have been added to Calendar view: Unassigned Lead, and Engagement/Test Type. - **(Dashboard)** Added Finding Status filter for Dashboard tiles. -- **(Engagements)** A repository URI can be added to an Engagement via **Edit Engagement > Optional Fields > Repo**. If this field is set, Findings under that Engagement will automatically generate clickable links to the source code if File Path is set on the Finding. See [docs](/asset_modelling/OS_hierarchy/OS__source-code-repositories/) for more details. +- **(Engagements)** A repository URI can be added to an Engagement via **Edit Engagement > Optional Fields > Repo**. If this field is set, Findings under that Engagement will automatically generate clickable links to the source code if File Path is set on the Finding. See [docs](/asset_modelling/os_hierarchy/os__source-code-repositories/) for more details. - **(Findings)** Added "Jira Issue URL" column to the CSV export of Finding tables. - **(Metrics)** Priority Dashboard has been added to Metrics, to display your organization's risk profile at a glance. ![image](images/pro_dashboard_priority.png)