Replies: 1 comment
-
There are a few things you probably want to do to prep this data for import:
For the last one, there are some obvious connections, like You'll need to review fields like Nessus results will likely be specific to a report, not something you want added to your findings library. If you're making a script to convert the Nessus output to findings suitable for adding a report, I would start by writing a parser to take all the information you want from Nessus, clean it up, assemble it into a structure matching Ghostwriter's findings, and then use the API to add each finding to your report. |
Beta Was this translation helpful? Give feedback.
-
I am working on trying to be able to import bulk findings from Nessus in either the .nessus format or a generated .csv report. Is there something that I need to do in order to get the required field types to play nice that someone has already figured out? Below are all of the header options by default that can be included with a generated csv out of Nessus.
Nessus .csv Headers
Plugin ID
2CVE
CVSS v2.0 Base Score
Risk
Host
Protocol
Port
Name
Synopsis
Description
Solution
See Also
Plugin Output
STIG Severity
CVSS v3.0 Base Score
CVSS v2.0 Temporal Score
CVSS v3.0 Temporal Score
Risk Factor
References
Plugin Information
Exploitable With
Beta Was this translation helpful? Give feedback.
All reactions