Greenbone Scan & Scheduling of Timings for Large IP's


Would like to know how this Greenbone Scans internally?
Suppose when I try to set Target of 10 IP Address for Scanning, how Greenbone internally functions? What are all the files does it consider? Could you please help me process.

Currently I have a list of 100 IP Address and I have divided into two sets like (i.e. 50 IP Address and another set of 50 IP Address). So my question is over here can I schedule the timings for these IP Address in different timings? Please suggest.

Does Greenbone has the capability of scan 50 IP Address at scheduled timings?


when choosing the category for a topic please try to have a look at the category description for each category first:

The current used category is/was (Description: About the Vulnerability Tests category) which is about vulnerability tests (the so called “NASL scripts”).

Your question is completely unrelated to the NASL script itself but about scanning with GVM / GVM internals so i have moved this topic into the better fitting (Description: About the Source Edition (GSE) category).


Can we have call on this issue with your team members?
I have few questions in regards with Greenbone requirement.

We have an extensive documentation for our products.

I am really sure it contains answers to your questions.


Hi Team,

Please find the below mentioned details how the Greenbone Works internally.

OpenVAS Manager serves as processing unit by processing and storing scanning results and by managing different users. It is possible to have many users connected to the same OpenVAS each of these users might have different types of permissions. It is in charge of storing information about all users. And able to store information from scanning results and information about users.

The OpenVAS Manager connects to Greenbone Management Protocol clients and Greenbone Security Assistant. GMP clients are using Greenbone management protocol. These clients provide tools that allow batch scripting and usage of OpenVAS via command line. Greenbone Security Assistant (GSA) is the web interface for the OpenVAS Manager. Greenbone Security Assistant consists of:

GSA – the web application written in React

GSAD – the HTTPS server talking to the OpenVAS Manager via Greenbone management protocol.

OpenVAS keeps up to date and running the latest security scripts to find the latest vulnerabilities as well as sync to the most updated NVT, SCAP and cert data. One of the best way to do this is to create a script that sync’s the necessary data for you automatically each day.

Default OpenVAS Scanner, full and fast type & and port nos will scan the IP Address based on the scheduled timings being set.

Various Scan reports can be generated (XML, CSV, etc).

Please do check and confirm if Greenbone internally functions and works accordingly and let me know the same.


Please note that I have not deployed any Greenbone OS, I have used packages from Centos 7.4 Version for the installation of Greenbone.

You are mixing GVM 9 and GVM 10. See

This is not valid for GVM 9.

And this is gvmd in GVM 10.


Okay I have removed those lines, now could you please let me know how this scan process works internally? What is the mechanism been used in OpenVAS? What protocol been used and how does it communicates our internal IP Address or Public IP Address?

Maybe you should rephrase your question to be more specific.

An overview about the internal communication structures of GVM 10 can be found at

With GVM 10 the openvas-scanner runs (network) vulnerability tests (called vts or nvts), which collect information about the target hosts. This information is passed via otp to gvmd. gvmd stores this data in a database. gsad collects the data via gmp from gvmd after GSA has requested it via http.


Thanks for the information.

Would like to know what is this gmp from gvmd stands for?

Sorry but did you even take a look at one of the links I posted here??? Both are explained on EVERY link!

1 Like

Okay, Thanks for the information.

A post was split to a new topic: Frequency of NVT, SCAP and CERT data updates