Upgrade to 2.4.190, Suricata: Rule Mismatch #15190
-
Version2.4.190 Installation MethodSecurity Onion ISO image Descriptionupgrading Installation TypeStandalone Locationon-prem with Internet access Hardware SpecsExceeds minimum requirements CPU48 (2 sockets, 24 cores) [x86-64-v2-AES] RAM150GB [balloon=0] Storage for /300G Storage for /nsm3000G 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 DetailStandalone installation used domestically, partially for self learning and partially as the household's SIEM. Installation is about a year old and has successfully upgraded a number of times in the past. This time around, I upgraded from 2.4.170 (I think, but wasn't really paying attention) to 2.4.190. Post upgrade, I also enabled ti_abusech in the Windows and Linux endpoint elastic tools with my API key. All seemed to work OK at the time and I didn't pay much further attention. But a few days later I noticed that previously suppressed suricata alerts were now appearing and that the "tune detection" in the drop down list is greyed out. An exclamation mark has appeared in the Detections page. I have followed the prior discussion on #13109 for additional guidance, with similar results.
These rule files are empty The log file There are logs in I have restarted Security Onion and also tried a SOUP, without any success. I am presently out of ideas for possible next steps. Thoughts? Guidelines
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
|
If you click on the |
Beta Was this translation helpful? Give feedback.
-
|
Ahh, OK. I didn't realise that I could click on the Rule Mismatch to dig further. This is the extract from the log The log file path pointed to is Grepping through the log for Digging around a bit more, I followed this discussion #13112 I picked the first rule that is barfing Selecting the pre-canned rule The contents of I am stuck again as to how to proceed next. |
Beta Was this translation helpful? Give feedback.
It looks like your Suricata rules did not make it into the so-detection index.
Try this:
Remove
/opt/so/conf/soc/fingerprints/emerging-all.fingerprintand/opt/so/conf/soc/fingerprints/suricataengine.stateRestart SOC -
sudo so-soc-restartRun a full sync on Suricata rules from Detections