Home page logo
/

openvas logo OpenVAS mailing list archives

Re: NVT Description
From: Sebastien Aucouturier <s.aucouturier () itrust fr>
Date: Thu, 24 Jan 2013 13:14:39 +0100
List-id: OpenVAS plugins <openvas-plugins.wald.intevation.org>

Thanks a lot Hani,
My Idea, was also to fix the structure to have mandatory and optional fields
each NVT should have : (but i may have missed entries)

NAME (MANDATORY)
FAMILY  (MANDATORY)
CVSS  (MANDATORY)
OVERVIEW  (MANDATORY)
DESCRIPTION (MANDATORY)
SOLUTION   (OPTIONAL)
REFERENCES  (OPTIONAL)
VULNERABLE SYSTEMS (OPTIONAL)
OUTPUT (DATA GET FROM HOST by PLUGIN)

and we need to replace the following keyword (build 09/11/11) by a the correct one :

CVSS Score( Report)?
Overview /  Synopsis
Description / Vulnerability Insight / Impact / Bug Report
Solution / Fix / Workaround
Reference[s?] / See [aA]lso
Affected [Ss]oftware(\/OS)? / The issue affects the following / The following package is affected / The following versions are affected / The following versions are vulnerable / Vulnerable systems



Le 24/01/2013 10:00, Hani Benhabiles a écrit :
Hi list,

I have read some of previous emails about separating some of the
information that is included in NVT scripts description in order to
make output parsing and reporting easier and more efficient. I have
discussed some ideas with Jan and have come up with the following as a
start:

* References/URLs/See also: These contain web links that have more
contextual information about the issue. A suitable name to
differentiate these references from other references types could be
"URL".

As an example, in gb_edirectory_57038.nasl:
References:
http://www.securityfocus.com/bid/57038
http://www.novell.com/products/edirectory/
http://www.novell.com/

Would become:
script_xref(name : "URL" , value "http://www.securityfocus.com/bid/57038";); script_xref(name : "URL" , value "http://www.novell.com/products/edirectory/";);
script_xref(name : "URL" , value "http://www.novell.com/";);

* Solution/Fix: These contain information about the issue. After some
discussion, we have come to think of using script_tag() with a
suitable tag name.

As an example:

Solution:
An update is available. Please see the references for more
information.

would become something like:
script_tag(name:"solution", value:"An update is available. Please see
the references for more information.");

Any issues with this ? Ideas on how this could be further improved ?
Feedback is welcome.

Cheers,
Hani.
_______________________________________________
Openvas-plugins mailing list
Openvas-plugins () wald intevation org

https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-plugins

--
"Le saviez-vous ? la technologie d'ITrust va sécuriser le cloud français"

    | Sébastien AUCOUTURIER | Responsable R&D
    | ITrust | 55 L'Occitane 31670 LABEGE
    | Email: s.aucouturier () itrust fr
    | Fixe Sdt. 05.67.34.67.80
    | IT Security Services & SaaS Editor
_______________________________________________
Openvas-plugins mailing list
Openvas-plugins () wald intevation org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-plugins

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]