GetMaliciousFileWhitelistConfig - Query sensitive file alert whitelist rule - Security Center

Queries the configuration of a sensitive file alert whitelist rule in agentless detection.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

yundun-sas:GetMaliciousFileWhitelistConfig

get

*MaliciousFileWhitelistConfig

acs:yundun-sas:{#regionId}:{#accountId}:maliciousfilewhitelistconfig/{#ConfigId}

None

Request parameters

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

Response elements

Element	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 alert name. Fixed value: ALL, indicating all alert types.	ALL
Field	string	The field used in the whitelist rule.	fileMd5
FieldValue	string	The value of the field used in the whitelist rule.	b2cf9747ee49d8d9b105cf16e078cc16
Operator	string	The logical operator used in the whitelist rule. Fixed value: strEqual (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 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 Returned only when TargetType is SELECTION_KEY.	0
Source	string	The feature to which this operation belongs. Fixed value: agentless.	agentless
Id	integer	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. 200 indicates success. Other codes indicate failure.	200
Message	string	The returned message.	successful
RequestId	string	The request ID.	F8B6F758-BCD4-597A-8A2C-DA5A552C****
HttpStatusCode	integer	The HTTP status code. 200 indicates success.	200

Examples

Success response

JSON format

{
  "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
500	ServerError	ServerError
403	NoPermission	caller has no permission	You are not authorized to do this operation.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.