Skip to content

Commit 164eb24

Browse files
authored
docs(connectors): add OpenVAS / Greenbone connector reference (#15273)
Setup and usage for the OpenVAS / Greenbone connector: GMP (XML over TLS) transport, GMP user credentials, gvmd host/port, TLS options (CA cert or skip verify), and import behavior (whole-instance sync; task -> product; one finding per result; threat->severity with Log/Debug -> Info; host/port -> endpoint). Placed alphabetically before Probely. Story: sc-13731
1 parent 081e388 commit 164eb24

1 file changed

Lines changed: 18 additions & 0 deletions

File tree

docs/content/import_data/pro/connectors/connectors_tool_reference.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -658,6 +658,24 @@ Unlike the device\-based Microsoft Defender connector, no API permissions or adm
658658

659659
Each enabled Azure subscription becomes a Record. Findings are read through Azure Resource Graph, so they surface promptly once Defender for Cloud has scanned your resources — but the scans themselves run on Microsoft's schedule: container\-registry images are usually scanned within an hour of being pushed, while a VM's first agentless vulnerability scan can take several hours. A newly enabled subscription will legitimately Sync zero findings until its resources have been scanned.
660660

661+
## **OpenVAS / Greenbone**
662+
663+
The OpenVAS / Greenbone connector imports **network vulnerability findings** from a Greenbone (Greenbone Community Edition or Greenbone Enterprise) instance. It talks to `gvmd` over **GMP (Greenbone Management Protocol)** — an XML protocol over a TLS socket, not HTTP — and syncs the whole instance: it enumerates scan **tasks** and creates a DefectDojo product for each, importing the results of each task's latest report.
664+
665+
#### Prerequisites
666+
667+
A Greenbone **GMP user** (username + password) and network access to gvmd's GMP TLS port (default **9390**). The Greenbone Community Edition compose stack fronts gvmd via a unix socket, so to reach it from a networked connector you either run the connector where it can reach the socket or expose the GMP TLS port (for example a `socat` TLS bridge to `gvmd.sock`).
668+
669+
#### Connector Mappings
670+
671+
1. Enter the gvmd host in the **Location** field (host or `host:port`).
672+
2. Enter the GMP **Username** and **Password**.
673+
3. Optionally set the **GMP Port** (defaults to 9390).
674+
4. For gvmd's default self\-signed certificate, either provide a **CA Certificate (PEM)** to verify against, or set **Skip TLS Verification** to `true`.
675+
5. Optionally, set a **Minimum Severity** to limit which findings are imported.
676+
677+
Each Greenbone task becomes a Record. Findings come from the task's latest finished report — one per `<result>`. Severity is taken from the result's threat level (Greenbone's `Log`/`Debug` informational levels map to Info), with the numeric CVSS score recorded; CVE references become vulnerability ids, the NVT solution becomes the mitigation, and each result's host/port becomes an endpoint.
678+
661679
## Probely
662680

663681
This connector uses the Probely REST API to fetch data.

0 commit comments

Comments
 (0)