Protect Sensitive Data in MySQL with Dynamic Data Masking — No Application Changes Required

Your applications need access to production data—but does every user who accesses those applications need to see every sensitive value?

Join us to see how Dynamic Data Masking in MySQL helps organizations control the exposure of sensitive data in real time, without changing the underlying data or requiring application changes.

We’ll demonstrate how MySQL can dynamically mask data based on the user or active role, allowing different users to run the same queries while seeing only the data they are authorized to see.

We’ll explore practical scenarios including:

• Personally identifiable information (PII), such as SSNs, email addresses, and phone numbers
• Financial, account, and payment-related information
• Employee and customer data
• Confidential or regulated business data
• Analytics and reporting environments where users need useful data without full exposure
• AI and GenAI workloads where sensitive information should be protected before it reaches models or downstream consumers

We’ll also compare Dynamic Data Masking with static data masking, discuss where each approach fits, and demonstrate how centralized masking policies can help reduce sensitive-data exposure while keeping existing applications and queries working.

WER:

WANN:

WO: