Re: Architecture of NESSUS

[Rodrigo Blanco <rodrigo.blanco.r () gmail com>]

Basically, nessus has two parts: server (daemon) which is started as
nessusd on a Unix server, and a client, which is available for both
Unix and Win32.

You add users to nessus server and connect with the client to the
server using these identities.

Then you select the targets and selected scan plugins, and start scanning.



On 5/24/05, Rajiv-Ranjan <rajiv () ncb ernet in> wrote:
> Hello folks,
>
>        we need to know the details about NESSUS vulnerability scanner.
> Like.
> 1. The ARCHITECTURE of nessus(nessus client and daemon).
> 2. How nessus is using different O/S tools like, NMAP, HYDRA..
> 3. Which module is responsible for what? means which module of nessus is
>        interacting with NMAP, which is for HYDRA and HOW?
> 4. Which module is responsible for customization to scan.
> 5. How to write plug in for nessus and also enable and disable the
>        plug-in(not by using UI)
> 6. How to customize the report generation of nessus.
> 7. How can one integrate nessus with IDS to correlate the report and
>        alert to reduce false alert .
> 8. How each and every module is interacting with each-other.
>
>          I have searched the net to know the whole
> architecture but didn't get much info. If u know or
> have some relevant documents then Please let me know.
>
>
> Thanks in-advance.
> Regds......
> Rajiv Ranjan
> NCST(now C-DAC), Bangalore
> 9886085012
> 080-28523300
> www.ncb.ernet.in/~rajiv
> www.ncb.ernet.in/nag