Who rated this post

Regarding Zero Phishing, Threat Emulation & Threat Extractions:

Small correction (also updated in the SK), Threat Emulation & Threat Extraction, can be boosted by HyperFlow, since they require the MD5 result of files, Zero Phishing on the other hand, does not need it, and hence is not being boosted, nevertheless, connections subject to it, will not stop boosting from occurring for the other supported blades.

Regarding Content Awareness and DLP:

It may be more precise to say, that they potentially decrease the boost, rather than blocking it, the reason is that these blades add more synchronous work to the FW instance, which results in a smaller portion of the work that can be sent to HyperFlow. We are currently not aware of other such blades.

Regarding Dynamic Dispatcher and Priority Queues:

Dynamic Dispatcher is required for Dynamic Balancing to be enabled, and Dynamic Balancing is required for HyperFlow to be enabled.

Disabling Priority Queues does not affect the Evaluator/Eviluator, so it will continue to work regardless.

Regarding Lightspeed and HyperFlow:

Lightspeed is currently supported on R81.10 JHF, while HyperFlow on R81.20.

On R82, and future R81.20 JHF, yes, they will be able to operate together on the same system.

Is there a specific place implying that HyperFlow requires KPPAK? We would want to change it if so.