|Applies To||RSA Product Set: Security Analytics, NetWitness Logs & Network|
RSA Version/Condition: 10.x, 11.x
O/S Version: EL6, EL7
|Issue||Berkeley Packet Filter or BPF is not filtering the expected traffic on RSA Security Analytics or NetWitness decoders due to VLAN tagging.|
A tcpdump or windump filter is not producing the expected output while testing a potential BPF.
BPF has been implemented in Decoder Configuration from ADMIN (for NW11) or Administration (for SA10)->Services-Config for the decoder->General but you're still seeing the sessions in RSA Security Analytics or NetWitness Investigation.
|Cause||Per System-level (BPF) packet filtering best practices and examples for RSA NetWitness decoders or the User Guide, BPF filters should be tested using tcpdump or windump prior to implementation to ensure they provide the expected behavior. In certain instances and on some networks, you might encounter issues where the variables supplied to tcpdump are not presenting the expected output. This might be due to instances where the network being sniffed is segmented into several VLAN's and the packets are being tagged with a VLAN ID. |
Using the below tcpdump variables, you would expect to see traffic to or from the host 10.20.10.12. When the packets being sniffed are tagged with VLAN ID's, the below tcpdump statement will yield ZERO results despite traffic originating from or destined to 10.20.10.12:
tcpdump host 10.20.10.12
Therefore, in an adverse query, you would expect to see no results containing 10.20.10.12 with the below tcpdump statement. As previously mentioned, if the packets being sniffed are tagged with VLAN ID's, the above statement will NOT filter out the traffic and you will see activity to and from 10.20.10.12
tcpdump not (host 10.20.10.12)
In these instances, you should try combining the current tcpdump variables with the vlan variable to correctly identify this traffic. Modifying the above queries to the below syntax, tcpdump will filter the traffic and output the expected results:
For example, if you want to block 188.8.131.52/16 traffic which is VLAN 710 tagged, you can use the following bpf rule to achieve this:
!((vlan 710) && (src net 184.108.40.206/16 && dst net 220.127.116.11/16))
|Legacy Article ID||a58789|