Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Tenable Plugin Info to References #11127

Closed
Marterich opened this issue Oct 24, 2024 · 3 comments
Closed

Add Tenable Plugin Info to References #11127

Marterich opened this issue Oct 24, 2024 · 3 comments

Comments

@Marterich
Copy link

Is your feature request related to a problem? Please describe
Tenable Vulnerability Scanner use so called Plugins to check a given host for the existence of Vulnerabilities.
Plugins can be thought of as a Script telling the scanner "Connect to port X, check for the Version string Y and if found do Z" These Plugins do have a unique Id and the plugin content can change over time. In every scan export, the Plugin Id, Published Date and Modified Date are contained.

After importing the Scan information, the Information which Plugin Id and the date values of the Plugin are discarded so there is no possibility to check from Defect Dojo which Plugin Version was used to find the Vulnerability. This information could be valuable when investigating to find out exactly why and how the scanner detected a given vulnerability

Describe the solution you'd like
The Scan Plugin Information should be added to the References section of a given Vulnerability when a Tenable scan is imported. Format wise this could be appended as a new line like:
<Tenable Plugin Information: ID: 12345, Published: 01/01/24, Modified: 01/01/24>

@Marterich Marterich changed the title Add Tenable Plugin Version info to References Add Tenable Plugin Info to References Oct 24, 2024
@manuel-sommer
Copy link
Contributor

see PR @Marterich
I added it to references because of the deduplication of the description field

@Marterich
Copy link
Author

Thank you very much :)
Had an implementation pretty much at the ready, but hesitated because i did not manage to get the unittests to run in my environment

@manuel-sommer
Copy link
Contributor

manuel-sommer commented Oct 29, 2024

Thank you very much :) Had an implementation pretty much at the ready, but hesitated because i did not manage to get the unittests to run in my environment

No worries. Regarding the unittests, take a look here:
#11143

@Maffooch Maffooch closed this as completed Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants