Thank you for your answer, Fábio. This is indeed what we're thinking of doing. It should be noted though that we're only testing right now with the virtual appliance (VM) available on the OpenVAS website, and there are details on the Greenbone website that we're wondering whether they apply only to the Greenbone OS packaged with their physical appliances. For instance, enabling the Remote OMP Feature with the "set public_omp enabled" CLI command, and the steps that must be done in the console user interface launched with gos-admin-menu (disabling feed synchronization from the Internet + enabling updates from the Master in the 'Feed' menu; activating automatic Scan Sensor synchronization in the 'Sensors' menu, etc.)
Source: http://greenbone.net/learningcenter/configuring_slaves.html These steps seem necessary in order to set up the sensors; are these options available in the virtual appliance? And if so, has anyone experimented with them? Thank you, Ben LeBlanc Nurun Services conseils Quebec, Canada -----Message d'origine----- De : Fábio Fernandes [mailto:[email protected]] Envoyé : 18 août 2016 16:37 À : LeBlanc Benjamin-Hugo (EXT) Cc : [email protected] 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 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 whole package but only uses the scanner because of the way they configure it but it is only my opinion. If i were you i would configure an Master in a machine and then in another machine install OpenVAS but only activate the scanner (openvassd) then in the Manager i would add this scanner and update the Master and then see if the updates appear in the remote scanner. > No dia 18/08/2016, às 19:35, LeBlanc Benjamin-Hugo (EXT) > <[email protected]> escreveu: > > 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 > Manager-Scanner binome. But since each such Manager "has to take care on its > own to update the feed and release", while the Scanner synchronizes > automatically with its Manager, could we instead use one single Manager, and > bypass the Slave Managers to connect directly to multiple scanner components > of OpenVAS, defined as additonal scanners in the web interface? I.e., instead > of having one OpenVAS, PaloAlto and w3af scanner, running rather many > instances of the OpenVAS one from one single Manager? And if so, how would > that be handled by the Manager, performance-wise? > > Thank you, > > Ben LeBlanc > Nurun Services conseils > Quebec, Canada > > _______________________________________________ > Openvas-discuss mailing list > [email protected] > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
