Configuring TCP Stream Preprocessing
Note | This section applies to Snort 2 preprocessors. For information on Snort 3 inspectors, see https://www.cisco.com/go/snort3-inspectors. |
Before you begin
-
Confirm that networks you want to identify in a custom target-based policy match or are a subset of the networks, zones, and VLANs handled by its parent network analysis policy. See Advanced Settings for Network Analysis Policies for more information.
Procedure
Step 1 | Choose Network Analysis Policy or , then click Network Analysis Policies. , then click
| ||||
Step 2 | Click Snort 2 Version next to the policy you want to edit. | ||||
Step 3 | Click Edit () next to the policy you want to modify. If View () appears instead, the configuration belongs to an ancestor domain, or you do not have permission to modify the configuration. | ||||
Step 4 | Click Settings in the navigation panel on the left. | ||||
Step 5 | If the TCP Stream Configuration setting is disabled under Transport/Network Layer Preprocessors, enable it by clicking Enabled. | ||||
Step 6 | Click Edit () next to TCP Stream Configuration. | ||||
Step 7 | Check or clear the Packet Type Performance Boost check box in the Global Settings section. | ||||
Step 8 | You can:
| ||||
Step 9 | To save changes you made in this policy since the last policy commit, click Policy Information, then click Commit Changes. If you leave the policy without committing changes, cached changes since the last commit are discarded if you edit a different policy. |
What to do next
-
If you want to generate events and, in an inline deployment, drop offending packets, enable TCP Stream preprocessor rules (GID 129). For more information, see Setting Intrusion Rule States and TCP Stream Preprocessing Options.
-
Deploy configuration changes.