what does this line do ? | foreach %* [eval <>=mvindex(<>,0)] ... View more

for version 1.3 of nessus data importer, scan names with spaces are not compatible. Rename the scan or rerun under a different (non-space) name. ... View more

ok great(kind off) I would recommend you change the scan name to non-spaces if you want it immediately. I note this and see if its something I can work on for future versions.. that is " importing scan names with spaces" ... View more

taking a guess here but it can also be the spaces in your scan name, if your scan(s) has spaces the same way your example does.. if this is the case please be sure to let me know.... ill test out as well. ... View more

sorry your having this issue on the file , nessus2splunkjson.py look at lines 33 and 34 , are your "dropdir" and "pickupdir" correct and match your enviroment? -also can you paste lines 310-315 from your nessus2splunkjson.py -are you running the latest version 1.3? ... View more

awesome, dont forget to switch back to api keys, it works allot better with that method as authentication. ... View more

@jmatthews_sovrn check out @spayneort most recent post, although the work around may work , the underlying issue might be with nessus app itself and not the import script. I would run nessusd -R to re-process plugins , otherwise you might be skipping over and not importing valuable data. Regardless, I will check with nessus to see if there can infact be an instance of a plugin without attributes, however I have yet to see this given your nessus is configured and operating correctly. If it turns out that plugins with no attributes is not normal .. I will look into building some sort of error checking into future versions. Thank you very much for bringing this issue up and your help is much appreciated. ... View more

interesting , i get a different outcome for plugin (66334) .. see below is your version and pluginset the same as mine? (my plugins just updated as I started up) 6.4.2 (#34) Plugin Set 201508210415 /plugins/plugin/66334 { "attributes": [ { "attribute_value": "patches_summary.nbin", "attribute_name": "fname" }, { "attribute_value": "Patch Report", "attribute_name": "plugin_name" }, { "attribute_value": "$Revision: 1.47 $", "attribute_name": "script_version" }, { "attribute_value": "Install the patches listed below.", "attribute_name": "solution" }, { "attribute_value": "None", "attribute_name": "risk_factor" }, { "attribute_value": "The remote host is missing one or more security patches. This plugin\nlists the newest version of each patch to install to make sure the\nremote host is up-to-date.", "attribute_name": "description" }, { "attribute_value": "all", "attribute_name": "agent" }, { "attribute_value": "2013/07/08", "attribute_name": "plugin_publication_date" }, { "attribute_value": "local", "attribute_name": "plugin_type" }, { "attribute_value": "The remote host is missing several patches.", "attribute_name": "synopsis" }, { "attribute_value": "2015/08/11", "attribute_name": "plugin_modification_date" } ], "family_name": "General", "name": "Patch Report", "id": 66334 } ... View more

No worries, can you post your version for nessus and plugin sets? im also looking into @spayneort work around ... View more

jim , im sorry you are having this issue.. i have seen this before when its a new install of nessus , is it? if it is, did you update the nessus plugins successfully without any errors? if it is not a new nessus install, what is the nessus status of the scan you are trying to import? "fooserver.foo.com " is it "completed", "aborted", "canceled" etc. regards alain ... View more