25.01.2026

How to Install and Configure OpenVAS (GVM) on Ubuntu for Vulnerability Scanning

Vulnerability scanners are tools designed to identify security weaknesses in operating systems, services, and network configurations. They help administrators detect outdated software, misconfigurations, and known vulnerabilities before they can be exploited.

OpenVAS (Greenbone Vulnerability Management) is a popular open-source vulnerability scanning platform that provides comprehensive security assessments for Linux-based systems, including Ubuntu servers.

This guide explains how to install and configure OpenVAS (Greenbone Vulnerability Management) on Ubuntu using Docker. You will learn how to deploy the scanner, access the web interface, and perform vulnerability assessments to improve system security.

Choosing a Vulnerability Scanner

Several vulnerability scanning solutions are available, but OpenVAS stands out due to its open-source model, extensive vulnerability database, and active community support.

Installing OpenVAS on Ubuntu Using Docker

Before using the main utility update and upgrade your system :

sudo apt update -y && sudo apt dist-upgrade -y

Screenshot №1 — Update OS

You need to log in to Docker Hub. If so, follow these steps. Register on the website, fill all the needed fields and confirm mail that you will receive after registration:

Screenshot №2 — Site

Install virtualization software for starting container:

apt install docker.io

Screenshot №3 — Installation

Press button for confirm installation process. Then you have to log in to Docker Pub via the console using the command:

docker login

Screenshot №4 — Log in

Enter your login details and wait for Docker to confirm a successful login that provide access to container in repositories. Now we need to pull container from repositories:

docker pull mikesplain/openvas

Screenshot №5 — Pull container

Amount data of the file is quiet big, please be patient in process of downloading! After this run container with parameters:

docker run -d -p 443:443 --name openvas mikesplain/openvas

Screenshot №6 — Run container

Retrieving the container from the docker registry and launching it will commence. Kindly note that Openvas startup may require a considerable amount of time as NVT's are scanned and databases reconstructed, hence please exercise patience. Upon sighting the message in the logs, you can proceed to access the web user interface by visiting https://localhost.

For login into the system use this credential:

Username: admin
Password: admin

If you are working on a remote server, it is recommended to access the OpenVAS web interface from your local machine by forwarding port 443 or using the server’s public IP address.

apt install gnome-core

Screenshot №7 — Gnome install

Reboot the server and login through the web console. You have to look at login panel and enter you credentials:

Screenshot №8 — Login

After this go to the application panel and choose needed browser to search URL:

Screenshot №9 — Firefox

Enter in the Search field URL:

https://localhost

Screenshot №10 — Web page

Enter credentials which we consider above of this instruction. Now you have access to modern vulnerability scanner that can help build more secure system!

Screenshot №11 — Dashboard

If you want to change password, at first you need stop container and then use command for change credentials:

docker stop openvas
docker rm openvas
docker run -d -p 443:443 -e OV_PASSWORD=Strong_Password_123! --name openvas mikesplain/openvas

And write complicated password with letters, numbers and special symbols.

Conclusion

OpenVAS (GVM) is a powerful open-source vulnerability scanner that helps identify security weaknesses in Ubuntu systems. Deploying OpenVAS using Docker simplifies installation and isolates the scanning environment.

By following this guide, you can quickly set up a vulnerability scanning platform, access the web interface, and improve your server’s security posture. Always change default credentials and regularly update vulnerability databases for accurate results.

FAQ