Repository navigation
ElastAlert rule doesn't fire for custom app log source, even though documents are visible in Kibana #16347
Version3.3.0 Installation MethodSecurity Onion ISO image Descriptionconfiguration Installation TypeStandalone Locationon-prem with Internet access Hardware SpecsMeets minimum requirements CPU8 RAM32gb Storage for /650gb Storage for /nsm650gb Network Traffic Collectionother (please provide detail below) Network Traffic SpeedsLess than 1Gbps StatusYes, all services on all nodes are running OK Salt StatusYes, there are salt failures (please provide detail below) LogsNo, there are no additional clues DetailI'm trying to use Security Onion as the alerting backend for a custom Setup:
What I'm trying to figure out:
Happy to share the full rule YAML and so-elastalert-test output if Guidelines
|
Replies: 2 comments
|
Can you share what your |
|
A passing SOC's Alerts page only shows ElastAlert hits that land in The supported route for app logs is a Sigma detection: Detections, create a new Sigma rule, paste this (keep the id SOC pre-fills), and enable it: title: Laravel Failed Login
id: 6f1f5c55-3b0e-4b8e-9a59-0c1f8a3c2d11
status: experimental
description: Failed login attempt logged by the Laravel app (channel security).
logsource:
product: laravel
service: security
detection:
selection:
event.action: login_failed
condition: selection
level: mediumSOC then writes the ElastAlert rule itself, with If you keep a hand-written rule instead:
On the time-window gap: ElastAlert runs every 3 minutes and only looks back |
A passing
so-elastalert-testonly proves the query matches. It wrapselastalert-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-sowithtags: 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 withalert: debug(theso-elastalert-createdefault), 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-…