-
Notifications
You must be signed in to change notification settings - Fork 267
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
Openvas 11 support #202
Comments
Related #181 |
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 |
Hello there, Any update regarding Openvas 11 integration? thx in advance. |
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: