BatchDeleteMaliciousFileWhitelistConfig - Security Center

Deletes whitelist rules for alerts generated for sensitive files that are detected by using the agentless detection feature in batches.

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.

Debug

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:BatchDeleteMaliciousFileWhitelistConfig	delete	All Resources *	none	none

Request parameters

Parameter	Type	Required	Description	Example
ConfigIdList	array	No	The IDs of the whitelist rules. You can call the ListMaliciousFileWhitelistConfigs operation to query the IDs of whitelist rules.
ConfigIdList	long	No	The ID of the whitelist rule.	1

Response parameters

Parameter	Type	Description	Example
	object	BaseResult
Success	boolean	Indicates whether the request was successful. Valid values: true false	true
Code	string	The response code. The status code 200 indicates that the request was successful. Other status codes indicate that the request failed. You can identify the cause of the failure based on the status code.	200
Message	string	The returned message.	successful
RequestId	string	The request ID.	A3D7C47D-3F11-57BB-90E8-E5C20C61****
HttpStatusCode	integer	The HTTP status code. The status code 200 indicates that the request was successful.	200

Examples

Sample success responses

JSONformat

{
  "Success": true,
  "Code": "200",
  "Message": "successful",
  "RequestId": "A3D7C47D-3F11-57BB-90E8-E5C20C61****",
  "HttpStatusCode": 200
}

Error codes

HTTP status code	Error code	Error message	Description
400	NoPermission	no permission	-
400	UnknownError	UnknownError	-
403	NoPermission	caller has no permission	You are not authorized to do this operation.
500	ServerError	ServerError	-

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

Change history

Change time	Summary of changes	Operation
2024-07-02	The Error code has changed	View Change Details