documentation
MBUSTER
Policy Setting
Policy Application Standards

Policy Application Standards Based on Macro Detection Levels

💡 Importance Classification Criteria: Selects the importance based on the accuracy of policies that can clearly detect macros.

  • Essential: A policy that can clearly define as a macro, allowing for immediate blocking operation.
  • Recommended: Policies generally considered macros, but normal users may also be detected due to thresholds, recommended to operate in combination with secondary verification.

Static Analysis

Policy NameImportance
Blocking through Header AnalysisEssential
Blocking through IP ManagementEssential
Blocking through Access Statistics AnalysisRecommended

Dynamic Analysis

CategoryPolicy NameImportance
GeneralBlocking Overseas AccessRecommended
Behavior AnalysisIf excessive URL requests occur from a single user within 1 secondRecommended
If excessive URL requests occur from a single user within 1 minuteRecommended
If excessive URL requests occur from a single user within 1 dayRecommended
Excessive requests for specific URLsRecommended
URL call counts repeat the same pattern every minuteEssential
Multiple personal IDs issued from a single IPRecommended
A single personal ID accessed from multiple IPsEssential
Repeated direct access to specific URLsEssential
Specific actions occurring at an abnormal speedEssential
Access to specific URLs outside set timesRecommended

Macro Detection Policies

MBUSTER's macro detection policies are broadly classified into two categories:

  1. Static Analysis: Techniques for determining the presence of macros at the entry point of MBUSTER API 🔎 Learn more about static analysis policies
  2. Dynamic Analysis: Analyzing user logs based on dynamic behavior analysis ruleset 🔎 Learn more about dynamic analysis policies