-
Version2.4.190 Installation MethodSecurity Onion ISO image Descriptionconfiguration Installation TypeDistributed Locationon-prem with Internet access Hardware SpecsExceeds minimum requirements CPU20 RAM256gb Storage for /300gb Storage for /nsm2tb Network Traffic Collectionspan port Network Traffic Speeds1Gbps to 10Gbps StatusYes, all services on all nodes are running OK Salt StatusNo, there are no failures LogsNo, there are no additional clues DetailAfter 5 faithful years of 24/7 service, our hard drives in our distributed cluster are starting to fail. The good news is that we budgeted to purchase new drives and have acquired a handful of newer servers. The plan is to rip out the old servers and green field another cluster. We have documented all our changes over the years, but one thing has drawn a slight blank. What is the most efficient way to export and import our Suricata rule tuning in version 2.4.190? I've searched the documentation and community support and didn't see that covered anywhere. Thanks! Guidelines
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Some of your tuning will be backed up in If you have custom detections and overrides, you will see them in |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, that pointed me in the right direction. So I need to grab a backup: https://docs.securityonion.net/en/2.4/backup.html Then I need to restore it on my new Manager: I'm posting the links here incase someone else needs this info. The backup contains a copy of Suricatta thresholds / suppressions. It's located at /opt/so/saltstack/local/salt/suricata/thresholding/sids.yaml incase you just need that specific file. |
Beta Was this translation helpful? Give feedback.
Some of your tuning will be backed up in
/nsm/backup/so-config-backup-<date>.tarThat will be pillar and salt data in the local path, for example, your idstools pillar.If you have custom detections and overrides, you will see them in
/nsm/backup/detections/repo