Manage data security objects to be published

Operation

Description

Filter

You can perform fuzzy search or batch search using keywords such as object name. You can also perform precise filtering based on object type, change time, publish status, change type, environment change, and more.

• Batch Search: You can click Batch Search, enter the supported search items for each object in the Batch Search dialog box, with a maximum of 1000 entries, separated by line breaks. After clicking OK, the system will perform a precise search and display the found objects in the list below.

• Filter:

  • Publish Status: The publish status includes To Be Published, In Publish, Publish Succeeded, Publish Failed, and Succeeded With Warning. Success with warning indicates that the actual publish succeeded, but the published content does not completely match the imported content, which does not affect the use of the published object, only prompts a threat.

  • Change Type: The change types include Add, Update, and Delete. For descriptions of change types, see change type description.

  • Changer: Only Identification Result and Key type objects support filtering by changer. You can select one or more recent submitters for filtering, and the filter source is from the system.

  • Change Time: You need to select the start date and end date separately for the change time, and the date format is YYYY-MM-DD hh:mm:ss.

  • Environment Change: Indicates whether there has been a change in the current target environment since the last import.

  • File Format: Only Classification objects support filtering by object type. You can select one or more object types at a time, including data classification and data grading.

  • Table Type: Only Identification Result type objects support filtering by table type. You can select one or more table types at a time, including logical dimension table, logical fact table, logical aggregate table, logical tag table, and physical table.

  • Key Type: Only Key type objects support filtering by key type. You can select one or more key types at a time, including hashing key, encryption and decryption key (including AES, DES, 3DES, SM2, SM4, RSA, FPE (FF1)).

Publish

Objects that failed to publish or are to be published can be republished, supporting single and batch publishing. Objects that have been successfully published do not need to be republished.

• Single Publish: Click publish in the operation column of the target object, fill in the publish name in the publish dialog box, with a name length not exceeding 64 characters, and click OK.

• Batch Publish: Select the check box in front of the target object name, or click select all or select all on this page at the bottom of the page. After selecting the target objects, click publish at the bottom of the page. Fill in the publish name in the publish dialog box, with a name length not exceeding 64 characters, and click OK.

  Note

  Selecting all only operates on all objects under the current filter and search conditions; selecting all on this page only operates on objects on the current page.

View Details

You can view the information details of a single object in the current target environment.

Version Comparison

Version comparison is supported only when the change type is Update. Compare the version of the object imported this time (that is, the deployment package from the source environment) with the latest version in the target environment.

Publish Details

You can view basic information, flow verification, and abnormal reminder information in the Publish Details dialog box. Flow verification includes overview verification and permission verification.

• Flow Verification:

  • Dependency Verification:

    • Classification: If the object type is data classification, verify whether the specified data grading and identification features in the data classification being published exist in the target environment.

    • Identification Result: Verify whether the data tables, fields, data classification, and data grading mapped in the identification result being published exist in the target environment.

      Note

      When the table type is a data source table, cross-tenant publishing of the identification result of this table is not supported.

  • Permission Verification:

    • Classification: If the function permission verification configuration in the cross-tenant publishing settings is Verify Operator Permission, verify the operation permission of each object in the current target environment during import. If the function permission verification configuration in the cross-tenant publishing settings is Ignore Permission Verification, skip permission verification.

      Note

      During the publishing process, it is verified whether the members replaced according to the import policy have operation permissions.

    • Identification Result: If the function permission verification configuration in the cross-tenant publishing settings is Verify Operator Permission, verify the operation permission of each object in the current target environment during import. If the function permission verification configuration in the cross-tenant publishing settings is Ignore Permission Verification, skip permission verification.

      Note

      • During the publishing process, it is verified whether the members replaced according to the import policy have operation permissions.

      • During the publishing verification process, if the current target environment import only contains automatic identification results and the import policy is configured to import only manual results, it will be published directly.

    • Key: If the function permission verification configuration in the cross-tenant publishing settings is Verify Operator Permission, verify the operation permission of each object in the current target environment during import. If the function permission verification configuration in the cross-tenant publishing settings is Ignore Permission Verification, skip permission verification.

      Note

      • During the publishing process, it is verified whether the members replaced according to the import policy have operation permissions.

      • During the publishing verification process, if the current target environment import only contains automatic identification results and the import policy is configured to import only manual results, it will be published directly.

  • Existence Verification: Only Key type objects support this verification. Verify whether the published items exist in the current target environment.

  • Key Value: Only Key type objects support this verification. Verify whether the value of the published item is empty in the current target environment. If it is empty, it is recommended to modify it in the security module after publishing.

• Abnormal Reminder: Display the abnormal details of some verification items for you.