Skpr now supports sanitisation policies. Discover what this means for you and your hosted applications.
What are sanitisation policies?
Sanitisation policies address Personally Identifiable Information (PII) privacy and compliance concerns, meaning you can be sure database backups won’t store secure information.
These policies provide a configuration which will remove or rewrite specific information in a database backup. Your organisation and git workflow can control these rules.
Given the database size is smaller, this approach also conserves bandwidth and improves local development speeds.
How it works
Applications on Skpr have benefited from MySQL sanitisation rules for some time, and we've extended this to be more flexible and to support backups.
With this latest release Skpr users can add a sanitisation policy to their environment that both MySQL images and backups can utilise.
If a sanitisation policy is not configured, Skpr will set a default policy for the application type.
When would I want to use sanitisation policies?
- Restrict access to personal or sensitive information in a database. For example, webform submission data, user data or data associated with custom functionality.
- Your organisation has compliance requirements for the sensitive information allowed in MySQL image backups.
- Ensure work performed in CI does not leak sensitive production data to non-production environments.
- Reduce the size of your database for better local environment performance and import times.
How can I set my own custom rules?
Skpr users can apply custom policies through your project’s configuration. You can view our technical documentation for more information.
Wrapping up
The Skpr product roadmap has a strong focus on security, and we are excited to release this feature so our customers can benefit from faster, more secure database images and backups.