GDPR pseudonymisation rules and data masking policies for sensitive columns.
## Overview The Data Protection page provides a centralized interface for defining, applying, and monitoring GDPR pseudonymisation rules across all catalog tables. Data stewards and compliance officers use this page to enforce column-level masking policies that protect personally identifiable information (PII) and other sensitive data before it reaches downstream consumers. Policies created here operate at the column level, allowing fine-grained control over which fields are masked and what transform type is applied. The page also surfaces real-time policy status so administrators can verify that all required protections are active and correctly configured. ## Key Features - **Pseudonymisation rule management.** Create, edit, enable, and disable pseudonymisation rules that target specific columns in Delta Lake tables. Each rule binds a source column to a transform type and an output behavior. - **Column-level masking policies.** Assign masking policies to individual columns rather than entire tables. This preserves analytical utility on non-sensitive fields while protecting PII columns. - **Transform type selection.** Choose from built-in transform types such as hashing, tokenization, redaction, and format-preserving encryption. Each transform type documents its reversibility and data-type compatibility. - **Policy status monitoring.** View a dashboard of all active and inactive policies with their last-evaluated timestamps. Filter by zone, schema, or table to audit coverage and identify columns that lack protection. ## Workflow 1. Navigate to the Data Protection page from the Catalog sidebar. 2. Select the target zone, schema, and table containing sensitive columns. 3. Choose one or more columns and assign a pseudonymisation rule by selecting a transform type. 4. Configure rule parameters (salt, key reference, output format) as required by the chosen transform. 5. Enable the rule and verify its status in the policy monitoring panel. 6. Periodically review the policy dashboard to confirm all PII columns remain covered after schema changes.