Handles alert events.
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:HandleSecurityEvents | none | *All Resources * |
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
SourceIp | string | No | The source IP address of the request. | 1.2.XX.XX |
OperationCode | string | Yes | The operation that you want to perform to handle the alert events. Valid values:
| block_ip |
OperationParams | string | No | The configuration of the operation that you want to perform to handle the alert events. Note
If you set OperationCode to kill_and_quara or block_ip , you must specify OperationParams. If you set OperationCode to other values, you can leave OperationParams empty.
| {} |
MarkMissParam | string | No | The whitelist rule. The value of this parameter is in the JSON format and contains the following fields:
Note
You can call the DescribeSecurityEventOperations operation to obtain the fields that you can specify for field.
| [{"uuid":"part","field":"gmtModified","operate":"contains","fieldValue":"asd"},{"uuid":"part","field":"loginUser","operate":"contains","fieldValue":"vff"}] |
MarkBatch | string | No | Specifies whether to add multiple alert events to the whitelist at a time. Valid values:
| true |
SecurityEventIds | array | Yes | The IDs of the alert events. | |
string | Yes | The ID of the alert event. | 909361 | |
Remark | string | No | The remarks of the handling operation. | remark test. |
ResourceDirectoryAccountId | long | No | The Alibaba Cloud account ID of the member in the resource directory. Note
You can call the DescribeMonitorAccounts operation to obtain the IDs.
| 16670360956***** |
Response parameters
Examples
Sample success responses
JSON
format
{
"RequestId": "FF0020B9-999F-5DE2-985F-DB282BDA5311",
"HandleSecurityEventsResponse": {
"TaskId": 15411
}
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | NoPermission | no permission | - |
400 | SecurityEventNotExists | Security event not exists. | - |
400 | RdCheckNoPermission | Resource directory account verification has no permission. | - |
403 | NoPermission | caller has no permission | You are not authorized to do this operation. |
500 | RdCheckInnerError | Resource directory account service internal error. | - |
500 | ServerError | ServerError | - |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-06-05 | The Error code has changed. The request parameters of the API has changed | View Change Details |
2023-06-07 | The Error code has changed. The request parameters of the API has changed | View Change Details |