All Products
Search
Document Center

Security Center:GetMaliciousFileWhitelistConfig

Last Updated:Nov 13, 2024

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

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

Request parameters

ParameterTypeRequiredDescriptionExample
ConfigIdlongNo

The ID of the whitelist rule.

1

Response parameters

ParameterTypeDescriptionExample
object

PlainResult

Dataobject

The response parameters.

GmtCreatestring

The creation time.

1671607025000
GmtModifiedstring

The modification time.

1674095396000
EventNamestring

The name of the alert.

  • The value is fixed as ALL, which indicates all alert types.
ALL
Fieldstring

The field that is used in the whitelist rule.

fileMd5
FieldValuestring

The value of the field that is used in the whitelist rule.

b2cf9747ee49d8d9b105cf16e078cc16
Operatorstring

The logical operator that is used in the whitelist rule.

  • The value is fixed as strEqual, which indicates the equality operator (=).
strEqual
TargetValuestring

The assets on which the whitelist rule takes effect. Valid values:

  • ALL: all assets
  • Others: selected assets
ALL
TargetTypestring

The type of the assets on which the whitelist rule takes effect. Valid values:

  • ALL: all assets
  • SELECTION_KEY: selected assets
ALL
Countstring

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
Sourcestring

The feature to which this operation belongs.

  • The value is fixed as agentless, which indicates the agentless detection feature.
agentless
Idlong

The ID of the whitelist rule.

1
Successboolean

Indicates whether the request was successful. Valid values:

  • true
  • false
true
Codestring

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
Messagestring

The returned message.

successful
RequestIdstring

The request ID.

F8B6F758-BCD4-597A-8A2C-DA5A552C****
HttpStatusCodeinteger

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 codeError codeError messageDescription
400NoPermissionno permission-
400UnknownErrorUnknownError-
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
2024-01-31The Error code has changedView Change Details