Re: [Openvas-discuss] how to minimize harm when introducing vuln scanning to a network

Thanks everyone so far, including the omnipresent Rui. This information is very helpful. Peter On Thu, Mar 15, 2018 at 4:55 AM, tatooin wrote: > Hi Peter, > > I am using OpenVAS to conduct VA in the environment of a big corporate > network (up to /21 networks) on a regular

Re: [Openvas-discuss] how to minimize harm when introducing vuln scanning to a network

Hi *, On 14.03.2018 20:59, TJ wrote: > I would exclude networked printers as the scans can cause them to > produce volumes of printed gibberish (found out the hard way) we have tried to work around this in the last year and implemented a few additional mitigations which showed quite good results

Re: [Openvas-discuss] how to minimize harm when introducing vuln scanning to a network

Good to know.  I will look into going to a newer version! On 3/15/2018 1:42 PM, Christian Fischer wrote: Hi *, On 14.03.2018 20:59, TJ wrote: I would exclude networked printers as the scans can cause them to produce volumes of printed gibberish (found out the hard way) we have tried to work

Re: [Openvas-discuss] how to minimize harm when introducing vuln scanning to a network

I have actually hit issues with scanning our hosts and what I have done is try to categorize the different types of hosts based on what they run (both OS and applications). Then create Scanning Policies that target the category of host being scanned. Since we also have machines in AWS, our

Re: [Openvas-discuss] how to minimize harm when introducing vuln scanning to a network

Hi Peter, I am using OpenVAS to conduct VA in the environment of a big corporate network (up to /21 networks) on a regular basis, and so far I have never witnessed any incidents on the IT world. I'm using default OpenVAS profile, altough I have also tried the most impactful profiles. So on IT