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
The old openvas versions generate this: "Report outdated Scan Engine / Environment (local)" for each scanned IP.
While waiting for Openvas latest version copatibility it would be nice to have a workaround in order to exclude it before sending to Logstash/ELK.
Thanks,
Antonio.
The text was updated successfully, but these errors were encountered:
This is not something in the current roadmap as we are working on a heavy refactoring to make the project modular and easy to integrate for other developers, but will be something very easily implementable when we get this priority goals done. Sorry for not being that much help on the short term with the issue.
Firstly, I don't get the point of prioritizing refactorization over restoring the connectivity to one of the data sources (OpenVAS 11).
@sarritzu: As a workaround, to disable logging of the outdated scan engine vulnerability, you can drop the respective documents by filtering for oid in a Logstash filter.
Can you please add Openvas 11 compatibility?
The old openvas versions generate this: "Report outdated Scan Engine / Environment (local)" for each scanned IP.
While waiting for Openvas latest version copatibility it would be nice to have a workaround in order to exclude it before sending to Logstash/ELK.
Thanks,
Antonio.
The text was updated successfully, but these errors were encountered: