Differences

This shows you the differences between two versions of the page.

--- infoblox_threat_defense:applications [2025/02/14 20:24] – bstafford
+++ infoblox_threat_defense:applications [2025/03/03 15:57] (current) – bstafford
@@ Line 1: / Line 1: @@
 ====== Infoblox Applications ======
 ===== Allow - Local Resolution =====
 NIOS-X with DFP and Infoblox Endpoint can honour "Allow - Local Resolution" for Application Custom List on Security Policy. DFP MUST have a fallback resolver configured. This is because the list of applications isn't put into the DNS config file but the DFP config file and the DFP can't send the query back to the DNS server. So to honour "Allow - Local Resolution", the DFP must have a DNS server it can forward to (i.e. the fallback resolver)
+Infoblox Endpoint can also honour this setting.
 NIOS cannot honour this setting and ignores it.
@@ Line 8: / Line 11: @@
 External Networks cannot honour this setting and ignores it.
+Note: When you configure a rule in a security policy for an application based custom filter with action set to "Allow - Local Resolution", then its position in the security policy makes no different when it is implemented by NIOS-X and/or Infoblox Endpoint. This is because NIOS-X and Endpoint will apply the "Local Resolution" policy locally before the query can reach the cloud based security policy. Any application "block" action will only apply that action once it reaches the cloud. There is no "Block Locally" option because anything that isn't explicitly told to resolve locally will go to cloud.
 ===== Application Domains =====
 Infoblox Threat Defense (cloud) can identify application usage. You can find out the exact domains but configuring "Allow - Local Resolution" for an application custom list in a security policy, apply to an endpoint and then look at the corefile.4 config.