11:32:03 -0500 Mason Malone * Fix dependency error in nessus::config 15:23:17 -0800 Adam Crews * Updating spec framework 15:30:50 -0800 Adam Crews * Removed deprecated 'types' from metadata.json' 16:08:40 -0800 Adam Crews * travis updates (origin/fix_tests) 16:23:28 -0800 Adam Crews * Fix travis notifications and bump version for release (HEAD -> fix_tests) Individual contributors can be found at: Many thanks to PuppetLabs and their ntp module for the template to work off of. So far only Nessus 5.2.7 and Nessus 6 on CentOS6 has been tested. Additionally, it is not possible to completely test the activation portion of nessus, since each activation is unique, and you would need a new activation code from nessus every time you try to activate. This module has some tests in place, but not many yet.

nessus_activation_code is set to the code that is active on the node, or undefined if no code is active.

Selects wether puppet should manage the service. The name of the nessus package being installed, defaults to 'Nessus'.ĭetermines what to do with the package, valid options are present/installed, latest, or absent.Ĭonfigure nessus to be connected to Security Center.ĭetermines the state of the service, valid options are running or stopped. The code used to download nessus plugin updates.

The following parameters are available in the nessus module:

nessus::config: Activate and configure nessus.

It must be available in wherever your system pulls packages from.

nessus::install: Handles installing the package.

nessus: Main class, includes all other classes.If you wish to activate an update feed, then you can specify an activation_code like this: class Include ::nessus is sufficient to get nessus installed and running with default settings. The nessus module installs, configures, and manages the nessus vulnerability scanner software. Reference - Class, parameter, and fact documentation.

Usage - Configuration options and examples.

How to use nessus ubuntu