Manage Data Masking with Terraform

• Part 1: Manage Environments with Terraform - Set up environments with policies
• Part 2: Manage Databases with Terraform - Register database instances
• Part 3: Manage Projects with Terraform - Organize databases into projects
• Part 4: Manage Bytebase Settings with Terraform - Configure workspace profile and approval policies
• Part 5: Manage SQL Review Rules with Terraform - Define SQL review policies
• Part 6: Manage Users and Groups with Terraform - Configure users and groups
• Part 7: Manage Database Access Control with Terraform - Grant database permissions
• Part 8: Manage Data Masking with Terraform 👈

​

What You’ll Learn

• Define semantic types with various masking algorithms
• Configure data classification levels and categories
• Create global masking policies that apply workspace-wide
• Set up database-specific column masking
• Grant masking exceptions for specific users

​

Prerequisites

• Completed Part 7: Manage Database Access Control with Terraform
• Bytebase running with service account configured
• Your Terraform files from the previous tutorials

​

Setup

• Database instances and projects configured
• Users and access controls set up
• Production database hr_prod with employee data

​

Understanding Data Masking in Bytebase

• Semantic Types: Define masking algorithms (e.g., full mask, partial mask)
• Classifications: Group data by sensitivity levels (e.g., Level 1, Level 2)

• Classifications define sensitivity levels (Level 1, Level 2, etc.) but cannot mask data by themselves
• Semantic types define the actual masking algorithms (full-mask, range-mask, etc.)

1. Global masking rules: Define workspace-wide rules that map to semantic types
   • Match by column names or patterns → semantic type
   • Match by classification levels → semantic type
2. Column-level masking: Apply directly to specific columns
   • Assign semantic types directly to columns
   • Assign classifications to columns (which then use semantic types via global rules)

​

Configure Data Masking

​

Step 1: Define Semantic Types

resource "bytebase_setting" "semantic_types" {
  name = "settings/SEMANTIC_TYPES"

  semantic_types {
    id    = "full-mask"
    title = "Full mask"
    algorithm {
      full_mask {
        substitution = "***"
      }
    }
  }

  semantic_types {
    id    = "date-year-mask"
    title = "Date year mask"
    algorithm {
      range_mask {
        slices {
          start        = 0
          end          = 4
          substitution = "****"
        }
      }
    }
  }

  semantic_types {
    id    = "name-first-letter-only"
    title = "Name first letter only"
    algorithm {
      inner_outer_mask {
        prefix_len   = 1
        suffix_len   = 0
        substitution = "*"
        type         = "INNER"
      }
    }
  }
}

​

Step 2: Define Data Classification

resource "bytebase_setting" "classification" {
  name = "settings/DATA_CLASSIFICATION"

  classification {
    id    = "classification-example"
    title = "Classification Example"

    levels {
      id    = "1"
      title = "Level 1"
    }
    levels {
      id    = "2"
      title = "Level 2"
    }

    classifications {
      id    = "1"
      title = "Basic"
    }

    classifications {
      id    = "1-1"
      title = "User basic"
      level = "1"
    }

    classifications {
      id    = "1-2"
      title = "User contact info"
      level = "2"
    }

    classifications {
      id    = "2"
      title = "Employment"
    }

    classifications {
      id    = "2-1"
      title = "Employment info"
      level = "2"
    }
  }
}

​

Step 3: Apply Basic Configuration

terraform plan
terraform apply

1. Click Data Access > Semantic Types on the left sidebar. You should see three masking types configured.
2. Click Data Access > Data Classification on the left sidebar. You should see the classification hierarchy with two levels. Note that Level 2 is marked as more sensitive.

​

Step 4: Apply Global Masking Policy

resource "bytebase_policy" "global_masking_policy" {
  depends_on = [
    bytebase_instance.prod,
    bytebase_setting.environments
  ]

  parent              = "workspaces/-"
  type                = "MASKING_RULE"
  enforce             = true
  inherit_from_parent = false

  global_masking_policy {

    rules {
      condition     = "column_name == \"birth_date\""
      id            = "birth-date-mask"
      semantic_type = "date-year-mask"
      title = "Mask Birth Date Year"
    }

    rules {
      condition     = "column_name == \"last_name\""
      id            = "last-name-first-letter-only"
      semantic_type = "name-first-letter-only"
      title = "Last Name Only Show First Letter"
    }

    rules {
      condition     = "classification_level in [\"2\"]"
      id            = "classification-level-2"
      semantic_type = "full-mask"  # Maps Level 2 classification to full-mask semantic type
      title = "Full Mask for Classification Level 2"
    }
  }
}

terraform plan
terraform apply

1. Click Data Access > Global Masking. You should see the global policy with three conditions with corresponding semantic types.
2. Log in as Developer 1 (dev1@example.com), then go to SQL Editor to access hr_prod. Double-click employee table on the left. birth_date has Mask Birth Date Year semantic type, and last_name has Last Name Only Show First Letter. Hovering the eye icon will show the masking reason.

​

Step 5: Apply Column-Specific Masking

• Column from_date is assigned the semantic type date-year-mask
• Column amount is assigned the classification 2-1 (Employment info)

resource "bytebase_database" "database" {
  depends_on = [
    bytebase_instance.prod,
    bytebase_project.project-two,
    bytebase_setting.environments
  ]

  name        = "instances/prod-sample-instance/databases/hr_prod"
  project     = bytebase_project.project-two.name
  environment = bytebase_setting.environments.environment_setting[0].environment[1].name

  catalog {
    schemas {
      name = "public"
      tables {
        name = "salary"
        columns {
          name          = "from_date"
          semantic_type = "date-year-mask"
        }
        columns {
          name          = "amount"
          classification = "2-1"
        }
      }
    }
  }
}

terraform plan
terraform apply

1. Go into Project Two, then click Database > Databases and click hr_prod.
2. Scroll down to find salary table, click it. You should see:
   • amount is assigned as Employment info (Level 2) classification
   • from_date is assigned as date-year-mask semantic type
   
3. Log in as Developer 1 (dev1@example.com), then go to SQL Editor to access hr_prod. Double-click salary table on the left. from_date has Date year mask semantic type, and amount has L2 classification which leads to Full masking semantic type.

​

Step 6: Grant Masking Exceptions

• Workspace Admin (admin@example.com) has Masking Exemptions for birth_date in table employee for Query
• Workspace Admin (admin@example.com) has Masking Exemptions for last_name in table employee for Export

resource "bytebase_policy" "masking_exception_policy" {
  depends_on = [
    bytebase_project.project-two,
    bytebase_instance.prod
  ]

  parent              = bytebase_project.project-two.name
  type                = "MASKING_EXCEPTION"
  enforce             = true
  inherit_from_parent = false

  masking_exception_policy {
    exceptions {
      reason = "Business requirement"
      database = "instances/prod-sample-instance/databases/hr_prod"
      table    = "employee"
      column   = "birth_date"
      member   = "user:admin@example.com"
      action   = "QUERY"
      expire_timestamp = "2027-07-30T16:11:49Z"

    }
    exceptions {
      reason = "Export data for analysis"
      database = "instances/prod-sample-instance/databases/hr_prod"
      table    = "employee"
      column   = "last_name"
      member   = "user:admin@example.com"
      action   = "EXPORT"
      expire_timestamp = "2027-07-30T16:11:49Z"
    }
  }
}

​

Step 7: Apply Final Configuration and Test

terraform plan
terraform apply

1. Log in as Workspace Admin (admin@example.com), then go to SQL Editor to access hr_prod, double-click employee table on the left. You may notice the birth_date is not masked any longer.
2. Click Export, and then open the file. You should notice the birth_date is still masked while last_name is no longer masked.
3. You may go to Manage > Masking Exemptions to view current exemptions. They will expire automatically after the expiration time.

​

Summary

• Semantic Types: Define reusable masking algorithms
• Classification: Organize data by sensitivity levels (requires mapping to semantic types)

• Global Policies: Apply masking rules workspace-wide based on conditions
• Column-Level Masking: Apply semantic types or classifications to specific columns

• Masking Exemption: Grant bypass permissions for specific users to query/export unmasked data

​

Next Steps

• Database instances and environments
• Organized projects
• Risk policies and approval workflows
• SQL review rules for schema standards
• Database access control
• Data masking for sensitive information