-
Notifications
You must be signed in to change notification settings - Fork 759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Suricata - Add payload support #1911
Comments
|
Hi Guillaume, It's not already on the list, but indeed quite useful. Best regards, Ad |
|
Thanks a lot @AdSchellevis, sure it can be an optional feature. As an ugly hack to enable this functionality manually, you can follow what I wrote in the forum here : https://forum.opnsense.org/index.php?topic=6284.msg26746#msg26746 Quote :
|
…. support enable/disable rule from log view. for #1911
|
To test on a recent version of OPNsense, use : |
- add options to suricata yaml - add tls and http options in alert view - bug: fix issue with grid when interface is missing (crash on replace()) - style: change dialog markup, a bit wider and less padding. a bit related to #1911
|
Some more work done on the alert viewer in 38aafc8 below examples of alerts with and without payload enabled. |
|
We pull our OpnSense syslog into ELK, so the more context we could get here, the merrier (not too worried about flooding elastic clusters with FW logs). Thank you much |
|
@sempervictus thank you for the encouragement! |
|
All done, thanks! |



Hello,
I think it's not already asked (I did not find this feature request).
Is it possible to add the payload support in "eve-log" and display the result in the WebUI ?
It will be very useful to get this information to enable/disable/investigate Suricata rules.
Thanks,
Guillaume.
The text was updated successfully, but these errors were encountered: