mikenowak / docker-nessus

Nessus Vulnerability Scanner in a Docker container
MIT License
10 stars 12 forks source link

WebUI Issue when Scanning #1

Closed BrendanThompson closed 6 years ago

BrendanThompson commented 7 years ago

Hi there,

I am running the latest version of the docker container, which has updated Nessus to the latest version as well.

When I run a scan on a network it tanks the WebUI and I'm no longer able to login. The container doesn't look as though it's doing too much the RAM usage is under 20% of available and the CPU usage is about a full CPU.

Just wondering if this is something that you've seen before?

mikenowak commented 7 years ago

Hi @BrendanThompson

no matter how silly it may sound, - are you accessing the WebUI over a WAN link by a chance?

BrendanThompson commented 7 years ago

Hey Mike,

I’m accessing it all internally, just on local host :)

Sent from my iPhone

On 4 Jul 2017, at 18:22, Mike Nowak notifications@github.com<mailto:notifications@github.com> wrote:

Hi @BrendanThompsonhttps://github.com/brendanthompson

no matter how silly it may sound, - are you accessing the WebUI over a WAN link by a chance?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/mikenowak/docker-casa-nessus/issues/1#issuecomment-312813591, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACebgFGdQKgS2Rr8kSOd642GYXj4OI3Tks5sKfY-gaJpZM4OM6Gp.

mikenowak commented 7 years ago

hi @BrendanThompson, ok fair enough - the only reason I asked about WAN is that I have a similar issue over a WAN link - but thats probably latency between Asia and Europe more than anything.

The only other thing that comes to mind is that the scan saturates your NIC - and nessus can really do that.

So the question is - are there any other containers running on the same host where your Nessus is? Are they reachable during the scan?

I suggest running iftop or something similar on the physical host to see what it happening in the network.

You may also try to enable "Slow down the scan when network congestion is detected" under Performance Options (see Policy -> Settings -> Advanced), and see if this improves the situation in any way.

Let me know how you get on.

BrendanThompson commented 7 years ago

@mikenowak I tried telnetting from my localhost to a remote box and was able to do so, however I was unable to from within the container.

mikenowak commented 6 years ago

its bit dated, and I was unable to reproduce - so closing off