OpenVAS Layout for OIDs
Note: The support of the OID scheme arrives with OpenVAS 2.0. To stay compatible with OpenVAS 1.0, it is recommended to apply the old ID scheme as described below.
Note also: The refinements of the OID scheme are still in progress. Please contact the OpenVAS development team for questions and especially in case you like to apply OIDs.
1.3.6.1.4.1.25623 (iso.org.dod.internet.private.enterprise.OpenVAS): Base OID | +--.1 (.NVT): OpenVAS Network Vulnerability Tests | | | +--.0 (.Legacy): Legacy method to incorporate old IDs into new OID layout | | | | | +--.NNNN: old ID as defined via script_id() | | | +--.1 (.Contrib): NVTs contributed by third parties | | | | | +--.1 (Contributor 1) | | | | | | | +--.NNNN (enumeration under responsibility of contributor) | | | | | +--... (next contributors) | | | +--.2 (.lib): Supporting scripts, usually suffixed .inc and proving some API | | | | | +--... | | | +--.3 (.DSA-LVT): Family of Local Vulnerbaility Checks for Debian Security Alerts | | | | | +--1157.1: Implementaiton for DSA 1157, Version 1 of the script (example) | | | +--... (next families) | +--... (other things of OpenVAS project that need a unique ID)
Layout for old Nessus-style ID
The old IDs are integer values. They are assigned via the NASL command script_id(). It is possible to concurrently define a OID (via script_oid()). In case no OID is defined, a legacy OID is assembled based on the old ID.
- 1NNNN: Scripts inherited from Nessus
- 2NNNN: Scripts inherited from Nessus
- 3NNNN: Not assigned yet.
- 4NNNN: Not assigned yet.
- 5NNNN: Contributions by Security Space
- 6NNNN: Contributions by Security Space
- 7NNNN: Not assgined yet.
- 8NNNN: Kost
- 9NNNN: Contributions by DN Systems
- 10NNNN: Not assgined yet.
- ...
- 20NNNN: Contributions by Ferdy Riphagen
- ...
- 80NNNN: GB
- 90NNNN: Contributions by SecPod
- ...
- 102NNNN: AlienVault
