Sandbox data masking and anonymization
Key Takeaway
Create and manage Data Mask & Seed masking policies once, in production. They run automatically in target sandboxes after each refresh, so the rules stay in one place and you don't rebuild the protection for copied PII after a refresh.
Sandboxes often hold copies of production data. More people usually get sandbox access than production access, for example developers, contractors, and trainers. Data masking replaces or removes sensitive values in a sandbox, such as names, emails, and phone numbers, so teams can build, test, and train without seeing real personal information. Salesforce offers two tools for this job: Data Mask & Seed, and the Anonymize application in Own from Salesforce.
Why sandbox data needs protection
Sandboxes can hold personal information (PI) and personally identifiable information (PII). Examples include:
- Customer and employee names
- Phone numbers
- Email addresses
- Physical addresses
- Social Security numbers
- Credit card and banking details
- Compensation
Because sandboxes are used for development and testing, developers, employees, and contractors who can't access production often get sandbox access. As a result, they can see data that production would restrict.
Privacy laws such as the EU General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA) require strict protection of personal data. Industry rules such as PCI DSS and HIPAA also require it. Masking or anonymizing sandbox data reduces risk and supports an org in meeting these compliance and privacy requirements.