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

Openvas 11 support #202

Open
sarritzu opened this issue Jan 21, 2020 · 4 comments
Open

Openvas 11 support #202

sarritzu opened this issue Jan 21, 2020 · 4 comments

Comments

@sarritzu
Copy link

sarritzu commented Jan 21, 2020

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.

@qmontal
Copy link
Contributor

qmontal commented Feb 4, 2020

Related #181

@qmontal
Copy link
Contributor

qmontal commented Feb 4, 2020

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.

@chmey
Copy link

chmey commented Sep 4, 2020

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.

@damelo
Copy link

damelo commented May 25, 2021

Hello there,

Any update regarding Openvas 11 integration?

thx in advance.

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

4 participants