Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
OpenVAS is the open-source vulnerability scanner at the heart of Greenbone Community Edition. It tests hosts and services against a community feed of vulnerability checks.

What Is OpenVAS?
OpenVAS is an open-source vulnerability scanner that probes hosts, services, and applications for known weaknesses, then reports each finding with a severity rating. It is the scanning engine inside the Greenbone Community Edition, and for many smaller security teams it is the first vulnerability scanning tool they ever run.
The project dates from 2005, when Nessus moved from an open-source licence to a closed commercial model. Developers forked the last freely licensed codebase and continued it as the Open Vulnerability Assessment System. Greenbone took over the bulk of development in 2008 and still maintains the free edition alongside a commercial appliance range, so the naming has shifted over the years: the scanner is OpenVAS, the management layer is GVM, and the whole free bundle is Greenbone Community Edition.
Treating OpenVAS as a single program causes most of the confusion people meet during installation. It is a set of daemons that talk to each other.
| Component | Role |
|---|---|
| openvas-scanner | Executes the vulnerability checks against targets |
| ospd-openvas | Wraps the scanner in the Open Scanner Protocol so the manager can drive it |
| gvmd | Stores targets, tasks, results, and users in PostgreSQL |
| Greenbone Security Assistant | The web interface, usually on port 9392 |
| Community Feed | The vulnerability tests, plus SCAP and CERT data, synchronised daily |
The checks themselves are Network Vulnerability Tests written in NASL, a small scripting language inherited from the Nessus era. The Community Feed carries well over 100,000 of them, and each one maps to CVE identifiers where they exist.
A task combines a target list with a scan configuration. The scanner first decides which hosts are alive, enumerates open ports, fingerprints the services behind them, and only then selects the vulnerability tests that are relevant to what it found. Stock configurations range from a fast discovery sweep to “Full and very deep ultimate”, which includes checks that can destabilise fragile services.
Credentials change the quality of the output more than any other setting. An unauthenticated scan infers versions from banners, which fails badly on Debian and Red Hat systems that backport security fixes without changing the version string. Give the scanner an SSH key or an SMB account with the right rights and it reads installed package versions and registry keys directly, which removes most of the guesswork.
Every result carries a severity derived from CVSS and, separately, a Quality of Detection percentage. QoD is the part people skip. A finding at 30 per cent came from a banner and may well be wrong; a finding at 97 or 99 per cent came from a registry check or a successful exploit attempt and deserves immediate attention. Filtering a report to QoD 70 and above is the quickest way to turn thousands of raw rows into a list an engineer can work through.
Reports export to XML, CSV, and PDF, and delta reports compare two scans of the same target so you can evidence that last month’s findings are gone.
OpenVAS is strong where the problem is breadth: sweeping an internal estate, checking a new subnet before it goes live, or giving a small team a repeatable monthly baseline without a per-asset licence. It is weaker on modern web applications, it has no native risk-prioritisation model comparable to Qualys VMDR, and its feed sometimes lags commercial equivalents by days after a high-profile disclosure.
It also is not a penetration test. A scanner reports that a flaw may exist; a tester proves what an attacker could do with it, chains findings together, and exercises logic that no signature covers. The two are complementary, not interchangeable.
Change the default administrator password before the appliance touches a network. Schedule aggressive scans outside business hours, and keep operational technology and medical devices on a cautious configuration or out of scope entirely, because printers, PLCs, and older appliances can fall over under port sweeps. Record authorisation in writing, even for your own estate, and store reports as the sensitive documents they are.
One compliance point catches people out: PCI DSS requires external quarterly scans from an Approved Scanning Vendor, and a self-hosted OpenVAS cannot produce that evidence however clean its output. Our Continuous Vulnerability Scanning Services cover that gap and turn raw scanner output into a prioritised remediation plan.
They share an ancestor. OpenVAS was forked from the last open-source Nessus release in 2005 and has been developed separately ever since, so the two now have different engines, feeds, and interfaces. Nessus is commercial software from Tenable with a free tier limited to sixteen IP addresses. OpenVAS has no asset limit but a smaller community feed.
Not strictly, but the results improve dramatically with them. Unauthenticated scans infer software versions from network banners, which produces false positives on Linux distributions that backport patches. A credentialed scan reads installed packages, patch levels, and registry settings directly, so it finds missing updates that an external view never sees and reports far fewer phantom issues.
Quality of Detection is a percentage that states how reliable a particular check is. Low values, around 30 per cent, mean the finding came from a version banner and could be wrong. Values of 97 to 99 per cent mean the scanner confirmed the issue through a registry key, package query, or a safe exploit attempt. Filter by QoD before you triage.
No. OpenVAS matches what it sees against a catalogue of known issues. It will not chain two medium findings into a domain compromise, abuse broken business logic, or judge whether a finding matters in your specific environment. Use scanning for continuous coverage between engagements, and a penetration test to understand what an attacker could genuinely achieve.
You May Be Interested In These
Cybersecurity Terms
17 November 2026
What Is the Difference Between Fail-Secure and Fail-Safe?
Read MoreWe use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.