Why am I missing some Nessus Events?

[mdorobek]

We are useing the Splunk Add-on for Nessus. The saved searches are active and everything seems to work well.
I made a top ten of the events counted by the host-fqdn and sort by the severity.

Heres the search:

index=nessus sourcetype="nessus:scan" severity_id>0  | rex field=host-fqdn "(?<Hostname>[^.]*)"| chart count by Hostname, severity | table Hostname,  critical,  high,  medium,  low | sort by -critical, -high, -medium, -low  | head 10

The search seems to be correct, but there are some differences between the ammount of Events in Splunk and the Nessus vulerability scanner.

Does anyone know what the reason could be?

[gfreitas · Accepted solution]

Hi,

I am having the same problem and I realized that the add-on downloads one event for each vulnerability by host. If the same host have the same vulnerability but in different ports, the add-on is going to download just one event (without port) but on Nessus you can see two vulnerabilities, one for each port.

Hope this helps.

[mdorobek]

Thank you, this explains a lot.