Associating a Security Level with Assets

Associating assets with security levels in batches: A single security level is associated with multiple assets.

For details, see Calling APIs.

PUT /v3/{project_id}/asset/entities/security-level

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Project ID. For details about how to obtain it, see Project ID and Account ID.

**Table 2** Request header parameters
Parameter	Mandatory	Type	Description
X-Auth-Token	Yes	String	User token. This parameter is mandatory when token authentication is used. You can obtain it from the value of X-Subject-Token in the response message header returned by the "Obtaining a User Token" API of the IAM service.
workspace	Yes	String	Workspace ID. For details about how to obtain it, see Instance ID and Workspace ID.

**Table 3** Request body parameters
Parameter	Mandatory	Type	Description
guids	Yes	Array of strings	Asset GUID.
security_level	Yes	String	Security level

Status code: 400

**Table 4** Response body parameters
Parameter	Type	Description
error_code	String	Error code.
error_msg	String	Error description.

Status code: 401

**Table 5** Response body parameters
Parameter	Type	Description
error_code	String	Error code.
error_msg	String	Error description.

Status code: 403

**Table 6** Response body parameters
Parameter	Type	Description
error_code	String	Error code.
error_msg	String	Error description.

Status code: 404

**Table 7** Response body parameters
Parameter	Type	Description
error_code	String	Error code.
error_msg	String	Error description.

{
  "guids" : [ "a0a555e8-0e52-48ef-a067-bd0a7e255a29", "6a9862e2-62d3-481c-8486-a4c609bca740" ],
  "security_level" : "l1"
}

None

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.