Help Center/ Data Security Center/ Best Practices/ How Do I Prevent Personal Sensitive Data From Being Disclosed During Development and Testing?
Updated on 2024-10-31 GMT+08:00

How Do I Prevent Personal Sensitive Data From Being Disclosed During Development and Testing?

Sensitive data refers to information that, if accessed, disclosed, or misused by unauthorized persons, may pose serious risks to individuals or organizations.

  • For individuals, this includes personal information such as ID card numbers, home addresses, employers, and bank card numbers.
  • For enterprises or organizations, sensitive data encompasses core information such as customer data, financial details, technical information, and major decisions.

Huawei Cloud Data Security Center (DSC) can perform static data masking on a large amount of data in one operation based on anonymization rules. Static anonymization is usually used when sensitive data in the production environment needs to be transferred to the development, test, or outside environment. It is applicable to scenarios such as development and test, data sharing, and data research.

Common Causes of Data Breaches

  • Insider leakage
    • Laptops or mobile devices are lost or stolen.
    • Sensitive data or storage is accessed by unauthorized personal
    • Sensitive data is sent, printed, and copied by employees.
    • Sensitive data is accidentally transmitted out.
  • Leakage caused by external attacks
    • Data access is uncontrollable, or there are security vulnerabilities in the data storage system.
    • Improper configurations allow external attacks.
    • Sensitive data or storage is accessed by unauthorized personal

Scenario

Assume that the dsc_bank table in the rsd-dsc-test database stores the information of the following bank employees:

Figure 1 Bank employee information

To identify and mask sensitive data in the table, you need to first identify the sensitive data and generate an identification result report, then mask the identified sensitive data using the Hash masking algorithm SHA256.

Step 1: Purchasing a DSC Professional Edition Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region or project.
  3. In the navigation tree on the left, click . Choose Security & Compliance > Data Security Center .
  4. If you are a first-time user, click Buy DSC.
  5. On the Buy DSC page, select a Region.

    Figure 2 Selecting a region and edition

    To switch a region, select a region from the Region drop-down list. Only one DSC edition can be purchased in a region.

  6. Set Database Expansion Package and OBS Expansion Package.

    Figure 3 Selecting expansion packages
    • One expansion package offers one database instance. RDS and DWS databases, self-built databases on ECSs, DLI, Elasticsearch, and big data on ECSs are supported.
    • One OBS expansion package offers 1 TB (1024 GB) of OBS storage.

  7. Set Required Duration. Select the required duration from one month to three years.

    Figure 4 Setting required duration

    Select Auto-renew to enable the system to renew your service by the purchased period when the service is about to expire.

  8. Click Next.

    If you have any questions about the pricing, click Pricing details.

  9. Confirm the order information and agree to the DSC disclaimer by selecting I have read and agree to the Data Security Center Service Statement and click Pay Now.

    Figure 5 Viewing details

  10. Select a payment method to pay for your order on the displayed page.

Step 2: Identifying Sensitive Data

  1. Log in to the management console.
  2. In the left navigation page, click , and choose Security > Data Security Center.
  3. In the left navigation pane, choose Sensitive Data Identification > Identification Task.
  4. Click Create Task. In the displayed dialog box, configure the basic parameters.

    Table 1 Parameters for creating a sensitive data identification task

    Parameter

    Description

    Example Value

    Task Name

    You can customize the task name.

    The task name must:

    • Contain 4 to 255 characters.
    • Consist of letters, digits, underscores (_), and hyphens (-).
    • Start with a letter.
    • Be unique.

    DSC_Test

    Data Type

    Type of data to be identified. You can select multiple types.

    • OBS: DSC is authorized to access your Huawei Cloud OBS assets and identify sensitive data in the assets. For details about how to add OBS assets, see Adding OBS Assets.
    • Database: DSC identifies sensitive data of authorized database assets. For details about how to authorize database assets, see Authorizing Access to a Database Asset.
    • Big Data: The DSC identifies sensitive data of authorized big data assets. For details about how to authorize big data source assets, see Authorizing Access to Big Data Assets.
    • MRS: DSC identifies sensitive data of authorized MRS assets. For details about authorized MRS assets, see Authorizing Access to Big Data Assets.
    • LTS: DSC will identify sensitive data of authorized LTS assets. For details about how to add a log stream, see Adding a Log Stream.

    Database > rsd-dsc-test

    Identification Template

    You can select a built-in or custom template. DSC displays data by level and category based on the template you select. For details about how to add a template, see Adding an Identification Template.

    Huawei Cloud Data Security Classifying and Grading Template

    Identification Period

    Set the execution policy of the data identification task.

    • Once: The task will be executed once at a specified time.
    • Daily: The task is executed at a fixed time every day.
    • Weekly: The task is executed at a specified time every week.
    • Monthly: The task is executed at a specified time every month.

    Once

    When to Execute

    This parameter is displayed when Identification Period is set to Once.
    • Now: Select the option and click OK, the system executes the data identification task immediately.
    • As scheduled: The task will be executed at a specified time.

    Now

  5. Click OK. The sensitive data identification task list is displayed.

    Figure 6 Sensitive data identification task list

  6. When the status of the identification task changes to Identification completed. Click View Result in the Operation column to go to the result details page.

    Figure 7 Identification result details

    The birthday dates and email addresses are identified as sensitive data, as shown in Figure 7.

  7. Click View Leveling and Details to view the result details.

    Figure 8 Categorizing and leveling results

    Perform operations described in Step 3: Performing Static Data Masking to mask the sensitive data in the Birthday and Email columns of the dsc_bank table in the rsd-dsc-test database.

Step 3: Performing Static Data Masking

DSC allows you to create masking tasks for various data sources such as databases, Elasticsearch, MRS, and Hive. This section describes how to create a static masking task for a database. For details about other masking methods, see the following:

  1. In the left navigation pane, choose Data Asset Protection > Static Data Masking. The Data Masking page is displayed.
  2. Set Mask Sensitive RDS Data to .
  3. Click Create Task to configure the data source.

    Select all data types if you want a complete table that contains all types of data after the data masking is completed.

    Figure 9 Data source configuration

  4. Click Next to switch to Set Masking Algorithm.

    Figure 10 Configuring the data masking algorithm

  5. Click Next to switch to the Configure Data Masking Period page and configure the data masking period.

    Figure 11 Configuring the data masking period

  6. Click Next to the Set Target Data page and configure the storage location of the table generated after data masking.

    Figure 12 Configuring the storage location of the table generated after data masking

  7. Click Finish to return to the database data masking task list. Click to enable the masking task and then Execute in the Operation column to execute the task.

    If the status changes to Completed, the data masking task has been successfully executed.

    Figure 13 Identification and masking completed

Verifying the Result