After you enable the feature scenario identification rules, the system identifies the functional scenario (such as login, payment, or data query) to which an API belongs based on its path and parameter characteristics. It then applies a scenario Tag to the corresponding API in the asset list. Using scenario Tags, you can distinguish high-sensitivity, high-risk scenarios from ordinary APIs. The platform provides a set of built-in rules that can identify 12 common functional scenarios by default. These rules are enabled by default and cannot be edited. The platform also supports adding custom rules, allowing you to define scenario names and matching methods according to your business needs.
Enabling System-Built-in Rules
After you enable the feature scenario identification rules on the API Security > Rule Configuration > Feature Scenario Identification Rule page, the system enables the built-in rules by default to apply scenario Tags to your API assets. The built-in rules can be enabled or disabled, but they cannot be edited or deleted. By default, these rules can identify 12 common functional scenarios (such as login, payment, and data query). They are enabled by default and are not editable. Adding Custom Rule
After you enable the feature scenario identification rules, you can customize the feature scenario identification rules according to your business needs. You can also define scenario names and matching methods based on your business requirements.
Note:
A maximum of 20 feature scenario identification rules can be manually added to a single domain.
2. In the Add Rule window, configure the following parameters and click OK to create the rule.
3. After you add a rule, you can edit or delete the corresponding rule.
Configuration Item Description
Scenario Name: Supports custom input, must be unique, and cannot exceed 10 characters.
Condition: At least one condition must be added, and up to five can be added.
|
API name | - | Equal to One of Them Include any Regex match | Enter multiple values separated by carriage return, up to 20 values. |
GET parameter name | - | Equal to One of Them Include any Regex match | Enter multiple values separated by carriage return, up to 20 values. |
GET parameter value | Enter parameter name. | Equal to One of Them Include any Regex match | Enter multiple values separated by carriage return, up to 20 values. |
POST parameter name | - | Equal to One of Them Include any Regex match | Enter multiple values separated by carriage return, up to 20 values. |
POST parameter value | Enter parameter name. | Equal to One of Them Include any Regex match | Enter multiple values separated by carriage return, up to 20 values. |
Cookie parameter name | - | Equal to One of Them Include any Regex match | Enter multiple values separated by carriage return, up to 20 values. |
Cookie parameter value | Enter parameter name. | Equal to One of Them Include any Regex match | Enter multiple values separated by carriage return, up to 20 values. |
Header parameter name | - | Equal to One of Them Include any Regex match | Enter multiple values separated by carriage return, up to 20 values. |
Header parameter value | Enter parameter name. | Equal to One of Them Include any Regex match | Enter multiple values separated by carriage return, up to 20 values. |
Response parameter name | - | Equal to One of Them Include any Regex match | Enter multiple values separated by carriage return, up to 20 values. |
Response parameter value | Enter parameter name. | Equal to One of Them Include any Regex match | Enter multiple values separated by carriage return, up to 20 values. |
On/Off: Controls whether to enable or disable this rule. The default setting is On.