infoblox_threat_defense:custom_lists
Differences
This shows you the differences between two versions of the page.
| infoblox_threat_defense:custom_lists [2024/12/27 15:08] – created bstafford | infoblox_threat_defense:custom_lists [2025/03/21 15:15] (current) – bstafford | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| However, cache means that you might need to wait a little while for all queries to get blocked. | However, cache means that you might need to wait a little while for all queries to get blocked. | ||
| - | For comparison, on NIOS RPZ, you would need example.co.uk and *.example.co.uk | + | For comparison, on NIOS RPZ, you would need example.co.uk and *.example.co.uk. |
| + | |||
| + | For Infoblox Threat Defense cloud, you cannot actualy set *.example.co.uk. If you try and save, when you re-open the custom list you will see that the product has removed the *. from the domain. | ||
| If you put a subdomain in an allow list and you put the parent domain in a block list, then the subdomain will resolve if, and only if, the allow list is further up the security policy rules than the block list. | If you put a subdomain in an allow list and you put the parent domain in a block list, then the subdomain will resolve if, and only if, the allow list is further up the security policy rules than the block list. | ||
infoblox_threat_defense/custom_lists.1735312085.txt.gz · Last modified: by bstafford