Help Center/ Data Security Center/ API Reference/ API Description/ Asset Map/ Updating the Security Protection Policy for Data Assets
Updated on 2026-01-13 GMT+08:00

Updating the Security Protection Policy for Data Assets

Function

This API is used to update the security protection policy of a specified data asset on the asset map. You can locate a specific asset using asset_id and project_id in the URI path, and modify the security policy configuration of the asset using the request body, including dbss_instance_id, enterprise_id, and strategy_type, to ensure that the security protection configuration of data assets meets requirements.

Calling Method

For details, see Calling APIs.

URI

PUT /v2/{project_id}/data-map/data-infos/{asset_id}/security-strategies

Table 1 Path Parameters

Parameter

Mandatory

Type

Description

asset_id

Yes

String

Asset ID, which is used to identify an asset.

project_id

Yes

String

Project ID, which is used to identify a specific project.

Request Parameters

Table 2 Request body parameters

Parameter

Mandatory

Type

Description

dbss_instance_id

No

String

DBSS instance ID.

enterprise_id

No

String

Enterprise ID.

strategy_type

No

String

Policy type.

Response Parameters

Status code: 200

Table 3 Response body parameters

Parameter

Type

Description

id

String

Unique ID of the response.

msg

String

Response message.

status

String

Response status.

Status code: 201

Security policy created.

Example Requests

This API is used to update the security protection policy of a specified data asset on the asset map. You can modify the security policy of an asset based on the asset ID and project ID, including the DBSS instance ID, enterprise ID, and policy type, to ensure asset security.

/v2/{project_id}/data-map/data-infos/{asset_id}/security-strategies

{
  "dbss_instance_id" : "string",
  "enterprise_id" : "string",
  "strategy_type" : "string"
}

Example Responses

None

Status Codes

Status Code

Description

200

Security policy updated.

201

Security policy created.

401

Unauthorized. The user is not logged in or the token is invalid.

403

Unauthorized to access the resource.

404

The specified asset or project does not exist.

Error Codes

See Error Codes.