Re: Using a database as backend for Nessus (current state and volunteering for development)

Michael Boman <[email protected]>
Newsgroups gmane.comp.security.nessus.devel
Message-ID <[email protected]>
Let's stop _talking_ and get down to action, shall we? I have not yet
taken a look at the code itself, but this is a quick draft based on what
XML_NG can do, with what people (might) want to be able to do..:

This is psudo code!!!

TABLE hosts (
	scan_id, 	# A auto incrimental value for each scan we do
	hostname, 	# name of host
	ip,		# address of host
	scan_start,	# when did we start scanning this host?
	scan_end,	# when did we end scanning this host?
	nessus_version,	# What version of nessus was used?
	request_user,	# Who requested the scan (username), good if
			# you want to limit what a user can see
	request_host,	# Where did this user login from? For audit purpose.. IP number here.
);

TABLE reports (
	scan_id,	# Refer to hosts.scan_id
	plugin_start,	# When did we start this scan?
	plugin_end,	# When did this plugin end?
	plugin_id,	# Plugin number
	plugin_version, # (is there such a thing? if not, something
			# for NASL2?)
	port_number,	# What port is it we scanned?
	port_protocol,	# and what protocol is it using?
	serverity,	# Number refering to serverity.serverity_id
	completed,	# did the plugin actually finish or did nessusd
			# kill it?
			
#ifndef	If people want to store plugin output in several languages
	lang		# I don't know how relivant this is, but some
			# ppl might want to store what lang the message
			# is written in. Do we want to store several languages at once?
	data		# plugin output
#endif

)

#ifdef If people want to store plugin output in several languages
TABLE data (
	scan_id		# refer to hosts.scan_id
	lang		# language
	data		# plugin output
	)
#endif

TABLE services (
	port_number,	# port number
	port_protocol,	# protocol
	service_name	# human readable name
	)

TABLE serverity (
	serverity_id	# Number
	serverity_name	# Human readable serverity
	)

TABLE references (
	plugin_id,	# Plugin ID
	refrence_type,	# reference_types.reference_type value
	reference_data	# CVE-1999-0191 (example)
	)

TABLE reference_types (
	reference_type	# Autoinc value
	reference_name	# CVE, CAN, BID and so on...
	reference_url	# http://cve.mitre.org/cgi-bin/cvename.cgi?name=
			# (example). The base URL to get to the page of
			# interest
)

-- 
Michael Boman
Security Architect, SecureCiRT (A SBU of Z-Vance Pte Ltd)
http://www.securecirt.com
signature.asc (application/pgp-signature, 232 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+JQzFds5fQJiraJwRArtCAKCgVs5TygCy+GCiI32WjKUObWlzyQCfW9yH
Rc0IOffUCUX+b3mD5FIG0dc=
=XX1q
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.