GetMaliciousFileWhitelistConfig - Security Center - Alibaba Cloud Documentation Center

Queries an alert whitelist rule of sensitive files that are detected by using the agentless detection feature.

Debugging

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

Debug

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

Parameter	Type	Required	Description	Example
ConfigId	long	No	The ID of the whitelist rule.	1

Response parameters

Parameter	Type	Description	Example
	object	PlainResult
Data	object	The response parameters.
GmtCreate	string	The creation time.	1671607025000
GmtModified	string	The modification time.	1674095396000
EventName	string	The name of the alert. The value is fixed as ALL, which indicates all alert types.	ALL
Field	string	The field that is used in the whitelist rule.	fileMd5
FieldValue	string	The value of the field that is used in the whitelist rule.	b2cf9747ee49d8d9b105cf16e078cc16
Operator	string	The logical operator that is used in the whitelist rule. The value is fixed as strEqual, which indicates the equality operator (=).	strEqual
TargetValue	string	The assets on which the whitelist rule takes effect. Valid values: ALL: all assets Others: selected assets	ALL
TargetType	string	The type of the assets on which the whitelist rule takes effect. Valid values: ALL: all assets SELECTION_KEY: selected assets	ALL
Count	string	The number of assets on which the whitelist rule takes effect. Note The value of this parameter is returned only if the value of TargetType is SELECTION_KEY.	0
Source	string	The feature to which this operation belongs. The value is fixed as agentless, which indicates the agentless detection feature.	agentless
Id	long	The ID of the whitelist rule.	1
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.	F8B6F758-BCD4-597A-8A2C-DA5A552C****
HttpStatusCode	integer	The HTTP status code. The value 200 indicates that the request was successful.	200

Examples

Sample success responses

JSONformat

{
  "Data": {
    "GmtCreate": "1671607025000",
    "GmtModified": "1674095396000",
    "EventName": "ALL",
    "Field": "fileMd5",
    "FieldValue": "b2cf9747ee49d8d9b105cf16e078cc16",
    "Operator": "strEqual",
    "TargetValue": "ALL",
    "TargetType": "ALL",
    "Count": "0",
    "Source": "agentless",
    "Id": 1
  },
  "Success": true,
  "Code": "200",
  "Message": "successful",
  "RequestId": "F8B6F758-BCD4-597A-8A2C-DA5A552C****",
  "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-01-31

The Error code has changed

see changesets

Change item	Change content
Error Codes	The Error code has changed.
	delete Error Codes: 400
	delete Error Codes: 500