Snort3 basic setup #885
Merged
Snort3 basic setup #885
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gsanchietti
force-pushed
the
snort3_giacomo
branch
2 times, most recently
from
21e0def to
3a52186
Compare
gsanchietti
force-pushed
the
snort3_giacomo
branch
from
cbb6e2f to
d7212e5
Compare
Closed
gsanchietti
force-pushed
the
snort3_giacomo
branch
from
c118062 to
79ec79f
Compare
gsanchietti
force-pushed
the
snort3_giacomo
branch
from
e6c87f0 to
25e1169
Compare
gsanchietti
added a commit
to NethServer/python3-nethsec
that referenced
this pull request
Dec 2, 2024
Imported from: https://github.com/jasonish/py-idstools/ Related PR: NethServer/nethsecurity#885
filippocarletti
approved these changes
Dec 3, 2024
gsanchietti
force-pushed
the
snort3_giacomo
branch
2 times, most recently
from
33ee9b1 to
4bdce2f
Compare
Nethesis custom config is under /var/ns-snort. The directory contains both temporary data and configuration. - Make sure there is always at least one rule so snort can correctly start - Setup all basic lua scripts - Move configuration and download data to a custom directory
Exclude blocking rules without relevant metadata. At time of writing, the number of blocked changes from 3075 to 2107.
The default rule is not required: snort can start without rules. Also the default rule was marking all traffic as pass.
API to configure Snort 3
Changes: - always setup queue_count and thread_count - add ns_policy option - add ns_disabled_rules option New options are directly used from ns-snort-rules
Changes: - remove ET rules: these rules do not work correctly on Snort 3 - read configuration from UCI - add --download option to force rules download
When a machine is rebooted or updated using an image, Snort rules are not present because stored in RAM. During the service start, if rules are not present, the init script now tries to load the rules multiple times. Maximum wait time is 1 minute. Snort will not fail the start: a nightly cron job can update the rules and restart the service.
The restart is required to load the new rules.
Official rules with a policy are rarerly triggered. Add the ns_alert_excluded option to alert all rules not belonging to a policy: this will give the user some insight about the network traffic without blocking rules with low confidence.
Make sure that all logs are stored to /var/log/messages to ease debugging. Also, such log can be sent remotely and stored safefly on the controller.
gsanchietti
force-pushed
the
snort3_giacomo
branch
from
4bdce2f to
7f08002
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NethSecurity configuration for Snort3:
Features:
Possible improvements:
Documentation:
Quick benchmarks on APU hardware in mbit/s:
This PR replaces #870 with a rebase on latest commit on main branch.
References: