Practical tips for streamlining bot-policy operations by quickly filtering abnormal requests with custom filters tailored to your service characteristics and traffic patterns.
BotManager’s Filters act as pre-filters that screen requests before bot-detection policies run.
Admins can define conditions such as IP, ASN, Query String, or User-Agent to selectively block or allow traffic.
Filtering unnecessary requests early improves detection efficiency and response speed.
Requests caught by Filters are not classified as bots but aggregated as filter-level statistics.
This approach optimizes bot-management workflows and produces more meaningful detection results.
STCLab offers its solution to the market under the name BotManager, a bot-management product that can be easily installed and applied in SaaS environments.
BotManager classifies and evaluates bot (macro) traffic, which appears alongside normal users in various forms, based on predefined policies. It then controls access when necessary. By using BotManager, organizations can protect users from unfair transactions while eliminating unnecessary traffic to improve overall system performance efficiency.
How BotManager’s Filters Improve Accuracy and Response Speed
“Filters” are pre-filters that selectively screen incoming requests before BotManager policies are applied. Administrators can define their own conditions and execute detection or blocking actions selectively based on the attributes of each request.
Admins can filter requests to boost detection efficiency and response speed.
Filters are executed sequentially according to their registration order or assigned priority values. If a condition is met by an upper filter, the lower filters are not executed. Requests detected by a Filter are not classified as bots, and instead of individual logs, they are aggregated as filter-level statistical data.
Sample Scenario#1 : Blocking a specific IP
Condition: IP / Equals / 12.184.233.77
Effect: Requests from 12.184.233.77 are filtered before any bot policies are applied.
Sample Scenario#2 : Filter requests with an empty query string
Condition: Query String / Matches / is_empty
Effect: Only requests without a query string are passed to detection and blocking policies.
*Key Filter Items
IP Country AS ASN HTTP Method Query String User Agent JA3 / JA4 Fingerprint Accept / Accept-Encoding / Accept-Language / CacheControl / ContentType Header Protocol Referrer
BotManager Filter Creation Screen
Beyond the preconfigured policies, you can refine detection logic to match your service characteristics and traffic patterns, quickly filtering out unnecessary requests to improve policy efficiency and response speed. Filters help optimize bot-management operations and deliver more meaningful outcomes.
BotManager is always striving for better optimization and efficiency.
