Skip to content
Discussion options

You must be logged in to vote

A passing so-elastalert-test only proves the query matches. It wraps elastalert-test-rule, which searches the last day with the debug alerter (unless you pass -a), so it never creates anything SOC can show.

SOC's Alerts page only shows ElastAlert hits that land in logs-detections.alerts-so with tags: alert, and on 3.3.0 the only thing that writes those is SO's own alerter, modules.so.securityonion-es.SecurityOnionESAlerter (source). A rule with alert: debug (the so-elastalert-create default), email or Slack can match every failed login and still never appear in SOC.

The supported route for app logs is a Sigma detection: Detections, create a new Sigma rule, paste this (keep the id SOC pre-…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by Simonbunse
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
3.0
Labels
None yet
3 participants