5
5
6
6
HeimdallTools supplies several methods to convert output from various tools to "Heimdall Data Format"(HDF) format to be viewable in Heimdall. The current converters are:
7
7
8
- 1 . [ ** aws_config_mapper** ] ( #aws_config_mapper ) - assess, audit, and evaluate AWS resources
9
- 1 . [ ** burpsuite_mapper** ] ( #burpsuite_mapper ) - commercial dynamic analysis tool
10
- 1 . [ ** dbprotect_mapper** ] ( #dbprotect_mapper ) - database vulnerability scanner
11
- 1 . [ ** fortify_mapper** ] ( #fortify_mapper ) - commercial static code analysis tool
12
- 1 . [ ** jfrog_xray_mapper** ] ( #jfrog_xray_mapper ) - package vulnerability scanner
13
- 1 . [ ** nessus_mapper** ] ( #nessus_mapper ) - commercial security scanner (supports compliance and vulnerability scans from Tenable.sc and Tenable.io)
14
- 1 . [ ** netsparker_mapper** ] ( #netsparker_mapper ) - web application security scanner
15
- 1 . [ ** nikto_mapper** ] ( #nikto_mapper ) - open-source web server scanner
16
- 1 . [ ** sarif_mapper** ] ( #sarif_mapper ) - static analysis results interchange format
8
+ 1 . [ ** asff_mapper** ] ( #asff_mapper ) - custom findings format for AWS Security Hub
9
+ 1 . [ ** aws_config_mapper** ] ( #aws_config_mapper ) - assess, audit, and evaluate AWS resources
10
+ 1 . [ ** burpsuite_mapper** ] ( #burpsuite_mapper ) - commercial dynamic analysis tool
11
+ 1 . [ ** dbprotect_mapper** ] ( #dbprotect_mapper ) - database vulnerability scanner
12
+ 1 . [ ** fortify_mapper** ] ( #fortify_mapper ) - commercial static code analysis tool
13
+ 1 . [ ** jfrog_xray_mapper** ] ( #jfrog_xray_mapper ) - package vulnerability scanner
14
+ 1 . [ ** nessus_mapper** ] ( #nessus_mapper ) - commercial security scanner (supports compliance and vulnerability scans from Tenable.sc and Tenable.io)
15
+ 1 . [ ** netsparker_mapper** ] ( #netsparker_mapper ) - web application security scanner
16
+ 1 . [ ** nikto_mapper** ] ( #nikto_mapper ) - open-source web server scanner
17
+ 1 . [ ** prowler_mapper** ] ( #prowler_mapper ) - assess, audit, harden, and facilitate incidence response for AWS resources
18
+ 1 . [ ** sarif_mapper** ] ( #sarif_mapper ) - static analysis results interchange format
17
19
1 . [ ** scoutsuite_mapper** ] ( #scoutsuite_mapper ) - multi-cloud security auditing tool
18
20
1 . [ ** snyk_mapper** ] ( #snyk_mapper ) - commercial package vulnerability scanner
19
21
1 . [ ** sonarqube_mapper** ] ( #sonarqube_mapper ) - open-source static code analysis tool
20
22
1 . [ ** xccdf_results_mapper** ] ( #xccdf_results_mapper ) - extensible configuration checklist description results format
21
- 1 . [ * scc_mapper] ( #xccdf_results_mapper ) - scap compliance checker format
23
+ 1 . [ ** scc_mapper** ] ( #xccdf_results_mapper ) - scap compliance checker format
22
24
1 . [ ** zap_mapper** ] ( #zap_mapper ) - OWASP ZAP - open-source dynamic code analysis tool
23
25
24
26
## Want to recommend a mapper for another tool? Please use these steps:
@@ -84,6 +86,27 @@ For Docker usage, replace the `heimdall_tools` command with the correct Docker c
84
86
85
87
Note that all of the above Docker commands will mount your current directory on the Docker container. Ensure that you have navigated to the directory you intend to convert files in before executing the command.
86
88
89
+ ## asff_mapper
90
+
91
+ asff_mapper translates AWS Security Finding Format results from JSON to HDF-formatted JSON so as to be viewable on Heimdall
92
+
93
+ Note: The following commands are examples to extract data via the AWS CLI that need to be fed to the mapper:
94
+
95
+ Output|Use|Command
96
+ ---|---|---
97
+ ASFF json|All the findings that will be fed into the mapper|aws securityhub get-findings > asff.json
98
+ AWS SecurityHub enabled standards json|Get all the enabled standards so you can get their identifiers|aws securityhub get-enabled-standards > asff_standards.json
99
+ AWS SecurityHub standard controls json|Get all the controls for a standard that will be fed into the mapper|aws securityhub describe-standards-controls --standards-subscription-arn "arn:aws:securityhub:us-east-1:123456789123: subscription /cis-aws-foundations-benchmark/v/1.2.0" > asff_cis_standard.json
100
+
101
+ USAGE: heimdall_tools asff_mapper -i <asff-finding-json> [--sh <standard-1-json> ... <standard-n-json>] -o <hdf-scan-results-json>
102
+
103
+ FLAGS:
104
+ -i --input -j --json <asff-finding-json> : path to ASFF findings file.
105
+ --sh --securityhub-standards --input-securityhub-standards : array of paths to AWS SecurityHub standard files.
106
+ -o --output <hdf-scan-results-json> : path to output scan-results json.
107
+
108
+ example: heimdall_tools asff_mapper -i asff_findings.json --sh aws_standard.json cis_standard.json -o asff_hdf.json
109
+
87
110
## aws_config_mapper
88
111
89
112
aws_config_mapper pulls Ruby AWS SDK data to translate AWS Config Rule results into HDF format json to be viewable in Heimdall
@@ -99,8 +122,8 @@ aws_config_mapper pulls Ruby AWS SDK data to translate AWS Config Rule results i
99
122
USAGE: heimdall_tools aws_config_mapper [OPTIONS] -o
100
123
101
124
FLAGS:
102
- -o --output : path to output scan-results json.
103
- -V --verbose : verbose run [optional].
125
+ -o --output : path to output scan-results json.
126
+ -V --verbose : verbose run [optional].
104
127
105
128
example: heimdall_tools aws_config_mapper -o aws_config_results_hdf.json
106
129
@@ -111,9 +134,9 @@ burpsuite_mapper translates an BurpSuite Pro exported XML results file into HDF
111
134
USAGE: heimdall_tools burpsuite_mapper [OPTIONS] -x -o
112
135
113
136
FLAGS:
114
- -x : path to BurpSuitePro exported XML results file.
115
- -o --output : path to output scan-results json.
116
- -V --verbose : verbose run [optional].
137
+ -x : path to BurpSuitePro exported XML results file.
138
+ -o --output : path to output scan-results json.
139
+ -V --verbose : verbose run [optional].
117
140
118
141
example: heimdall_tools burpsuite_mapper -x burpsuite_results.xml -o scan_results.json
119
142
@@ -124,9 +147,9 @@ dbprotect_mapper translates DBProtect report in `Check Results Details` format X
124
147
USAGE: heimdall_tools dbprotect_mapper [OPTIONS] -x -o
125
148
126
149
FLAGS:
127
- -x : path to DBProtect report XML file.
128
- -o --output : path to output scan-results json.
129
- -V --verbose : verbose run [optional].
150
+ -x : path to DBProtect report XML file.
151
+ -o --output : path to output scan-results json.
152
+ -V --verbose : verbose run [optional].
130
153
131
154
example: heimdall_tools dbprotect_mapper -x check_results_details_report.xml -o db_protect_hdf.json
132
155
@@ -137,9 +160,9 @@ fortify_mapper translates an Fortify results FVDL file into HDF format json to b
137
160
USAGE: heimdall_tools fortify_mapper [OPTIONS] -f -o
138
161
139
162
FLAGS:
140
- -f --fvdl : path to Fortify Scan FVDL file.
141
- -o --output : path to output scan-results json.
142
- -V --verbose : verbose run [optional].
163
+ -f --fvdl : path to Fortify Scan FVDL file.
164
+ -o --output : path to output scan-results json.
165
+ -V --verbose : verbose run [optional].
143
166
144
167
example: heimdall_tools fortify_mapper -f audit.fvdl -o scan_results.json
145
168
@@ -150,9 +173,9 @@ jfrog_xray_mapper translates an JFrog Xray results JSON file into HDF format JSO
150
173
USAGE: heimdall_tools jfrog_xray_mapper [OPTIONS] -j -o
151
174
152
175
FLAGS:
153
- -j : path to xray results JSON file.
154
- -o --output : path to output scan-results json.
155
- -V --verbose : verbose run [optional].
176
+ -j : path to xray results JSON file.
177
+ -o --output : path to output scan-results json.
178
+ -V --verbose : verbose run [optional].
156
179
157
180
example: heimdall_tools jfrog_xray_mapper -j xray_results.json -o xray_results_hdf.json
158
181
@@ -166,9 +189,9 @@ Note: A separate HDF JSON file is generated for each host reported in the Nessus
166
189
USAGE: heimdall_tools nessus_mapper [OPTIONS] -x -o
167
190
168
191
FLAGS:
169
- -x : path to Nessus-exported XML results file.
170
- -o --output_prefix : path to output scan-results json.
171
- -V --verbose : verbose run [optional].
192
+ -x : path to Nessus-exported XML results file.
193
+ -o --output_prefix : path to output scan-results json.
194
+ -V --verbose : verbose run [optional].
172
195
173
196
example: heimdall_tools nessus_mapper -x nessus-results.xml -o test-env
174
197
@@ -181,9 +204,9 @@ The current iteration only works with Netsparker Enterprise Vulnerabilities Scan
181
204
USAGE: heimdall_tools netsparker_mapper [OPTIONS] -x -o
182
205
183
206
FLAGS:
184
- -x : path to netsparker results XML file.
185
- -o --output : path to output scan-results json.
186
- -V --verbose : verbose run [optional].
207
+ -x : path to netsparker results XML file.
208
+ -o --output : path to output scan-results json.
209
+ -V --verbose : verbose run [optional].
187
210
188
211
example: heimdall_tools netsparker_mapper -x netsparker_results.xml -o netsparker_hdf.json
189
212
@@ -196,22 +219,36 @@ Note: Current this mapper only support single target Nikto Scans.
196
219
USAGE: heimdall_tools nikto_mapper [OPTIONS] -x -o
197
220
198
221
FLAGS:
199
- -j : path to Nikto results JSON file.
200
- -o --output_prefix : path to output scan-results json.
201
- -V --verbose : verbose run [optional].
222
+ -j : path to Nikto results JSON file.
223
+ -o --output_prefix : path to output scan-results json.
224
+ -V --verbose : verbose run [optional].
202
225
203
226
example: heimdall_tools nikto_mapper -j nikto_results.json -o nikto_results.json
204
227
228
+ ## prowler_mapper
229
+
230
+ prowler_mapper translates Prowler-derived AWS Security Finding Format results from concatenated JSON blobs to HDF-formatted JSON so as to be viewable on Heimdall
231
+
232
+ Note: Currently this mapper only supports Prowler's ASFF output format.
233
+
234
+ USAGE: heimdall_tools prowler_mapper -i <prowler-asff-json> -o <hdf-scan-results-json>
235
+
236
+ FLAGS:
237
+ -i --input -j --json <prowler-asff-json> : path to Prowler ASFF findings file.
238
+ -o --output <hdf-scan-results-json> : path to output scan-results json.
239
+
240
+ example: heimdall_tools prowler_mapper -i prowler_results.js -o prowler_hdf.json
241
+
205
242
## sarif_mapper
206
243
207
244
sarif_mapper translates a SARIF JSON file into HDF format JSON to be viewable in Heimdall
208
245
209
246
USAGE: heimdall_tools sarif_mapper [OPTIONS] -j -o
210
247
211
248
FLAGS:
212
- -j : path to SARIF results JSON file.
213
- -o --output_prefix : path to output scan-results json.
214
- -V --verbose : verbose run [optional].
249
+ -j : path to SARIF results JSON file.
250
+ -o --output_prefix : path to output scan-results json.
251
+ -V --verbose : verbose run [optional].
215
252
216
253
example: heimdall_tools sarif_mapper -j sarif_results.json -o sarif_results_hdf.json
217
254
@@ -224,8 +261,8 @@ Note: Currently this mapper only supports AWS.
224
261
USAGE: heimdall_tools scoutsuite_mapper -i -o
225
262
226
263
FLAGS:
227
- -i --input -j --javascript : path to Scout Suite results Javascript file.
228
- -o --output : path to output scan-results json.
264
+ -i --input -j --javascript : path to Scout Suite results Javascript file.
265
+ -o --output : path to output scan-results json.
229
266
230
267
example: heimdall_tools scoutsuite_mapper -i scoutsuite_results.js -o scoutsuite_hdf.json
231
268
@@ -238,9 +275,9 @@ Note: A separate HDF JSON is generated for each project reported in the Snyk Rep
238
275
USAGE: heimdall_tools snyk_mapper [OPTIONS] -x -o
239
276
240
277
FLAGS:
241
- -j : path to Snyk results JSON file.
242
- -o --output_prefix : path to output scan-results json.
243
- -V --verbose : verbose run [optional].
278
+ -j : path to Snyk results JSON file.
279
+ -o --output_prefix : path to output scan-results json.
280
+ -V --verbose : verbose run [optional].
244
281
245
282
example: heimdall_tools snyk_mapper -j snyk_results.json -o output-file-prefix
246
283
@@ -251,11 +288,11 @@ sonarqube_mapper pulls SonarQube results, for the specified project, from the AP
251
288
USAGE: heimdall_tools sonarqube_mapper [OPTIONS] -n -u -o
252
289
253
290
FLAGS:
254
- -n --name : Project Key of the project in SonarQube
255
- -u --api_url : url of the SonarQube Server API. Typically ends with /api.
256
- --auth : username:password or token [optional].
257
- -o --output : path to output scan-results json.
258
- -V --verbose : verbose run [optional].
291
+ -n --name : Project Key of the project in SonarQube
292
+ -u --api_url : url of the SonarQube Server API. Typically ends with /api.
293
+ --auth : username:password or token [optional].
294
+ -o --output : path to output scan-results json.
295
+ -V --verbose : verbose run [optional].
259
296
260
297
example:
261
298
@@ -272,8 +309,8 @@ xccdf_results_mapper translates an XCCDF_Results XML scan into HDF format json t
272
309
USAGE: heimdall_tools xccdf_results_mapper [OPTIONS] -x -o
273
310
274
311
FLAGS:
275
- -x : path to XCCDF-Results XML file.
276
- -o --output : path to output scan-results json.
312
+ -x : path to XCCDF-Results XML file.
313
+ -o --output : path to output scan-results json.
277
314
278
315
example: heimdall_tools xccdf_results_mapper -x xccdf_results.xml -o scan_results.json
279
316
@@ -284,10 +321,10 @@ zap_mapper translates OWASP ZAP results Json to HDF format Json be viewed on Hei
284
321
USAGE: heimdall_tools zap_mapper [OPTIONS] -j -n -o
285
322
286
323
FLAGS:
287
- -j --json : path to OWASP ZAP results JSON file.
288
- -n --name : URL of the site being evaluated.
289
- -o --output : path to output scan-results json.
290
- -V --verbose : verbose run [optional].
324
+ -j --json : path to OWASP ZAP results JSON file.
325
+ -n --name : URL of the site being evaluated.
326
+ -o --output : path to output scan-results json.
327
+ -V --verbose : verbose run [optional].
291
328
292
329
example: heimdall_tools zap_mapper -j zap_results.json -n site_name -o scan_results.json
293
330
@@ -355,6 +392,7 @@ To release a new version, update the version number in `version.rb` according to
355
392
356
393
### Authors
357
394
395
+ - Author:: Amndeep Singh Mann [ Amndeep7] ( https://github.com/Amndeep7 )
358
396
- Author:: Rony Xavier [ rx294] ( https://github.com/rx294 )
359
397
- Author:: Dan Mirsky [ mirskiy] ( https://github.com/mirskiy )
360
398
0 commit comments