DOT-NESSUS FILE

Tenable Team,
 
I was pleasantly surprised to find out that extraneous XML is not
stripped out of the dot-nessus file by the scanner.  I plan to create a
new node called <Directives> (a sibling to <Policies>) and beneath that
will be configuration items of my own which will be consumed by
post-scan handlers (e.g., scripts that convert and email the scan
results).  For example:
 
<?xml version="1.0"?>
<NessusClientData>
  <Directives>
    <Directive>
      <name>outputFormats</name>
      <value>html;nbe</value>
    </Directive>
    <Directive>
      <name>emailRecipients</name>
      <value>jscherff@24hourfit.com,deraison@nessus.org</value>
    </Directive>
    <Directive>
      <name>attachResults</name>
      <value>no</value>
    </Directive>
    <Directive>
      <name>stripInfos</name>
      <value>yes</value>
    </Directive>
  </Directives>
  <Targets>
    ...
  </Targets>
  <Policies>
    <Policy passwordsType="Linux">
      <policyName/>
      <policyComments/>
      ...
</NessusClientData>
 
My question: Is it by accident or design that unused XML is ignored and
left untouched by the nessus, and will this continue to be the behavior
in the future?
 
Thanks,
 
John Scherff
Information Security and Storage Manager
24 Hour Fitness
o: 760-918-4485
c: 760-351-6946
e: jscherff@24hourfit.com
 
The code of competence is the only system of morality that's on a gold
standard. -Ayn Rand
 

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus