All Products
Search

This Product

    Security Center:HandleSecurityEvents

    Document Center

    Security Center:HandleSecurityEvents

    Last Updated:Feb 20, 2024

    Handles alert events.

    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:HandleSecurityEventsRead
    • All Resources
      *
      none
    		none

    Request parameters

    ParameterTypeRequiredDescriptionExample
    SourceIpstringNo

    The source IP address of the request.

    		1.2.XX.XX
    OperationCodestringYes

    The operation that you want to perform to handle the alert events. Valid values:

    • block_ip: blocks the source IP address.
    • advance_mark_mis_info: adds the alert events to the whitelist.
    • ignore: ignores the alert events.
    • manual_handled: marks the alert events as manually handled.
    • kill_process: terminates the malicious process.
    • cleanup: performs in-depth virus detection and removal.
    • kill_and_quara: kills the malicious processes and quarantines the source file.
    • disable_malicious_defense: stops the container on which the alerting files or processes exist.
    • client_problem_check: performs troubleshooting.
    • quara: quarantines the source file of the malicious process.
    		block_ip
    OperationParamsstringNo

    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.
    		{}
    MarkMissParamstringNo

    The whitelist rule. The value of this parameter is in the JSON format and contains the following fields:

    • field: The field based on which alert events are added to the whitelist.

    • operate: The method that is used to added alert events to the whitelist. Valid values:

      • notContains: does not contain
      • contains: contains
      • regex: matches by regular expression
      • strEqual: equals
      • strNotEqual: does not equal

    • fieldValue: The value of the field based on which alert events are added to the whitelist.

    • uuid: The application scope of the whitelist rule. Valid values:

      • part: the current asset
      • ALL: all assets
    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"}]
    MarkBatchstringNo

    Specifies whether to add multiple alert events to the whitelist at a time. Valid values:

    • true: yes
    • false: no
    		true
    SecurityEventIdsarrayYes

    The IDs of the alert events.

    stringYes

    The ID of the alert event.

    		909361
    RemarkstringNo

    The remarks of the handling operation.

    		remark test.

    Response parameters

    ParameterTypeDescriptionExample
    object
    RequestIdstring

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

    		FF0020B9-999F-5DE2-985F-DB282BDA5311
    HandleSecurityEventsResponseobject

    The handling result of the alert events.

    TaskIdlong

    The ID of the task to handle the alert events.

    		15411

    Examples

    Sample success responses

    JSONformat

    {
  "RequestId": "FF0020B9-999F-5DE2-985F-DB282BDA5311",
  "HandleSecurityEventsResponse": {
    "TaskId": 15411
  }
}

    Error codes

    HTTP status codeError codeError messageDescription
    400NoPermissionno permission-
    400SecurityEventNotExistsSecurity event not exists.-
    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