All Products
Search

This Product

    Security Center:AddContainerDefenseRule

    Document Center

    Security Center:AddContainerDefenseRule

    Last Updated:Feb 20, 2024

    Creates a rule for non-image program defense.

    Debugging

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

    Authorization information

    There is currently no authorization information disclosed in the API.

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

    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.

    stringNo

    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.

    stringNo

    The image that needs to be added to the whitelist.

    		repo:tag
    Scopeobject []No

    The scope.

    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.

    stringNo

    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.