All Products
Search
Document Center

Security Center:AddContainerDefenseRule

Last Updated:Nov 25, 2024

Creates a rule for non-image program defense.

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

Request parameters

ParameterTypeRequiredDescriptionExample
RuleIdlongNo

The ID of the rule. You do not need to manually specify the ID.

500018
RuleActionintegerNo

The action that is performed when the rule is hit. Valid values:

  • 1: alert
  • 2: block
1
RuleSwitchintegerNo

The switch of the rule. Valid values:

  • 0: off
  • 1: on
1
RuleNamestringNo

The name of the rule.

auto-test-rule-lt9umq
DescriptionstringNo

The description of the rule.

test-proc-defense
RuleTypeintegerNo

The rule type. Valid values:

  • 2: user-defined rules
Note Only the value 2 is supported.
2
WhitelistobjectNo

The whitelist.

HasharrayNo

The hash values of the files that need to be added to the whitelist.

Note This parameter is not supported.
HashstringNo

The hash value of the file that needs to be added to the whitelist.

hashcode
PatharrayNo

The paths to the files that need to be added to the whitelist.

PathstringNo

The path to the file that needs to be added to the whitelist.

/test/worker.sh
ImagearrayNo

The images that need to be added to the whitelist.

PathstringNo

The image that needs to be added to the whitelist.

repo:tag
Scopearray<object>No

The scope.

ScopeobjectNo
ClusterIdstringNo

The ID of the cluster.

Note You can call the DescribeGroupedContainerInstances operation to query the IDs of clusters.
8e2***75b
AllNamespaceintegerNo

Specifies whether to include all namespaces. Valid values:

  • 0: You can use the Namespaces parameter to specify the namespaces to include.
  • 1: All namespaces are included.
0
NamespacesarrayNo

The namespaces to include.

NamespacestringNo

The namespace to include.

default

Response parameters

ParameterTypeDescriptionExample
object

PlainResult

Datalong

The ID of the rule that is created.

182
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.

There was an error with your request.
RequestIdstring

The request ID.

8C376***AE74FB4
HttpStatusCodeinteger

The HTTP status code that is returned.

200

Examples

Sample success responses

JSONformat

{
  "Data": 182,
  "Success": true,
  "Code": "200",
  "Message": "There was an error with your request.",
  "RequestId": "8C376***AE74FB4",
  "HttpStatusCode": 200
}

Error codes

HTTP status codeError codeError messageDescription
403NoPermissioncaller has no permissionYou are not authorized to do this operation.
500ServerErrorServerError-

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