HASecuritySolutions/VulnWhisperer

Openvas 11 support

Open

#202 opened on Jan 21, 2020

View on GitHub
 (4 comments) (1 reaction) (0 assignees)Python (1,320 stars) (281 forks)batch import
feature requesthelp wantedversion update

Description

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.

Contributor guide

Tech stack
python
Domain
backendsecuritydata
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic understanding of OpenvasPython programmingFamiliarity with VulnWhisperer project structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Examine the issue comments and repository to see if any maintainer has responded or if there is an existing workaround. If not, review the Openvas 11 output format and compare it to the current parser in VulnWhisperer (likely in a file related to Openvas processing). The goal would be to add a filter or toggle to exclude the outdated scan engine report. Check the project's documentation for contribution guidelines.