Help Center/ Edge Security/ API Reference/ API/ HTTP Protection Rule Management - Attack Penalty/ Creating a Known Attack Source Rule.

Updated on 2024-11-18 GMT+08:00

View PDF

Creating a Known Attack Source Rule.

Function

This API is used to create a known attack source rule.

URI

POST /v1/edgesec/configuration/http/policies/{policy_id}/punishment-rule

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
policy_id	Yes	String	Policy ID.

Request Parameters

**Table 2** Request header parameters
Parameter	Mandatory	Type	Description
X-Auth-Token	Yes	String	auth token

**Table 3** Request body parameters
Parameter	Mandatory	Type	Description
description	No	String	Rule description, which contains a maximum of 512 characters.
category	Yes	String	Blocking type. The options are as follows: long_ip_block (long-time IP address blocking), long_cookie_block (long-time cookie blocking), long_params_block (long-time parameter blocking), and short_ip_block (short-time IP address blocking). short_cookie_block (short-time cookie blocking) and short_params_block (short-time parameter blocking)
block_time	Yes	Integer	Blocking duration. If the prefix of the attack penalty type is long, the value range of block_time is 301-1800. If the prefix of the attack penalty type is short, the value range of block_time is 0-300.

Response Parameters

Status code: 200

**Table 4** Response body parameters
Parameter	Type	Description
id	String	Rule ID
policy_id	String	ID of the policy to which the rule belongs
timestamp	Long	Time when a rule is created
description	String	Rule description
category	String	Blocking type. The options are as follows: long_ip_block (long-time IP address blocking), long_cookie_block (long-time cookie blocking), long_params_block (long-time parameter blocking), and short_ip_block (short-time IP address blocking). short_cookie_block (short-time cookie blocking) and short_params_block (short-time parameter blocking)
block_time	Integer	Blocking duration.

Status code: 400

**Table 5** Response body parameters
Parameter	Type	Description
error_code	String	Standard error code: service name.8-digit code
error_msg	String	Detailed error information.
encoded_authorization_message	String	If the service is integrated with IAM5.0, an IAM response must be returned when access is denied.

Status code: 401

**Table 6** Response body parameters
Parameter	Type	Description
error_code	String	Standard error code: service name.8-digit code
error_msg	String	Detailed error information.
encoded_authorization_message	String	If the service is integrated with IAM5.0, an IAM response must be returned when access is denied.

Status code: 500

**Table 7** Response body parameters
Parameter	Type	Description
error_code	String	Standard error code: service name.8-digit code
error_msg	String	Detailed error information.
encoded_authorization_message	String	If the service is integrated with IAM5.0, an IAM response must be returned when access is denied.

Example Requests

None

Example Responses

None

Status Codes

Status Code	Description
200	OK
400	Request failed.
401	The token does not have required permissions.
500	Internal server error.

Error Codes

See Error Codes.

Parent topic: HTTP Protection Rule Management - Attack Penalty

Previous topic: Querying Known Attack Source Rules

Next topic: Querying a Penalty Rule

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.