Handles multiple alert events that are triggered by the same IP address rule or IP address rules of the same type at a time.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
yundun-sas:HandleSimilarSecurityEvents | none | *All Resources * |
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
SourceIp | string | No | The source IP address of the request. | 192.168.XX.XX |
TaskId | long | Yes | The ID of the task that handles the alert events at a time. Note
You can call the CreateSimilarSecurityEventsQueryTask operation to query the IDs of tasks.
| 666038 |
OperationCode | string | Yes | The operation that you want to perform to handle the alert events. Note
You can call the DescribeSecurityEventOperations operation to query the operations.
| offline_handled |
OperationParams | string | No | The configuration of the operation that you want to perform to handle the alert events. The value of this parameter is in the JSON format. Note
If you set OperationCode to kill_and_quara, block_ip, or virus_quara, you must specify OperationParams. If you set OperationCode to other values, you can leave OperationParams empty. If you set OperationCode to block_ip, the value of OperationParams must consist of the following fields:
Note
Note
If you set OperationCode to kill_and_quara, the value of OperationParams must consist of the following fields:
Note
Note
* **killAndQuaraFileByMd5andPath**: terminates the process and quarantines the source file of the process.
* **killByMd5andPath**: terminates the running process.
Note
If you set OperationCode to virus_quara, the value of OperationParams consists of the following fields:
Note
Note
* **quaraFileByMd5andPath**: quarantines the source file of the process.
| {"expireTime":1646208726195} |
MarkMissParam | string | No | The whitelist rule. For example, if you want to add a file that contains the string a to the whitelist based on the MD5 hash value, set this parameter to {"field":"md5","operate":"contains","fieldValue":"aa"}. | {"field":"md5","operate":"contains","fieldValue":"aa"} |
Remark | string | No | The remark of the operation. | remark test. |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "A3653911-33A6-5268-8B91-7690471F7AA1"
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | DataRetrieveNotFinished | Data retrieving not finished yet | - |
400 | IllegalParam | Illegal param | - |
403 | NoPermission | caller has no permission | You are not authorized to do this operation. |
500 | ServerError | ServerError | - |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-09-24 | The Error code has changed | View Change Details |
2024-07-25 | The Error code has changed | View Change Details |
2023-06-07 | The Error code has changed. The request parameters of the API has changed | View Change Details |
2022-08-01 | The Error code has changed | View Change Details |
2022-08-01 | The Error code has changed | View Change Details |