All Products
Search
Document Center

Security Center:OperationSuspEvents

Last Updated:Nov 13, 2024

Handles multiple exceptions at a time.

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

Request parameters

ParameterTypeRequiredDescriptionExample
SourceIpstringNo

The source IP address of the request.

1.2.XX.XX
SuspiciousEventIdsstringYes

The IDs of alert events.

Note You can call the DescribeSuspEvents operation to obtain the IDs of alert events from the SecurityEventIds response parameter.
290852
OperationstringYes

The operation that you want to perform on alerts. Valid values:

  • deal: quarantines the source file of the malicious process.
  • ignore: ignores the alerts.
  • mark_mis_info: marks the alerts as false positives by adding the alerts to the whitelist.
  • rm_mark_mis_info: cancels false positives by removing the alerts from the whitelist.
  • offline_handled: marks the alerts as handled.
deal
SubOperationstringNo

The suboperation that you want to perform when you quarantine the source file of the malicious process. Valid values:

  • killAndQuaraFileByPidAndMd5andPath: terminates the process based on its process ID (PID) and quarantines the source file of the process.
  • quaraFileByMd5andPath: quarantines the source file of the process.
  • killAndQuaraFileByMd5andPath: terminates the process and quarantines the source file of the process.
killAndQuaraFileByPidAndMd5andPath
FromstringNo

The ID of the request source.

Set the value to sas, which indicates that the request is sent from Security Center.

sas
WarnTypestringNo

The type of the exceptions. Valid values:

  • alarm: alerts
  • null: exceptions
alarm

Response parameters

ParameterTypeDescriptionExample
object

The response parameters.

Successboolean

Indicates whether exceptions are handled. Valid values:

  • true: yes
  • false: no
true
RequestIdstring

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

7E0618A9-D5EF-4220-9471-C42B5E92719F
AccessCodestring

Indicates whether you have access permissions. Valid values:

  • pass: yes
  • no_permission: no
pass

Examples

Sample success responses

JSONformat

{
  "Success": true,
  "RequestId": "7E0618A9-D5EF-4220-9471-C42B5E92719F",
  "AccessCode": "pass"
}

Error codes

HTTP status codeError codeError messageDescription
400ClientOfflineClient offline-
400UnknownErrorUnknownError-
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
2022-08-01The Error code has changedView Change Details
2022-08-01The Error code has changedView Change Details