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

Am 14.03.2018 um 21:06 schrieb Eero Volotinen: I usually prefer lower scan speed as too intensive can crash firewall devices.. if a security scan from a single node crashs your firewall device you should say "thank you" for konwing that this crap needs to be replaced ASAP real attackers

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

Hi! I am performing vulnerability testing in large scale enterprise for a while now and I have seen everything. To start with: * If a system crashes, it is not caused by the scan, there is a DOS vulnerability found by the scanner. * If a system acts unpredicted, it’s an weakness found by the

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

I usually prefer lower scan speed as too intensive can crash firewall devices.. Eero 14.3.2018 22.01 "TJ" kirjoitti: > I would exclude networked printers as the scans can cause them to produce > volumes of printed gibberish (found out the hard way) > > Yes, definitely scan

Re: [Openvas-discuss] Internal error: get_many:2338 (GSA 7.0.2)

I just ran into the same.I tried omp --verbose --get-tasks and got the same error. What I found is that I had named a task using an ampersand in the title. To dig it out I used DB Browser for SQLite from http://sqlitebrowser.org/ Make an offline copy of the

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

well. it depends on scan settings. on wrong settings it can dos/crash your systems or network devices.. Eero 14.3.2018 21.53 "Peter Collins" kirjoitti: > (Sorry if this is a repost. I had a technical issue with my first attempt) > > I would like to use OSSIM's OpenVAS

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

(Sorry if this is a repost. I had a technical issue with my first attempt) I would like to use OSSIM's OpenVAS component to run asset and vulnerability scans on both prod and non-prod. Like every place, we want to make sure the IT infrastructure is not harmed or jeopardized. So what is due care