This project is not covered by Drupal’s security advisory policy.
Does a developer retrieve the actual data of your production database for developing the website?
Does your database contain company/customer/business sensitive information?
If you answer "yes" on both questions, then you actually need to start using the scrambler module.
ATTENTION! WE STRONGLY ADVICE NOT TO USE THIS MODULE IN A LIVE/PRODUCTION ENVIRONMENT. YOUR DATA WILL GET SCRAMBLED AND THE ONLY WAY BACK IS PLACING BACK A DATABASE BACKUP.
The scrambler module helps you to prevent exposing sensitive information from the database. It does this by giving you the ability to configure what data to scramble. The scrambling methods that can be applied by default are:
- Emptying values
- Shuffle characters
- Shuffle words
Optionally you can introduce your own methods.
A presentation about how to protect resources from being able to read & exploit sensitive data/information, given on Drupalcamp Leuven 2015
How to implement your own data sanitizing?
If you want to implement data that is not related to the Drupal core's field structure, you can implement this custom coded by reading the following documentation.
- Maintenance status: Actively maintained
- Development status: Under active development
- Module categories: Content, Developer, Drush, Fields, Security
- Downloads: 328
- Last modified: 10 September 2016
- This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.