Skip to content

Commit 796d05b

Browse files
committed
feat: Add Debricked support for GitLab SCA Import (implements fortify#52 for GitLab)
1 parent 4e792c5 commit 796d05b

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

doc-resources/repo-usage.md

+6-4
Original file line numberDiff line numberDiff line change
@@ -446,7 +446,7 @@ fortify_scanning:
446446
dast: gl-fortify-dast.json
447447
```
448448
449-
The configuration file `/config/FoDToGitLab.yml` used in this example outputs all available GitLab reports. Alternatively, you can use `/config/FoDToGitLabSAST.yml` or `/config/FoDToGitLabDAST.yml` to output only a SAST or DAST report respectively. Note that contrary to the [SSC implementation](#ssc-to-gitlab), outputting Sonatype/dependency scanning
449+
The configuration file `/config/FoDToGitLab.yml` used in this example outputs all available GitLab reports. Alternatively, you can use `/config/FoDToGitLabSAST.yml` or `/config/FoDToGitLabDAST.yml` to output only a SAST or DAST report respectively. Note that contrary to the [SSC implementation](#ssc-to-gitlab), outputting Debricked or Sonatype dependency scanning
450450
results from FoD is not yet supported.
451451
452452
As described in the [CI/CD Integration](#cicd-integration) section, you can optionally combine this with other Fortify tools to create a full workflow that scans your code and makes the results available on GitLab.
@@ -471,11 +471,12 @@ fortify_scanning:
471471
artifacts:
472472
reports:
473473
sast: gl-fortify-sast.json
474-
dast: gl-fortify-dast.json
475-
dependency_scanning: gl-fortify-depscan.json
474+
dependency_scanning: gl-fortify-debricked-depscan.json
475+
# Or for Sonatype Nexus IQ use: gl-fortify-sonatype-depscan.json
476476
```
477477
478-
The configuration file `/config/SSCToGitLab.yml` used in this example outputs all available GitLab reports. Alternatively, you can use `/config/SSCToGitLabSAST.yml`, `/config/SSCToGitLabDAST.yml`, or `/config/SSCToGitLabSonatype.yml` to output only a SAST, DAST or Sonatype report respectively.
478+
The configuration file `/config/SSCToGitLab.yml` used in this example outputs all available GitLab reports. Alternatively, you can use `/config/SSCToGitLabSAST.yml`, `/config/SSCToGitLabDAST.yml`, `/config/SSCToGitLabDebricked.yml` or `/config/SSCToGitLabSonatype.yml`
479+
to output only a SAST, DAST, Debricked SCA or Sonatype SCA report respectively.
479480
480481
As described in the [CI/CD Integration](#cicd-integration) section, you can optionally combine this with other Fortify tools to create a full workflow that scans your code and makes the results available on GitLab.
481482
@@ -558,6 +559,7 @@ At the moment of writing, DefectDojo supports GitLab SAST and GitLab Dependency
558559
559560
* [Export FoD SAST results to a GitLab SAST report](#fod-to-gitlab) and import this report into DefectDojo
560561
* [Export SSC SAST results to a GitLab SAST report](#ssc-to-gitlab) and import this report into DefectDojo
562+
* [Export SSC Debricked results to a GitLab Dependency Scanning report](#ssc-to-gitlab) and import this report into DefectDojo
561563
* [Export SSC Sonatype results to a GitLab Dependency Scanning report](#ssc-to-gitlab) and import this report into DefectDojo
562564
* [Export other FoD or SSC results to CSV format](#csv-export) and import the CSV file into DefectDojo
563565

0 commit comments

Comments
 (0)