Repository navigation
Replies: 1 comment
|
Your filter structure is valid BPF, and yes, you should set it under bpf > zeek as well. Each of the three lists applies to a different tool, so a filter in one place does not cover the others.
If you enter the filter as several list entries, they are joined with spaces into one expression. So either keep it as one entry or make sure the parts combine into a valid expression.
(I looked this up in the code with help from an AI assistant; the links are to the lines I checked.) |
Uh oh!
There was an error while loading. Please reload this page.
Version
3.3.0
Installation Method
Security Onion ISO image
Description
configuration
Installation Type
Distributed
Location
airgap
Hardware Specs
Meets minimum requirements
CPU
16
RAM
128
Storage for /
400gb
Storage for /nsm
5tb
Network Traffic Collection
tap
Network Traffic Speeds
Less than 1Gbps
Status
Yes, all services on all nodes are running OK
Salt Status
No, there are no failures
Logs
No, there are no additional clues
Detail
We have heavy backup traffic between one backup server and a group of internal hosts, on specific ports. We want to stop processing and recording this traffic, without excluding any other traffic to or from these hosts.
We set a filter with this structure under bpf > pcap and bpf > suricata (placeholders instead of real values):
not (host <BACKUP_SERVER> and (host <HOST_1> or host <HOST_2> or ... or host <HOST_N>) and (port <PORT_A> or port <PORT_B>))
Questions:
Guidelines
All reactions