All Products
Search
Document Center

Security Center:HandleSimilarSecurityEvents

Last Updated:Feb 20, 2024

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

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

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.
OperationAccess levelResource typeCondition keyAssociated operation
yundun-sas:HandleSimilarSecurityEventsRead
  • All Resources
    *
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
SourceIpstringNo

The source IP address of the request.

192.168.XX.XX
TaskIdlongYes

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
OperationCodestringYes

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
OperationParamsstringNo

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
  • expireTime: the end time of locking. Unit: milliseconds.
  • Note If you set OperationCode to kill_and_quara, the value of OperationParams must consist of the following fields:
    Note
  • subOperation: the method of detection and removal. Valid values:
  • 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
  • subOperation: the method of detection and removal. Valid values:
  • Note * **quaraFileByMd5andPath**: quarantines the source file of the process.
    {"expireTime":1646208726195}
    MarkMissParamstringNo

    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"}
    RemarkstringNo

    The remark of the operation.

    remark test.

    Response parameters

    ParameterTypeDescriptionExample
    object

    The data returned.

    RequestIdstring

    The ID of the request, which is used to locate and troubleshoot issues.

    A3653911-33A6-5268-8B91-7690471F7AA1

    Examples

    Sample success responses

    JSONformat

    {
      "RequestId": "A3653911-33A6-5268-8B91-7690471F7AA1"
    }

    Error codes

    HTTP status codeError codeError messageDescription
    400DataRetrieveNotFinishedData retrieving not finished yet-
    400IllegalParamIllegal param-
    403NoPermissioncaller has no permissionYou are not authorized to do this operation.
    500ServerErrorServerError-

    For a list of error codes, visit the Service error codes.

    Change history

    Change timeSummary of changesOperation
    2023-06-07The Error code has changed. The request parameters of the API has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      delete Error Codes: 400
    Input ParametersThe request parameters of the API has changed.
      Added Input Parameters: Remark
    2022-08-01The Error code has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      delete Error Codes: 400
    2022-08-01The Error code has changedsee changesets
    Change itemChange content
    Error CodesThe Error code has changed.
      delete Error Codes: 400