Actions
Task #5666
openrules: help to visualize how a Suricata rule matches (different contents/offsets)
Description
Have a Wireshark module/plugin that helps to visualize how a Suricata rule matches its different contents / pcres step by step
Updated by Philippe Antoine 3 months ago
- Related to Task #5488: Suricon 2022 brainstorm added
Updated by Philippe Antoine 3 months ago
- Tracker changed from Optimization to Task
Updated by Philippe Antoine 3 months ago
- Related to Task #4432: libsuricata: Wireshark plugin as an example added
Updated by Anthony Verez 3 months ago
As a workaround for now: https://github.com/google/gonids/blob/master/rule.go#L608 can match a part of a pcap matching with a rule (when the rule does already trigger the capture)
Updated by Victor Julien 3 months ago
- Subject changed from Rules : help to visualize how a Suricata rule matches (different contents/offsets) to rules: help to visualize how a Suricata rule matches (different contents/offsets)
Updated by Victor Julien 2 months ago
The way I see this ticket work is a new eve event type like "rule trace" or something, that would dump the matching steps from the detection engine, logging:
- prefilters called
- rule keywords called
- content inspection step my step, including matching offsets, etc
This could then be used to construct the "story" of how a match (or a non-match) came to be, and it could be used visualize outside of suri, like in Wireshark.
Actions