Previous Topic: Filter GroupsNext Topic: Which Filter Takes Precedence?


Multiple Filters Are Applied Successively

In both passive and active modes, the NBA uses filters to check every IP packet it sees. These are filters that define which communications are captured, blocked or sent to a policy engine for processing.

The NBA supports network filters and application filters. These support the following actions.

Network filter actions

Application filter actions

How Are Filters Applied?

Data packets are filtered as they pass through the NBA. The filters are defined in nbapolicy.xml. In this example, one network filter and two application filters are active. The network and application filters operate to successively narrow down the communications that must be sent to a policy engine for processing. This is the slowest part of the process.

Network filters are always applied first, followed by application filters. For best performance, configure the network filters to decrypt and/or analyze the smallest amount of network data possible for the application filters. In turn, configure the application filters to analyze or monitor the smallest amount of network data for reassembly into files and emails that are sent to a policy engine.

The following steps show how the NBA applies filters to data packets.

  1. A network filter checks data packets for their protocol (TCP or UDP). In this example, the filter action is set to analyze TCP packets. Any UDP packets are ignored and permitted to continue through the NBA without further intervention.
  2. When the NBA detects any TCP packets, it analyzes them to identify the application protocol.
  3. The NBA then applies the appropriate application filter to the packets.

    In this example, the ‘monitor’ and 'prohibit' actions for application filters are not used.

  4. The policy engine, after analyzing the non-SMTP communication, either blocks it or allows it to continue.