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/about_defectdojo/about_docs.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,6 +67,8 @@ Other guides for working with an Open-Source install:
67
67
68
68
If you run into trouble with an Open Source install, we highly recommend asking questions on the [OWASP Slack](https://owasp.org/slack/invite). Our community members are active on the **# defectdojo** channel and can help you with issues you’re facing.
69
69
70
+
Looking for cool DefectDojo laptop stickers? As a thank you for being a part of the DefectDojo community, you can sign up to get some free DefectDojo stickers. For more information, check out [this link](https://defectdojo.com/defectdojo-sticker-request).
71
+
70
72
### Online Demo
71
73
72
74
A running example of DefectDojo (Open-Source Edition) is available on [our demo server](https://demo.defectdojo.org), using the credentials `admin` / `1Defectdojo@demo#appsec`. The demo server is refreshed regularly and provisioned with some sample data.
Copy file name to clipboardExpand all lines: docs/content/en/changelog/changelog.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,11 @@ For Open Source release notes, please see the [Releases page on GitHub](https://
10
10
11
11
## Sept 2025: v2.50
12
12
13
+
### Sept 15, 2025: v2.50.2
14
+
15
+
***(Pro UI)** Added Any/All status filtering. Filtering by status allows you to apply either AND (inner join) logic, or OR (outer join) logic to the filter.
16
+
***(Pro UI)** Added Contact Support form for On-Premise installs.
17
+
13
18
### Sept 9, 2025: v2.50.1
14
19
15
20
***(Tools)** Removed CSV limit for Qualys HackerGuardian
Copy file name to clipboardExpand all lines: docs/content/en/connecting_your_tools/parsers/file/generic.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,9 +3,9 @@ title: 'Generic Findings Import'
3
3
toc_hide: true
4
4
---
5
5
6
-
Import Generic findings in CSV or JSON format.
6
+
Generic Findings Import can be used to import any report in CSV or JSON format.
7
7
8
-
Attributes supported for CSV:
8
+
### Supported Attributes (CSV)
9
9
10
10
- Date: Date of the finding in mm/dd/yyyy format.
11
11
- Title: Title of the finding
@@ -37,6 +37,8 @@ The CSV expects a header row with the names of the attributes.
37
37
38
38
Date fields are parsed using [dateutil.parse](https://dateutil.readthedocs.io/en/stable/parser.html) supporting a variety of formats such a YYYY-MM-DD or ISO-8601.
39
39
40
+
### Supported Attributes (JSON)
41
+
40
42
The list of supported fields in JSON format:
41
43
42
44
- title: **Required.** String
@@ -93,7 +95,7 @@ The list of supported fields in JSON format:
You can use Generic Findings Import as a method to ingest JSON or CSV files into DefectDojo which are not already in the supported parsers list.
7
+
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.
8
8
9
-
Files uploaded using Generic Findings Import must conform to the accepted format with respect to CSV column headers / JSON attributes.
9
+
Using Generic Findings Import will create a new Test Type in your DefectDojo instance called "`{The Name Of Your Test}` (Generic Findings Import)". For example, this JSON content will result in a Test Type called "Example Report (Generic Findings Import)":
10
10
11
-
These attributes are supported for CSV:
12
-
13
-
- Date: Date of the finding in mm/dd/yyyy format.
14
-
- Title: Title of the finding
15
-
- CweId: Cwe identifier, must be an integer value.
16
-
- epss_score: The probability of exploitation in the next 30 days, must be a float value between 0 and 1.0.
17
-
- epss_percentile: The proportion of all scored vulnerabilities with the same or a lower EPSS score, must be a float value between 0 and 1.0.
18
-
- Url: Url associated with the finding.
19
-
- Severity: Severity of the finding. Must be one of Info, Low, Medium, High, or Critical.
20
-
- Description: Description of the finding. Can be multiple lines if enclosed in double quotes.
21
-
- Mitigation: Possible Mitigations for the finding. Can be multiple lines if enclosed in double quotes.
22
-
- Impact: Detailed impact of the finding. Can be multiple lines if enclosed in double quotes.
23
-
- References: References associated with the finding. Can be multiple lines if enclosed in double quotes.
24
-
- Active: Indicator if the finding is active. Must be empty, TRUE or FALSE
25
-
- Verified: Indicator if the finding has been verified. Must be empty, TRUE, or FALSE
26
-
- FalsePositive: Indicator if the finding is a false positive. Must be TRUE, or FALSE.
27
-
- Duplicate: Indicator if the finding is a duplicate. Must be TRUE, or FALSE
28
-
29
-
The CSV expects a header row with the names of the attributes.
30
-
31
-
Example of JSON format:
32
-
33
-
```JSON
34
-
{
35
-
"findings": [
36
-
{
37
-
"title": "test title with endpoints as dict",
38
-
"description": "Some very long description with\n\n some UTF-8 chars à qu'il est beau",
This parser supports some additional attributes to be able to define custom `TestTypes` as well as influencing some meta fields on the `Test`:
109
-
110
-
-`name`: The internal name of the tool you are using. This is primarily informational, and used for reading the report manually.
111
-
-`type`: The name of the test type to create in DefectDojo with the suffix of `(Generic Findings Import)`. The suffix is an important identifier for future users attempting to identify the test type to supply when importing new reports. This value is very important when fetching the correct test type to import findings into, so be sure to keep the `type` consistent from import to import! As an example, a report submitted with a `type` of `Internal Company Tool` will produce a test type in DefectDojo with the title `Internal Company Tool (Generic Findings Import)`. With this newly created test type, you can define custom `HASHCODE_FIELDS` or `DEDUPLICATION_ALGORITHM` in the settings.
112
-
-`version`: The version of the tool you are using. This is primarily informational, and is used for reading the report manually and tracking format changes from version to version.
113
-
-`description`: A brief description of the test. This could be an explanation of what the tool is reporting, where the tools is maintained, who the point of contact is for the tool when issues arise, or anything in between.
114
-
-`static_tool`: Dictates that tool used is running static analysis methods to discover vulnerabilities.
115
-
-`dynamic_tool`: Dictates that tool used is running dynamic analysis methods to discover vulnerabilities.
116
-
-`soc`: Dictates that tool is used for reporting alerts from a soc (Pro Edition Only).
117
-
118
-
Example:
119
-
120
-
```JSON
121
11
{
122
-
"name": "My wonderful report",
123
-
"type": "My custom Test type",
124
-
"version": "1.0.5",
125
-
"description": "A unicorn tool that is capable of static analysis, dynamic analysis, and even capturing soc alerts!",
126
-
"static_tool": true,
127
-
"dynamic_tool": true,
128
-
"soc": true,
129
-
"findings": [
130
-
]
12
+
"name": "Example Report",
13
+
"findings": []
131
14
}
132
-
```
133
15
134
-
### Sample Scan Data
16
+
DefectDojo Pro users can also consider using the [Universal Parser](../universal_parser), a tool which allows for highly customizable JSON, XML and CSV imports.
135
17
136
-
Sample Generic Findings Import scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/generic).
18
+
For more information on supported parameters for Generic Findings Import, see the [Parser Guide](../file/generic)
0 commit comments