This project is not covered by Drupal’s security advisory policy.
Is your website GDPR compliant?
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 TO RESTORE FROM A 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.
Presentation
A presentation about how to protect resources from being able to read & exploit sensitive data/information, given on Drupalcamp Leuven 2015
Protecting Resources from Being Able to Read & Exploit Sensitive Data.
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.
Travis CI build status
Project information
- Module categories: Content Editing Experience, Developer Tools, Site Structure
- Created by nico.knaepen on , updated
- This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
Releases
Development version: 7.x-1.x-dev updated 1 Mar 2018 at 10:18 UTC