BotManager's Key Feature : The first verification step, Firewall
BotManager uses a multi-layer verification flow — starting with a firewall, followed by filters and policies — to effectively detect and block malicious bots, macro-generated traffic, and unwanted access based on ASN, IP, or country criteria.
BotManager provides a multi-stage verification flow built with firewalls, filters, and policies.
It can proactively detect and block malicious bots and abnormal traffic based on ASN, country, or IP conditions.
he firewall supports blocklists and allowlists for proactive blocking, while filters enable condition combinations and log aggregation.
The system allows flexible, service-specific security configurations.
STCLab continues to advance its technology to ensure fair and reliable user experiences.
BotManager’s Multi-Verification System
BotManager implements a multi-layer verification system to detect malicious bots and macro-generated traffic. When an access request is received, BotManager performs an initial validation through the firewall, followed by detection processes based on user-defined filters and policy configurations.
Application flow of BotManager:
Access Request → Firewall → Filters → Policies
What’s the Difference Between the Firewall and Filters?
The firewall serves as the first security checkpoint for incoming access requests. It supports both blocklists and allowlists, enabling you to proactively block or selectively permit requests based on specific conditions. Supported criteria include ASN, country, and IP.
When a blocklist entry is added, BotManager can proactively block incoming requests without affecting the system itself. If the same value exists in both the blocklist and the allowlist, the allowlist takes precedence.
A firewall is the first security gateway to verify incoming access requests.
The ‘Filter’ feature also allows you to proactively detect and block malicious bots by registering conditions such as specific IPs, countries, or ASNs. Filters are executed sequentially based on their registration order or assigned priority.
Unlike the firewall, filters can combine multiple conditions for more granular control. For example, you can block or allow only specific IPs within a particular country. Another key difference is that the firewall does not collect log data, whereas filters aggregate data. This allows you to choose between the firewall and filters based on your operational needs and optimize how traffic is managed.
Flexible and Customizable Bot Detection Settings
The multi-stage verification flow provided by BotManager — consisting of firewalls, filters, and policies — enables security architectures that can be tailored to each service’s characteristics and risk profile, ranging from simple bot blocking to highly advanced policy configurations. We will continue to enhance BotManager’s technology and product quality to ensure fair and stable user experiences across diverse services.
