Best way to install/scale OpenVAS?

[Lukas]

@carl

If your target /22 is a cloud network (sdn) you will miss the .0 and .255 for this network.

If you have a /22 network and you substract the Network “.0” and the Broadcast (highest bit) you still get 1022 hosts Normally you don´t scan on “.0” as well the broadcast, that makes no scene at all.

Classless Inter-Domain Routing

@carl

I was not talking about the kernel you run inside your gvm boxes.

You still don´t get it right, GOS runs on our appliances, GVM is the free (like freedom) stack and the Kernel is part of GOS.

Frequently Asked Questions (FAQ)

@carl

Maybe you simply don’t need to do the “recon phase (mass-scanning)” inside docker

Then running a scanner inside docker is pointless

@carl

yeah “masscan” could maybe help with the tcp narrowing, b

Not on IPv6, we develop our own solution for that at the moment.

@carl

Maybe also something like shodan or other stuff already available tells you what you need to scan / verify.

I don´t think this is beneficial for the community at this point. We should take from this post:

• Docker is not useful for big networks, without customization. You exactly need to understand the underlying network and kernel configuration.
• Do not use stateful device/mechanisms within your scan-system (docker, dsl-router, NAT, Kernel …) if you wanna scale the OpenVAS for a big network.
• Try to run the up link and connectivity stateless.