Robert, Here's something I came up with that builds a "safe" .nessusrc by looking at the script_category line in each plugin that is installed on the system. I'd be interested in knowing what you think about it.
The approach used was to break up the .nessusrc file into three separate
files like so:
Beginning of the file up to "begin(PLUGIN_SET)" = file 1
File that gets generated via this script = file 2
Everything remaining get stored in = file 3
So after having file 1 and 3 on the system (should be prepared in
advance), this script will generate the plugin list (file 2) and then
we'll just cat them all together into .nessusrc
I've been meaning to explore this modular approach further but just
haven't had the time to run with it.
Best,
Adam
" With all this talk about cli interfaces, figured id post my
" questions/concerns. I'm writing (as many others are) a web gui to help
" me facilitate my scans/reporting.
"
" I am having a bitch of a time with the .nessusrc file and understanding
" it (is there any documentation direclty related to .nessusrc?) . Scanner
" Set section in particular is whats confused me. What does it do?
"
" begin(SCANNER_SET)
" 10180 = yes
" 10277 = no
" 10278 = no
" 10331 = no
" 10335 = no
" 10841 = no
" 10336 = yes
" end(SCANNER_SET)
"
" Also, if I understand correctly begin(PLUGIN_SET) is either a yes or no
" for each plugin which can only be updated automagically by the GUI. If
" so, has anyone written a script to perhaps update .nessusrc plugins
" selection w/o using the GUI? Something that scans the plugins dir, gets
" the new plugins dowloaded, sees if it's classified as DoS, etc. and make
" a decision and include it based on that? Or even better a PHP script to
" edit the .nessusrc?
"
" Robert Timko, CISSP
"
--
"Silly hacker, root is for administrators"
- Unknown
GnuPG Key : 11C2 79F6 BD3D 3A86 5640 3DA0 3860 B30E 711D 3B66
nessus-build-saferc.sh
Description: Bourne shell script
msg03573/pgp00000.pgp
Description: PGP signature
