performing-authenticated-scan-with-openvas

Create a credential with gvm-cli (SSH key or password for Linux, SMB for Windows), attach it to a target, then create and start a scan task using a config like Full and fast. Validate success via the authentication NVT results in the report.

On Kali or Debian, run apt install gvm followed by gvm-setup and gvm-start. For production, use the official Greenbone Community Edition docker-compose deployment, which takes 15-30 minutes for the initial feed sync.

Sparse local findings usually mean authentication silently failed. Check the SSH and SMB authentication NVTs (OIDs 1.3.6.1.4.1.25623.1.0.103591 and 1.3.6.1.4.1.25623.1.0.90023) in the report, and verify credentials have sufficient privileges.

Yes, OpenVAS supports SMB credentials for Windows authenticated scanning. Create an up-type credential with a DOMAIN\account login, attach it as smb_credential to the target, and use an admin-equivalent service account to see patch state.

Use gvm-cli with get_reports and a format UUID for XML or CSV output, or use the python-gvm library with a Unix socket connection to authenticate and retrieve reports through the GMP protocol.

You need GVM 22.x or later with gvmd, openvas-scanner, gsad, and ospd-openvas, a configured PostgreSQL database and Redis, a synchronized NVT feed, valid SSH or SMB credentials, and network access to target scan ports.