Understanding usage to LightSPD rules
Dheeraj Gupta via Snort-users <[email protected]> Thu, 21 Mar 2024 11:08:37 +0530
| Newsgroups | gmane.comp.security.ids.snort.general |
|---|---|
| Message-ID | <CAOsL98Mv_sXCLZpM0AuVWK+2PJfmjWqqv1jRp3NUXUDD1wJDdQ__17860.1041365013$1711000229$gmane$org@mail.gmail.com> |
Hi, We have been using the snapshot ruleset for Snort since last many years with pulledpork (the original perl script which has been patched to support Snort3). With Snort3 and its accelerated release cycle, snapshots are no longer generated for each version. So these days we download the latest snapshot and just rename it to whatever version we are using for pulledpork to pick it up. The available guidance on official site points to using the LightSPD rules and I have seen that the stated goal of pulledpork3 Python project is to support Snort3 rule management using traditional snapshot or new LightSPD rules. My understanding is that LightSPD rules basically bundle all the rules for all the versions together and use a `manifest.json` to allow users to choose the correct ruleset based on their version. However, I have a few queries: 1. In manifest.json in LightSPD, under each version, there is a key called "extended_rule_groups" which points to a bunch of `extended_rule_groups.json` files. However, these JSON files do not exist at their purported paths. Is this a bug or are these files part of a future improvement which is not yet implemented? 2. How are we supposed to gather the non-SO rules? Should we just recurse under all directories and gather all the rules or is manifest.json to be used there as well? 3. The last commit to Pulledpork3 project was almost a year ago. Since then it appears that rule directory structure has been updated. E.g. new rulesets have subdirectories other than 3.0.0.0 (3.1.35.0 etc.). But the code has only a single sub-directory (3.0.0.0) hard-coded in it. Thus, it doesn't seem that newer rulesets will be processed correctly by Pulledpork3. Old pulledpork (perl one) while able to support Snort3 has no concept of LightSPD rules. So how are we supposed to apply these rules while running Snort? 3. Is there an up-to-date general documentation about best practices for Snort signature management? Regards, Dheeraj _______________________________________________ Snort-users mailing list [email protected] Go to this URL to change user options or unsubscribe: https://lists.snort.org/mailman/listinfo/snort-users To unsubscribe, send an email to: [email protected] Please visit http://blog.snort.org to stay current on all the latest Snort news! Please follow these rules: https://snort.org/faq/what-is-the-mailing-list-etiquette