Re: [Openvas-discuss] Managing many scanners instead of a master-slave architecture?

2016-11-09 Thread Jan-Oliver Wagner
Am Donnerstag, 18. August 2016, 18:35:04 schrieb LeBlanc Benjamin-Hugo: > We are seriously considering deploying OpenVAS in our organisation, and we > will most certainly opt for a distributed architecture that matches our > network segmentation. We understand so far that a Master-Slave > configura

Re: [Openvas-discuss] Managing many scanners instead of a master-slave

2016-08-26 Thread Fábio Fernandes
That chatty communication between manager and scanner is probably the status and intermediate results messages but i would have to analyse these interaction to be sure. Em 19/08/2016 16:00, "Tyler Sable" escreveu: > Ben, > > I have built the master-scanner architecture, and it works. But, I have

Re: [Openvas-discuss] Managing many scanners instead of a master-slave

2016-08-26 Thread mattm
> Now we wonder, though, how the NVT/SCAP/CERT Feed updates are managed on each > scanner; in other words, when we click the "Synchronize with Feed now" > button, in the web interface, does the Manager remotely call a syncing action > with feed on *each scanner* defined in the Configuration/Scan

Re: [Openvas-discuss] Managing many scanners instead of a master-slave

2016-08-25 Thread LeBlanc Benjamin-Hugo (EXT)
Thank you Tyler and Fabio for your answers. We experimented with the Manager -> n Scanners architecture, and it actually works well (we launch physically distant scanners directly from one manager), as long as the right Scanner IPs are provided and proper certificates are loaded in the Scanner

Re: [Openvas-discuss] Managing many scanners instead of a master-slave

2016-08-19 Thread Tyler Sable
Ben, I have built the master-scanner architecture, and it works. But, I have been disappointed in its performance. The scans run on the external scanner seem to take a lot longer than scans run on the same machine. I think the communication between the manager and scanner is probably too chatty

Re: [Openvas-discuss] Managing many scanners instead of a master-slave architecture?

2016-08-18 Thread Fábio Fernandes
t; > > -Message d'origine- > De : Fábio Fernandes [mailto:fabiogfernan...@gmail.com] > Envoyé : 18 août 2016 16:37 > À : LeBlanc Benjamin-Hugo (EXT) > Cc : openvas-discuss@wald.intevation.org > Objet : Re: [Openvas-discuss] Managing many scanners instead of a

Re: [Openvas-discuss] Managing many scanners instead of a master-slave architecture?

2016-08-18 Thread LeBlanc Benjamin-Hugo (EXT)
: LeBlanc Benjamin-Hugo (EXT) Cc : openvas-discuss@wald.intevation.org Objet : Re: [Openvas-discuss] Managing many scanners instead of a master-slave architecture? I have never had the need or tested an distributed OpenVAS architecture but i think that it is possible. If you go to the menu Co

Re: [Openvas-discuss] Managing many scanners instead of a master-slave architecture?

2016-08-18 Thread Fábio Fernandes
Of course that you have to manually configure what scanner to use for each Task. And in terms of performance i don’t know since i never used it distributed but it makes sense that it will increase the performance for each scan you add. > No dia 18/08/2016, às 21:36, Fábio Fernandes > escreveu:

Re: [Openvas-discuss] Managing many scanners instead of a master-slave architecture?

2016-08-18 Thread Fábio Fernandes
I have never had the need or tested an distributed OpenVAS architecture but i think that it is possible. If you go to the menu Configuration->Slaves you will see that you can add remote slaves. In the Greenbone Manual you can see that you can setup an appliance as Sensor which i think it has the

[Openvas-discuss] Managing many scanners instead of a master-slave architecture?

2016-08-18 Thread LeBlanc Benjamin-Hugo (EXT)
Hello, We are seriously considering deploying OpenVAS in our organisation, and we will most certainly opt for a distributed architecture that matches our network segmentation. We understand so far that a Master-Slave configuration involves two instances of OpenVAS, each slave running on its own