Skip to content
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

[FR]IDS/IPS: Drop event logging switch and alert details #4841

Closed
2 tasks done
kulikov-a opened this issue Mar 18, 2021 · 7 comments
Closed
2 tasks done

[FR]IDS/IPS: Drop event logging switch and alert details #4841

kulikov-a opened this issue Mar 18, 2021 · 7 comments
Labels
help wanted Contributor missing / timeout

Comments

@kulikov-a
Copy link
Member

kulikov-a commented Mar 18, 2021

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Is your feature request related to a problem? Please describe.

Hi!
now if the IPS drops the packet two lines appear in the Alerts tab: one for the Alert event and the second for the Drop event.
both contain the same information although the Alert event may contain information about the payload
IDS_de0

Describe the solution you like

could you please consider adding an Drop events logging switch. and adding debug info display for Drop events?

IDS_de1
IDS_de2

Thanks!
Describe alternatives you considered

Just disable drop events logging in suricata.yaml template:
`
- drop:
alerts: yes # log alerts that caused drops
flows: start # start or all: 'start' logs only a single drop
# per flow direction. All logs each dropped pkt.

`

Additional context

Add any other context or screenshots about the feature request here or links to relevant forum thread or similar

@AdSchellevis
Copy link
Member

I think there was another ticket about this a long time ago and there was some issue with solving it without side affects, so I'm a bit cautious here....

@kulikov-a
Copy link
Member Author

@AdSchellevis
thanks. hmm. searched before making the request. perhaps not enough. I'll try again

@AdSchellevis
Copy link
Member

no problem, not saying we shouldn't look at this, just cautious ;)

@kulikov-a
Copy link
Member Author

) thanks. I see the commit when it appeared but unfortunately there is no additional information why
573612d#diff-61dc886561c7b1530e89119eab64a828fb1dc9f63768d4d307a99063c73316e2

@AdSchellevis
Copy link
Member

Maybe it crosses my mind one of these days, vaguely remember there was "something" with it.

@kulikov-a
Copy link
Member Author

in any case, this is another reason to once again compare the behavior with enabled and disabled logging. I will test it for a while. thanks!

@OPNsense-bot
Copy link

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository,
please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.

@OPNsense-bot OPNsense-bot added the help wanted Contributor missing / timeout label Sep 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Contributor missing / timeout
Development

No branches or pull requests

3 participants