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/generic_findings_import.md
+16-1Lines changed: 16 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ You can use Generic Findings Import as a method to ingest JSON or CSV files into
9
9
Files uploaded using Generic Findings Import must conform to the accepted format with respect to CSV column headers / JSON attributes.
10
10
11
11
These attributes are supported for CSV:
12
+
12
13
- Date: Date of the finding in mm/dd/yyyy format.
13
14
- Title: Title of the finding
14
15
- CweId: Cwe identifier, must be an integer value.
@@ -104,18 +105,32 @@ Example:
104
105
}
105
106
```
106
107
107
-
This parser supports an attribute `name` and `type` to be able to define `TestType`. Based on this, you can define custom `HASHCODE_FIELDS` or `DEDUPLICATION_ALGORITHM` in the settings.
108
+
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).
108
117
109
118
Example:
110
119
111
120
```JSON
112
121
{
113
122
"name": "My wonderful report",
114
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,
115
129
"findings": [
116
130
]
117
131
}
118
132
```
119
133
120
134
### Sample Scan Data
135
+
121
136
Sample Generic Findings Import scans can be found [here](https://github.com/DefectDojo/django-DefectDojo/tree/master/unittests/scans/generic).
0 commit comments