redef Notice::emailed_types += {
SSH::Interesting_Hostname_Login,
HTTP::Malware_Hash_Registry_Match
};
I know the email alerts are working, as I have received notification from matches to SSH::Interesting_Hostname_Login. However, I don't know if the latter option, HTTP::Malware_Hash_Registry_Match, is functioning as intended.
Does this functionality of Bro work? I can see that the system is making DNS queries to the hash registry, but I want to make sure the alerting functionality is working. Is there a particular, known malicious, file that I can try downloading to see if I receive an alert?
Thanks,
Vincent
Message: 1xx.30.x.99 ef48afd2bb7ed04ed56f6a5dc22a2f91 hxxp://www.marinelog.com/templates/rt_solarsentinel_j15/js/rokfonts.js
Connection: 1xx.30.x.99:54767 -> 199.229.227.238:80
--
You received this message because you are subscribed to the Google Groups "security-onion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to security-onio...@googlegroups.com.
To post to this group, send email to securit...@googlegroups.com.
Visit this group at http://groups.google.com/group/security-onion.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "security-onion" group.
Seth,
I setup a simulated test for a file that I knew would have a hit in the registry. I captured the following DNS lookup and response via TCPDump:
18:26:32.070591 IP xx.xx.xx.10.34097 > xx.xx.xx.30.53: 49831+ A? cfc7b9dff5ce62a12e31457d974e5618.malware.hash.cymru.com. (73)
18:26:32.070711 IP xx.xx.xx.10.34097 > xx.xx.xx.30.53: 23934+ AAAA? cfc7b9dff5ce62a12e31457d974e5618.malware.hash.cymru.com. (73)
18:26:32.111464 IP xx.xx.xx.30.53 > xx.xx.xx.10.34097: 49831 1/0/1 A 127.0.0.2 (100)
18:26:32.115409 IP xx.xx.xx.30.53 > xx.xx.xx.10.34097: 23934 0/1/1 (128)
I believe the response, 127.0.0.2, indicates a hit in the registry, but I never received an email alert from Bro. Any ideas on what may be wrong?
Thanks,
Vincent
After performing a software update on the SO box, this is working as expected. Not sure what changed.
Thanks,
Vincent