You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/en/connecting_your_tools/parsers/file/fortify.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -3,22 +3,22 @@ title: "Fortify"
3
3
toc_hide: true
4
4
---
5
5
You can either import the findings in .xml or in .fpr file format. </br>
6
-
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).
6
+
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.
7
7
8
8
### Sample Scan Data
9
9
Sample Fortify scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/fortify).
10
10
11
11
### Fortify Webinspect report formats.
12
-
Fortify Webinspect released in version 24.2 a new xml report format. This parser is able to handle both report formats. See [this issue](https://github.com/DefectDojo/django-DefectDojo/issues/12065) for further information.
12
+
Fortify Webinspect released in version 24.2 a new xml report format. This parser is able to handle both report formats. See [this issue](https://github.com/DefectDojo/django-DefectDojo/issues/12065) for further information.
13
13
14
14
#### Generate XML Output from Foritfy
15
-
This section describes how to import XML generated from a Fortify FPR. It assumes you
15
+
This section describes how to import XML generated from a Fortify FPR. It assumes you
16
16
already have, or know how to acquire, an FPR file. Once you have the FPR file you will need
17
17
use Fortify's ReportGenerator tool (located in the bin directory of your fortify install).
18
18
```FORTIFY_INSTALL_ROOT/bin/ReportGenerator```
19
19
20
20
By default, the Report Generator tool does _not_ display all issues, it will only display one
21
-
per category. To get all issues, copy the [DefaultReportDefinitionAllIssues.xml](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/fortify/DefaultReportDefinitionAllIssues.xml) to:
21
+
per category. To get all issues, copy the [DefaultReportDefinitionAllIssues.xml](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/fortify/DefaultReportDefinitionAllIssues.xml) to:
22
22
```FORTIFY_INSTALL_ROOT/Core/config/reports```
23
23
24
24
Once this is complete, you can run the following command on your .fpr file to generate the
self.assertEqual("Threaded Comments:\n2025-03-10T20:52:28.964+05:30 - (testuser): Not an issue. Handled in server config to refer to internal Artifactory\n", finding.impact)
0 commit comments