[Oisf-users] alerting on alerts

[Champ Clark III]

This _might_ help. Sagan, which is a log analysis engine, has the option to "email" based on logs triggered. If you already know how to configure Suricata, then Sagan isn't likely to scare you. :) 



From: "Jeff Dyke" <jeff.dyke at gmail.com> 
To: "erik clark" <philosnef at gmail.com> 
Cc: "oisf-users" <oisf-users at lists.openinfosecfoundation.org> 
Sent: Wednesday, March 28, 2018 8:30:28 AM 
Subject: Re: [Oisf-users] alerting on alerts 

again, not applicable if you're not using AWS, but we have a Lambda that runs based on CW alert which grabs the last N log lines and sends them an email to our team, in pretty printed json format, so its pretty much instant. That project does look helpful, kind of wish it supported CW. 

On Wed, Mar 28, 2018 at 7:52 AM, erik clark < [ mailto:philosnef at gmail.com | philosnef at gmail.com ] > wrote: 



Jeff, we have about 5Mb/s burst (yes, our sustained is far lower than 5Mb/s). We have a really narrow target list in the network, since it sits behind an openvpn tunnel, so the alerts we would see would not be very many, and we would want to send an email for them so someone knows to go look at Kibana I suppose. I found elastalert ( [ https://github.com/Yelp/elastalert | https://github.com/Yelp/elastalert ] ) which seems like it might do? 

On Tue, Mar 27, 2018 at 5:12 PM, Jeff Dyke < [ mailto:jeff.dyke at gmail.com | jeff.dyke at gmail.com ] > wrote: 

BQ_BEGIN

What does your stack look like, if amazon, i have alerts coming out of CloudWatch based on metric filters. Given my blocking rules, these don't trigger often except to tell me a block has occured, but if you're using AWS, CloudWatch is better than setting up an ELK stack, which you can also do in AWS. What Travis pasted is basically my rules for CloudWatch. 

On Tue, Mar 27, 2018 at 2:04 PM, Travis Green < [ mailto:travis at travisgreen.net | travis at travisgreen.net ] > wrote: 

BQ_BEGIN

Erik, have you considered something like an hourly cron job to diff fast.log since last run, then email any new lines? Might not be the most robust solution but will probably get you by while you figure something better out. 
Here's an example: [ https://pastebin.com/YaQv0mzJ | https://pastebin.com/YaQv0mzJ ] 

Hope that helps, 
-Travis 

On Tue, Mar 27, 2018 at 6:53 AM, erik clark < [ mailto:philosnef at gmail.com | philosnef at gmail.com ] > wrote: 

BQ_BEGIN

I am trying to find an effective way to alert on critical signatures when they find it, preferably by email. What tools can be used to do this? We don't have a security team for this, so it has to be pretty straight forward. If needed, I can set up an ELK stack to handle this, assuming emails can be sent like Splunk. The easiest way to do and manage this, the better. :) Thank you for your input! 

_______________________________________________ 
Suricata IDS Users mailing list: [ mailto:oisf-users at openinfosecfoundation.org | oisf-users at openinfosecfoundation.org ] 
Site: [ http://suricata-ids.org/ | http://suricata-ids.org ] | Support: [ http://suricata-ids.org/support/ | http://suricata-ids.org/support/ ] 
List: [ https://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users | https://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users ] 

Conference: [ https://suricon.net/ | https://suricon.net ] 
Trainings: [ https://suricata-ids.org/training/ | https://suricata-ids.org/training/ ] 






-- 
PGP: ABE625E6 
[ http://keybase.io/travisbgreen | keybase.io/travisbgreen ] 

_______________________________________________ 
Suricata IDS Users mailing list: [ mailto:oisf-users at openinfosecfoundation.org | oisf-users at openinfosecfoundation.org ] 
Site: [ http://suricata-ids.org/ | http://suricata-ids.org ] | Support: [ http://suricata-ids.org/support/ | http://suricata-ids.org/support/ ] 
List: [ https://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users | https://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users ] 

Conference: [ https://suricon.net/ | https://suricon.net ] 
Trainings: [ https://suricata-ids.org/training/ | https://suricata-ids.org/training/ ] 

BQ_END



BQ_END



BQ_END



_______________________________________________ 
Suricata IDS Users mailing list: oisf-users at openinfosecfoundation.org 
Site: http://suricata-ids.org | Support: http://suricata-ids.org/support/ 
List: https://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users 

Conference: https://suricon.net 
Trainings: https://suricata-ids.org/training/ 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openinfosecfoundation.org/pipermail/oisf-users/attachments/20180328/001737f4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2111 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openinfosecfoundation.org/pipermail/oisf-users/attachments/20180328/001737f4/attachment-0001.bin>