Building Vulnerability Scanners with Portainer

  Currently, I am in school for my Master, and we had an assignment to conduct vulnerability scanning on our home network.  It has been a while since I installed Nessus or OpenVAS, and technology has certainly changed. 

I have been using Portainer recently for most of my Docker containers and wanted to see if it was that easy for Nessus or OpenVAS.   

For Nessus, I did a search for 'Nessus docker-compose' 

version: '3.1'

services:

  nessus:
    image: tenableofficial/nessus
    restart: always
    container_name: nessus
    environment:
      USERNAME: <user>
      PASSWORD: <password>
      ACTIVATION_CODE: <code>
    ports:
      - 8834:8834

I changed the username/password and activation code.  Then I went into Portainer, created a new stack, and placed the above in the web editor.  

From there, I clicked deploy stack.  About 20 minutes later (plugin updates on Nessus), I was up and operational on Nessus Essentials.  One side note to this is that Essentials will only scan 16 IPs, but it's free.

For OpenVAS I searched on Google for 'OpenVAS docker-compose' and found https://github.com/immauss/openvas.  From there, I used the below:

version: "3"
	services:
	openvas:
	ports:
	- "8080:9392"
	environment:
	- "PASSWORD=admin"
	- "USERNAME=admin"
	- "RELAYHOST=172.17.0.1"
	- "SMTPPORT=25"
	- "REDISDBS=512" # number of Redis DBs to use
	- "QUIET=false" # dump feed sync noise to /dev/null
	- "NEWDB=false" # only use this for creating a blank DB
	- "SKIPSYNC=true" # Skips the feed sync on startup.
	- "RESTORE=false" # This probably not be used from compose... see docs.
	- "DEBUG=false" # This will cause the container to stop and not actually start gvmd
	- "HTTPS=false" # wether to use HTTPS or not
	volumes:
	- "openvas:/data"
	container_name: openvas
	image: immauss/openvas:$TAG
	volumes:
	openvas:

Footer

© 2022 GitHub, Inc.

Footer navigation

• Terms
• Privacy

Same procedures as Nessus.  Opened Portainer, and added new stack.  The web editor copied the above information and deployed stack.   On this one, I forgot to update the username/password for my instance.  So that shows as a vulnerability as you conduct a scan. 

Overall, both of these installs were very easy, and I was up and running in about 30 minutes and running scans against my home network.