OpenVAS
Connect OpenVAS to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your OpenVAS connection as vulnerability scanning evidence. Automated collection is not available for this provider yet.
| Category | Vulnerability Scanning |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In OpenVAS:
- OpenVAS / Greenbone has no API tokens. Remote access is through the Greenbone Management Protocol (GMP) to gvmd, which authenticates with a GMP user name and password.
- Use a dedicated GMP user for Safeguard on the Greenbone server and put its password in the token field.
- Make gvmd reachable over a TLS or SSH connection; the default Unix domain socket (/run/gvmd/gvmd.sock) only works on the same host.
Where to find the other values:
- Base URL (optional): The host and port of your gvmd GMP endpoint (TLS or SSH connection type).
- Account / Org / Workspace (optional): The GMP user name of the account you created.
OpenVAS issues this credential through its API or its support team, not through its admin screens.
Greenbone's gvm-tools docs describe GMP authentication by username and password and three connection types (TLS, SSH, Unix domain socket); TLS and SSH require server-side setup unless a Greenbone OS appliance is used. The user/role creation clicks in the Greenbone Security Assistant web UI were not fetched, so no UI path is given.
Source: greenbone.github.io, greenbone.github.io, checked 2026-10-07.
-
On Compliance › Connectors, open OpenVAS, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
OpenVAS publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Attestation | CC7.1 | 1 |
| ISO/IEC 27001 | Attestation | A.8.8 | 1 |
| HIPAA Security Rule | Attestation | 164.308(a)(1) | 1 |
| PCI DSS | Attestation | 6.3.3, 11.3.1 | 1 |
| NIST CSF 2.0 | Attestation | ID.RA-01 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- Vulnerability Scanning connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks