MySQL itself does not natively support complete data desensitization and tokenization functions, but can achieve similar effects through built-in functions, views, stored procedures and architecture design. 1. Use built-in functions such as SUBSTRING and CONCAT to perform simple desensitization processing on sensitive fields; 2. Create views to achieve unified desensitization logic, centrally manage without affecting the original data; 3. Use stored procedures or UDF to dynamically control the desensitization method according to user roles; 4. Tokenization recommendations are handled by external services, and MySQL only stores encrypted data or tokens to improve security and scalability.
MySQL itself does not natively support complete data desensitization and tokenization functions like some modern database systems, but similar effects can be achieved through built-in functions, views, stored procedures and reasonable architectural design. If you are processing sensitive data, such as user mobile phone number, ID number, bank card number, etc., these methods can help you effectively protect data privacy.
Use MySQL built-in functions to desensitize basic data
MySQL provides some string processing functions that can be used for simple desensitization. For example, SUBSTRING() , CONCAT() , REPEAT() , etc.
For example, if you are desensitized to your mobile phone number, keep the first 3 and the last 4 digits, and use an asterisk in the middle instead:
SELECT CONCAT(SUBSTRING(phone, 1, 3), '****', SUBSTRING(phone, 8, 4)) AS masked_phone FROM users;
This method is suitable for temporary desensitization during querying and will not modify the original data. But note:
- Only suitable for simple string replacement
- Limited support for complex desensitization needs
- Not suitable for dynamic permission control
Use views to achieve a unified data desensitization layer
If you want the application layer to not care about desensitization logic, you can handle it uniformly by creating views.
For example:
CREATE VIEW safe_users AS
SELECT id,
CONCAT(SUBSTRING(email, 1, 3), '****', SUBSTRING_INDEX(email, '@', -1)) AS masked_email,
CONCAT(SUBSTRING(phone, 1, 3), '****', SUBSTRING(phone, 8, 4)) AS masked_phone
FROM users; In this way, the application only needs to query the view safe_users to see the desensitized data. The benefits are:
- Centralized logic management for easy maintenance
- Multiple views can be created based on different roles
- Does not affect the original data storage
However, the view does not support dynamic judgment of user permissions. If more flexible control is required, it must be processed using stored procedures or combined with application layer.
Use stored procedures or UDF to achieve more flexible desensitization logic
If you need to decide whether to desensitize based on user role dynamically, you can use stored procedures or custom functions (UDFs).
For example, create a function to determine whether the current user has permission to view the original data:
DELIMITER //
CREATE FUNCTION get_masked_phone(phone VARCHAR(20), user_role VARCHAR(50))
RETURNS VARCHAR(20)
DETERMINISTIC
BEGIN
IF user_role = 'admin' THEN
RETURN phone;
ELSE
RETURN CONCAT(SUBSTRING(phone, 1, 3), '****', SUBSTRING(phone, 8, 4));
END IF;
END //
DELIMITER ;Then use in the query:
SELECT get_masked_phone(phone, 'user') AS phone FROM users;
This method is more flexible, but it also needs to be noted:
- Manage permissions and role judgment logic well
- Don't let the desensitization logic be too complicated and affect performance
- It is recommended to combine the application layer for finer granular control
Data tokenization is recommended to use external services to process it
MySQL itself does not support real tokenization. If you need to replace sensitive data with irreversible tokens, it is recommended to use external services, such as:
- Write an intermediate service to generate tokens using Java or Python
- Encrypt the original data and store it, and the application layer is responsible for decryption
- Use Kafka or ETL tools to convert data
MySQL can only store encrypted data or tokens and do not participate in processing. This is safer and easier to scale.
Basically that's it. Although MySQL is not a strong point in data desensitization, it can meet the needs of most scenarios through reasonable design.
The above is the detailed content of MySQL Data Masking and Tokenization Techniques. For more information, please follow other related articles on the PHP Chinese website!
Hot AI Tools
Undress AI Tool
Undress images for free
Undresser.AI Undress
AI-powered app for creating realistic nude photos
AI Clothes Remover
Online AI tool for removing clothes from photos.
Clothoff.io
AI clothes remover
Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!
Hot Article
Hot Tools
Notepad++7.3.1
Easy-to-use and free code editor
SublimeText3 Chinese version
Chinese version, very easy to use
Zend Studio 13.0.1
Powerful PHP integrated development environment
Dreamweaver CS6
Visual web development tools
SublimeText3 Mac version
God-level code editing software (SublimeText3)
Performing logical backups using mysqldump in MySQL
Jul 06, 2025 am 02:55 AM
mysqldump is a common tool for performing logical backups of MySQL databases. It generates SQL files containing CREATE and INSERT statements to rebuild the database. 1. It does not back up the original file, but converts the database structure and content into portable SQL commands; 2. It is suitable for small databases or selective recovery, and is not suitable for fast recovery of TB-level data; 3. Common options include --single-transaction, --databases, --all-databases, --routines, etc.; 4. Use mysql command to import during recovery, and can turn off foreign key checks to improve speed; 5. It is recommended to test backup regularly, use compression, and automatic adjustment.
Calculating Database and Table Sizes in MySQL
Jul 06, 2025 am 02:41 AM
To view the size of the MySQL database and table, you can query the information_schema directly or use the command line tool. 1. Check the entire database size: Execute the SQL statement SELECTtable_schemaAS'Database',SUM(data_length index_length)/1024/1024AS'Size(MB)'FROMinformation_schema.tablesGROUPBYtable_schema; you can get the total size of all databases, or add WHERE conditions to limit the specific database; 2. Check the single table size: use SELECTta
Handling character sets and collations issues in MySQL
Jul 08, 2025 am 02:51 AM
Character set and sorting rules issues are common when cross-platform migration or multi-person development, resulting in garbled code or inconsistent query. There are three core solutions: First, check and unify the character set of database, table, and fields to utf8mb4, view through SHOWCREATEDATABASE/TABLE, and modify it with ALTER statement; second, specify the utf8mb4 character set when the client connects, and set it in connection parameters or execute SETNAMES; third, select the sorting rules reasonably, and recommend using utf8mb4_unicode_ci to ensure the accuracy of comparison and sorting, and specify or modify it through ALTER when building the library and table.
Implementing Transactions and Understanding ACID Properties in MySQL
Jul 08, 2025 am 02:50 AM
MySQL supports transaction processing, and uses the InnoDB storage engine to ensure data consistency and integrity. 1. Transactions are a set of SQL operations, either all succeed or all fail to roll back; 2. ACID attributes include atomicity, consistency, isolation and persistence; 3. The statements that manually control transactions are STARTTRANSACTION, COMMIT and ROLLBACK; 4. The four isolation levels include read not committed, read submitted, repeatable read and serialization; 5. Use transactions correctly to avoid long-term operation, turn off automatic commits, and reasonably handle locks and exceptions. Through these mechanisms, MySQL can achieve high reliability and concurrent control.
Managing Character Sets and Collations in MySQL
Jul 07, 2025 am 01:41 AM
The setting of character sets and collation rules in MySQL is crucial, affecting data storage, query efficiency and consistency. First, the character set determines the storable character range, such as utf8mb4 supports Chinese and emojis; the sorting rules control the character comparison method, such as utf8mb4_unicode_ci is case-sensitive, and utf8mb4_bin is binary comparison. Secondly, the character set can be set at multiple levels of server, database, table, and column. It is recommended to use utf8mb4 and utf8mb4_unicode_ci in a unified manner to avoid conflicts. Furthermore, the garbled code problem is often caused by inconsistent character sets of connections, storage or program terminals, and needs to be checked layer by layer and set uniformly. In addition, character sets should be specified when exporting and importing to prevent conversion errors
Connecting to MySQL Database Using the Command Line Client
Jul 07, 2025 am 01:50 AM
The most direct way to connect to MySQL database is to use the command line client. First enter the mysql-u username -p and enter the password correctly to enter the interactive interface; if you connect to the remote database, you need to add the -h parameter to specify the host address. Secondly, you can directly switch to a specific database or execute SQL files when logging in, such as mysql-u username-p database name or mysql-u username-p database name
Setting up asynchronous primary-replica replication in MySQL
Jul 06, 2025 am 02:52 AM
To set up asynchronous master-slave replication for MySQL, follow these steps: 1. Prepare the master server, enable binary logs and set a unique server-id, create a replication user and record the current log location; 2. Use mysqldump to back up the master library data and import it to the slave server; 3. Configure the server-id and relay-log of the slave server, use the CHANGEMASTER command to connect to the master library and start the replication thread; 4. Check for common problems, such as network, permissions, data consistency and self-increase conflicts, and monitor replication delays. Follow the steps above to ensure that the configuration is completed correctly.
Strategies for MySQL Query Performance Optimization
Jul 13, 2025 am 01:45 AM
MySQL query performance optimization needs to start from the core points, including rational use of indexes, optimization of SQL statements, table structure design and partitioning strategies, and utilization of cache and monitoring tools. 1. Use indexes reasonably: Create indexes on commonly used query fields, avoid full table scanning, pay attention to the combined index order, do not add indexes in low selective fields, and avoid redundant indexes. 2. Optimize SQL queries: Avoid SELECT*, do not use functions in WHERE, reduce subquery nesting, and optimize paging query methods. 3. Table structure design and partitioning: select paradigm or anti-paradigm according to read and write scenarios, select appropriate field types, clean data regularly, and consider horizontal tables to divide tables or partition by time. 4. Utilize cache and monitoring: Use Redis cache to reduce database pressure and enable slow query
