About

OpenVAS
Constitution
OpenVAS-Server
OpenVAS-Client
OpenVAS NVT Feed

Information/Howtos

Integrated Tools
Related Tools
Sources For Security Issues
Creation Process For NVTs
Trusted NVTs
NVT Feeds
Performing Local Security Checks
Articles/Studies
OpenVAS Compendium (en)
OpenVAS Compendium (de)

Support

Team & Tasks

Bug Tracker

Mailinglist Discussion:
Archive | Subscribe
Mailinglist Announcements:
Archive | Subscribe

Online Chat

FAQ

Professional Services

Developers Corner

Development Platform
Code quality
Change requests
Internal Architecture
Assigning OIDs for NVTS
DevCon2
DevCon2 - Minutes
Code Documenation

Mailinglist Development:
Archive | Subscribe
Mailinglist Writing NVTs:
Archive | Subscribe
Mailinglist Packaging/Distributing:
Archive | Subscribe
Mailinglist Source Code Commits:
Archive | Subscribe

Download

OpenVAS 3.0:
openvas-libraries 3.0.3
openvas-scanner 3.0.1
openvas-client 3.0.0
Optional:
openvas-manager 1.0.0-beta4
openvas-administrator 0.7.0
gsa 1.0.0-beta4

OpenVAS 2.0:
Server components:
openvas-libraries 2.0.4
openvas-libnasl 2.0.2
openvas-server 2.0.3
openvas-plugins 1.0.7
Client:
openvas-client 2.0.5

Documentation:
OpenVAS Compendium 1.0.1
PDF (en)
PDF (de)

More downloads...

NVT Lookup by OID

(replace 61039 by any other old-style ID)

About OpenVAS NVT Feed

The OpenVAS project offers a public feed of Network Vulnerability Tests (NVTs). Starting from September 10th, 2008, the feed contains all NASL plugins available in the OpenVAS source code repository and now contains more than 15,000 NVTs. It contains only signed files.

This feed is configured as default for OpenVAS Server. Read about NVT Feed Services on how to synchronize your OpenVAS Server with the OpenVAS NVT Feed.

The feed is usually updated every weekday. The files of the OpenVAS NVT Feed are signed by the "OpenVAS: Transfer Integrity" certificate. The presence of this signature does not indicate any judgement or quality control of the script itself. It is only intended to assist you in verifing the integrity of the NVT files after transfer. Thus, a valid signature only means that the script has not been modified on the way between the OpenVAS distribution point and your OpenVAS installation. See the notes at the bottom of the overview on Trusted NVTs for more information on this certificate.