Greenbone and GVM testing

Add your authorised Greenbone console as an HTTPS target, including its port. In Target testing configuration, save a dedicated low-privilege GVM probe account. Request a Greenbone or GVM assessment explicitly so the planner selects the GVM capabilities.

The optional gsad URL must match the assessed HTTPS origin, including its port. Credentials are encrypted at rest and are never returned by the configuration API.

The permission check attempts to grant modify_scanner on the shared default scanner to the User role. It can affect other users. Run only under the required intrusive-test approval and rules of engagement.

The optional password-change check submits an incorrect current password and requests the existing password as the new value. It may end other sessions. Use a dedicated account.

A successful command produces a finding for the observed operation. An explicit control-specific rejection can pass. Unsupported commands, ambiguous failures and server errors are inconclusive and do not count as completed checks.

The probe attempts to remove its permission. If gsad omits the permission ID or removal fails, the report includes the exact marker and a cleanup error. The lab owner must remove that marked permission and verify removal before closing the engagement. A successful grant does not independently demonstrate scanner redirection or credential theft.

This feature requires the gmpprobe configuration migration, a configured credential encryption key, native GVM routing and access to the authorised target. Private labs also require an operator-configured network allowlist. Loopback and metadata addresses remain blocked.

Missing credentials, out-of-scope targets and unavailable runners are reported as untested. Repository integration does not establish that a hosted deployment is ready.