In addition to the predefined threat intelligence feeds that your subscription offers, you can create custom lists (containing domains and IP addresses) to define allow lists and block lists for additional protection. You can use a custom list to complement existing feeds or override the Block, Allow, Log, or Redirect action that is currently defined for an existing feed. The default custom list configuration also includes Allow - No Log for for the custom allow list and Block with Log for for the custom block list. These lists are included in the default policy for new and existing customers and allow the editing of domains, IP addresses, and tags. When using your own threat intelligence feeds with BloxOne Threat Defense Cloud, allow lists and block lists, you can apply your own security policies. Each custom list can contain as many as 50,000 records, and BloxOne Thread Defense Cloud supports up to 500,000 records across al customer lists
Default Custom Lists
- Default Allow: The default allow list enables only allow actions with no logging (Allow - No Log). All types of allow related actions can be used with the default allow list. Organizations can change the default order of the allow list and can also edit the list of domains, IP addresses, and tags on the custom allow list.
- Default Block: The default block list enables block actions with logging (Block with Log). All types of block related actions can be used with the default block list. Organizations can change the default order of the block list and can also edit the list of domains, IP addresses, and tags on the custom block list.
You can add a custom list to multiple security policies or multiple custom lists to one security policy based on your business needs. When you assign multiple custom lists that contain the same domain name(s) but with different actions to the same security policy, BloxOne Threat Defense Cloud takes actions based on the following order:
...
- Threat Insight – Data Exfiltration: The default action for this policy is Log. This list helps minimize the risk of DNS data exfiltration that are brought upon your networks through DNS tunneling.
- Threat Insight - Notional Data Exfiltration: Threat Insight - Notional Data Exfiltration is part of the default feed and will be listed below Threat Insight - Data Exfiltration. (For existing customers to be aware and take advantage of this new Threat Insight - it will be automatically enabled and displayed below Threat Insight - Data Exfiltration, if that’s already enabled in existing policy). This list includes low confidence DNS Tunnel detections. The default action for this policy is Allow with Log. Ideally, only high confidence DNS Tunnel detections should be of interest and blocked, which are listed in the existing Threat Insight - Data Exfiltration list. However, there are cases where you may want to be informed of even lower confidence tunnels in your network. This Notional Data Exfiltration Threat Insight list addresses those cases. These are just suggestions for tunnel activity (hence, Notional) and not confident enough to be added to the original Threat Insight - Data Exfiltration list. Customers can also change the default action of this Notional list to Block based on the organization's sensitivity to these low confidence DNS tunnels.
Threat Insight - Notional Data Exfiltration is part of the default feed and will be listed below Threat Insight - Data Exfiltration. (For existing customers to be aware and take advantage of this new Threat Insight - it will be automatically enabled and displayed below Threat Insight - Data Exfiltration, if that’s already enabled in existing policy)
- Threat Insight – DNS Messenger: The default action for this policy is Log. This list helps minimize the risk of malicious activities that are brought upon your networks through the DNSMessenger malware, a Remote Access Trojan (RAT), that attackers use to conduct malicious Powershell commands on compromised devices.
- Threat Insight – Fast Flux: The default action for this policy is Log. This list helps minimize the risk of malicious activities that are brought upon your networks using the Fast Flux technique. Fast Flux is a DNS technique used by botnets to hide phishing and malware delivery sites behind a network of compromised hosts acting as proxies. It can also be a combination of peer-to-peer networking, distributed command and control, web-based load balancing and proxy redirection used to make malware networks more resistant to discovery.
- Threat Insight – DGA: The default action for this policy is Log. This list helps minimize the risk of malicious activities that are brought upon your networks using the Domain Generation Algorithm (DGA). DGA is a scheme used by malwares for domain fluxing by generating variations of a given domain name. They can be used to create a large number of domain names used as rendezvous points with command and control servers, in an attempt to evade detection by signature filters, block lists, reputation systems, security gateways, intrusion prevention systems, and other security methods.
...