mysql-data-masking

To mask PII in MySQL without altering stored data, use mask_* and gen_* functions that transform query output on the fly. This ensures sensitive information remains secure in tables while views and reports display compliance-safe results.

Generating synthetic data in Percona Server for MySQL involves installing the masking component, creating the dictionary table, and calling gen_* functions in SQL queries. This produces realistic test data for development and non-production environments.

Yes, you must create the dictionary table first, then install the masking component and apply correct grants. The functions operate on the mysql.masking_dictionaries dictionary, managed via dictionary-admin calls to add or remove terms.

Yes, you can manage masking dictionaries directly using helper functions like masking_dictionary_term_add, masking_dictionary_term_remove, gen_dictionary, and gen_blocklist. These maintain custom terms and blocklists for data masking operations.

Data masking in Percona Server for MySQL works with queries, views, and routines by applying mask_* and gen_* functions. It transforms output without altering stored data, delivering compliance-safe results across non-production environments.

Data masking in MySQL is a tech preview feature, so users should anticipate potential changes. It is designed for development, testing, and non-production environments where realistic test data or compliance-safe results are required.