-
Version2.4.140 Installation MethodSecurity Onion ISO image Descriptionother (please provide detail below) Installation TypeDistributed Locationon-prem with Internet access Hardware SpecsExceeds minimum requirements CPU42 RAM128 Storage for /300GB Storage for /nsm1TB Network Traffic Collectionspan port Network Traffic SpeedsLess than 1Gbps StatusYes, all services on all nodes are running OK Salt StatusNo, there are no failures LogsNo, there are no additional clues DetailGuidelines
Hi, Version I'm testing the Elastic Endpoint and found that no alerts are being generated from it. Output of
Any ideas what's wrong with my setup? Are those rules even supposed to be utilized by the Security Onion ? Best Regards, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Beta Was this translation helpful? Give feedback.
-
@presianbg We currently map I have created an issue to track this - possibly we can automagically swap that mapping to Elastic Defend if we see the |
Beta Was this translation helpful? Give feedback.
Figure it out... this rule is for alerting upon malware detection.
The default Elastic Defend integration setting is
off
, so turning it on and dropping a malware on the host is creating the missing index and alert is being triggered:So the next missing piece is how to make it appear as an alert in SOC dashboard:
Any ideas ?Looks like a custom sigma rule in
Detections
is the only path forward: