Athena NGFW (Next-Generation Firewall)

Athena NGFW (previously known as Network Secure) provides comprehensive protection for every network perimeter, ensuring the safety of your valuable assets, data, and users from emerging threats.
{{ $t('productDocDetail.guideClickSwitch') }}
{{ $t('productDocDetail.know') }}
{{ $t('productDocDetail.dontRemind') }}
8.0.39
{{sendMatomoQuery("Athena NGFW (Next-Generation Firewall)","Botnet")}}

Botnet

{{ $t('productDocDetail.updateTime') }}: 2026-01-07

The botnet is used to discover and isolate PCs infected with viruses, Trojans, and other malicious software in the intranet. When viruses or Trojans try to communicate with external networks, NGAF can recognize the traffic, and then block and log it according to user policies. Its configuration is as follows.

Click Security Policy Template/Botnet to go to the template settings page and add or delete the botnet detection template. Click Add. The Add Template page pops up, as shown below.

 

Template Name: Define the name of the template.

Description: Define the description of the template.

Security Options: Set the attack types to be detected.

Default Detection:
Malicious URL Detection:  Detect the malicious domain. This option enables by default and cannot be disabled.

Malicious Domain Detection: Detect the malicious domain. This option enables by default and cannot be disabled.

Remote Access Trojan: Specify whether to perform remote Trojan detection against data sent by or requested from the protection zone.

Suspicious Traffic: There are two conditions. One is to detect port-protocol mismatches, and the other is to detect outbound traffic. Detected abnormal traffic is only logged but not blocked. Click Settings to select the abnormal traffic to be detected, as shown below.

Outbound Traffic Trigger: It is a heuristic DoS attack detection method covering SYN flood, ICMP flood, DNS flood, and UDP flood attacks with the same source IP address. When outbound packets of these protocols exceed the threshold, the system considers them abnormal traffic and automatically starts packet capture. The detection threshold can be set as follows.

1. Abnormal traffic is only logged but not blocked.

2. In Security Protection Rule Database/Security Rule Database, you can set the action for each botnet rule. Disabled rules will not be rejected.