Flow-Based Vs Proxy Scanning
Flow-Based Vs Proxy Scanning
Proxy mode relies on Layer 7 redirection. TCP packets must pass from the kernel in
software (slow) data path and bounce up and down between kernel and proxy daemons. At
the same time, proxy tends to buffer data for scanning which may cause latency to
increase.
The layer 7 data packet may need to redirect between different proxies to complete different
UTM features. For example, SSL proxy does traffic decryption and redirect decrypted traffic
to other proxies (HTTP, IMAP, POP3, etc) to do other work.
In Flow mode, network traffic is scanned in the means of raw IP packets. And traffic keeps
going during the scanning, so latency tends to be much lower than proxy. Also because of
flow modes apply to raw network packets, hardware acceleration can be utilized, such as
nTurbo, XG2/XH0 acceleration cards, etc.
!This mode does not rely on precious kernel resources. Instead, memory is the only limiting
factor. So it can scale very well the models. For example, when memory doubles from one
model to another, the throughput and concurrent connections follows.
All UTM features are applied in a single pass. A network packet goes through IPS engine
and all features are applied without duplicated scanning. That's why the throughput of a
single IPS feature is almost the same as IPS+AppCtrl+WCF.
Performance-wise, Flow mode is the uncontested winner, because of its “flow” nature and
its ability to use hardware-acceleration (N-Turbo).
Feature-wise, Flow mode provides two unique features: IPS and Application Control.
But for other traditional UTM features, such as AV, Webfilter, DLP and Antispam, usually
Proxies provide a better feature set, because they can react on the full Layer7 data packet
and take action before the data is forwarded.
Internal
FORTINET
a. AntiVirus
In FOS 5.0, flow mode can only do checksum based AV scanning.
In FOS 5.2, flow modes also take advantage of the power AV engine for virus
scanning. So detection wise, it's almost the same as proxies. But due to the nature of
flow mode scanning, packets keep going, so there _might_ not be "replacement
messages". Indeed IPS engine remembers the infected URLs, so that subsequent
visits trigger "replacement messages" directly. It's not consistent as proxies are.
b. Webfilter
For web filtering, proxies and flow mode provide similar feature set. But for the "safe
search", proxies provide a far better solution. Flow engine does not alter the original
traffic, so what it can do is very limited. For proxies, the original traffic could be
manipulated anyway they can.
For example, HTTP proxy can add necessary HTTP headers so that "safe search" can
be enforced all the time. HTTP proxies also support features such as Google
Enterprise Service control by utilizing the traffic alternation advantage.
c. DLP
Proxies provide document fingerprinting, which is very powerful to match documents
for similarity. For flow mode, only simple pattern match (including regular expression)
and file type match are available.
d. AntiSpam
Similar as DLP, flow mode supports pattern match only. Proxies (POP3/IMAP/SMTP)
have a far more powerful AntiSpam engine which when coupled with FortiGuard
AntiSpam services can be very comprehensive.
Internal www.fortinet.com
FORTINET
4. Comparison Matrix
* Replacement messages will not be sent on a consistent basis. See 3.a for details.
Internal www.fortinet.com