All Products
Search
Document Center

Security Center:OperateVirusEvents

Last Updated:Nov 13, 2024

Handles alert events that are generated by the antivirus feature. You can perform in-depth detection and removal, add alert events to the whitelist, ignore alert events, or manually handle alert events.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

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

Request parameters

ParameterTypeRequiredDescriptionExample
OperationCodestringYes

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

  • default: performs in-depth detection and removal
  • ignore: ignores the alert event
  • advance_mark_mis_info: adds the alert events to the whitelist
  • manual_handled: marks the alert events as manually handled
default
OperationRangestringNo

The handling scope.

[{\"type\":\"machine\",\"list\":[\"xxxxxxxxx-4cbf-4ca6-a1b7-8a09d1f86ab0\"]}]
OperationAllintegerYes

Specifies whether to handle all alert events. Valid values:

  • 1: yes
  • 0: no
0

Response parameters

ParameterTypeDescriptionExample
object
TaskIdlong

The ID of the task to handle multiple alert events at a time.

1
RequestIdstring

The ID of the request.

B72BEC03-001C-5C77-A4BB-1E6XXXXXXX

Examples

Sample success responses

JSONformat

{
  "TaskId": 1,
  "RequestId": "B72BEC03-001C-5C77-A4BB-1E6XXXXXXX"
}

Error codes

HTTP status codeError codeError messageDescription
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
No change history