Data security objects pending deployment-Dataphin(Dataphin)-阿里云帮助中心

If an imported release package contains changes to data security objects, these objects are listed on the data security page. You can then manage and deploy them from this page.

Access the data security page

Log in to Dataphin as a cross-tenant deployment user.
On the Dataphin homepage, choose management center > cross-tenant deployment from the top navigation bar.
In the left-side navigation pane, choose cross-tenant deployment > import a release package.
Click the Deploy icon in the Actions column for the desired release package.
Click the data security tab to open the page for data security objects pending deployment.

Manage data security objects

After a release package is successfully imported, you can filter, deploy, view details, or compare versions of classification and grading, identification result, and key objects on the Global tab. The available actions differ slightly for each object type.

Note

The Data Standard and data security modules share the same identification feature configurations. You must deploy identification features in the Global category.
The Data Standard module has dependencies on other modules, such as Quality. We recommend deploying objects in the order suggested in the Instructions section at the top-right of the page. For more information about the deployment order for a release package, see Suggested deployment order.

Actions	Description
Filter	You can perform a fuzzy search by keywords such as object name, use batch search, or filter by criteria such as object type, modification time, deployment status, change type, and environment change. Batch search: Click batch search. In the Batch Search dialog box, enter the search terms for the objects. You can enter up to 1,000 terms, separated by line breaks. After you click OK, the system performs an exact match search and displays the results in the list. Filter: Deployment status: The deployment status can be pending deployment, queued, deploying, succeeded, failed, or succeeded with risks. The queued status indicates the object is in the deployment queue, awaiting deployment. The succeeded with risks status means the deployment was successful, but the deployed content does not exactly match the imported content. This indicates a risk but does not affect the object's functionality. Change type: The change type can be addition, update, or deletion. For more information, see Change type descriptions. Modifier: You can filter only identification result and key objects by modifier. You can select one or more recent submitters from the list. Modification time: Select a start and end date and time. The format is YYYY-MM-DD hh:mm:ss. Environment change: Indicates whether the target environment has changed since the last import. Object type: You can filter only classification and grading objects by object type. You can select one or more object types, such as data category and data sensitivity level. Table type: You can filter only identification result objects by table type. You can select one or more table types. The available types are dimension logical table, fact logical table, summary logical table, tag logical table, and physical table. Key type: You can filter only key objects by key type. You can select one or more key types. The available types include hash desensitization key and encryption/decryption key, which supports algorithms such as AES, DES, 3DES, SM2, SM4, RSA, and FPE (FF1).
Deploy	You can redeploy objects that have a failed or pending deployment status. Both single and batch deployments are supported. Succeeded objects do not require redeployment. Single deployment: In the Actions column for the target object, click Deploy. In the dialog box that appears, enter a deployment name (up to 64 characters) and click OK. Batch deployment: Select the checkboxes next to the target objects, or click Select All or Select Current Page at the bottom of the page. After selecting the objects, click Deploy at the bottom. In the dialog box that appears, enter a deployment name (up to 64 characters) and click OK. Note Select All applies to all objects that match the current filter and search criteria. Select Current Page applies only to the objects on the current page.
View details	View detailed information about an object in the target environment. Note If the change type is deletion and the deployment status is succeeded, the object no longer exists and you cannot view its details.
Version comparison	Version comparison is available only when the change type is update. It compares the object version from the imported release package (from the source environment) with the latest version in the target environment.
Deployment details	In the Deployment Details dialog box, you can view basic information, process check results, and exception alerts. Process checks include dependency and permission checks. Process check: Dependency check: Classification and grading: If the object is a data category, the system checks whether the specified data sensitivity level and identification features for that category exist in the target environment. Identification result: The system checks whether the data table, field, data category, and data sensitivity level mapped in the identification result exist in the target environment. Note Cross-tenant deployment of identification results is not supported for tables of the data source table type. Permission check: Classification and grading: If the function permission check in the cross-tenant deployment settings is set to Validate operator permissions, the system checks the operator's permissions for each object in the target environment during import. If the setting is Ignore permission check, this check is skipped. Note During the deployment process, the system validates the permissions of the members who have been substituted based on the import policy. Identification result: If the function permission check in the cross-tenant deployment settings is set to Validate operator permissions, the system checks the operator's permissions for each object in the target environment during import. If the setting is Ignore permission check, this check is skipped. Note During the deployment process, the system validates the permissions of the members who have been substituted based on the import policy. During the pre-deployment check, if the imported objects for the target environment contain only automatically generated identification results and the import policy is configured to import only manual results, the deployment succeeds immediately. Key: If the function permission check in the cross-tenant deployment settings is set to Validate operator permissions, the system checks the operator's permissions for each object in the target environment during import. If the setting is Ignore permission check, this check is skipped. Note During the deployment process, the system validates the permissions of the members who have been substituted based on the import policy. During the pre-deployment check, if the imported objects for the target environment contain only automatically generated identification results and the import policy is configured to import only manual results, the deployment succeeds immediately. Existence check: This check is supported only for key objects. It verifies whether the item to be deployed already exists in the target environment. Key value: This check is supported only for key objects. It verifies that the key value to be deployed is not empty. If the value is empty, we recommend modifying it in the security module after deployment. Exception alerts: Displays the details of any exceptions found during the checks.