-
-
-
- Introduction to security
- Secure development
- Security certification
- Field properties concerning security
- Developing user groups securely
- Security considerations for user interface
- Secure file organization
- Securely using the request
- Cross Site Scripting (XSS)
- Other options concerning secure development
- Security analysis
- Secure deployment
- Secure application management
- Scrambling of testdata
- Anonymization of personal data
- Using robots.txt
- Permission settings
- Security measures
- Data encryption
-
- Search Engine Optimization
- OTP
- User Interface migration guide
- User account management
- Instructies voor implementatie van visueel editen van nieuwsbrieven
- Login as another user
- Support
- More information about moving to User Interface Version 4.0
- Standaard page layout
- Sections moved to layout
- Aanpassingen in release 2024-7
- Media library
- Aanpassingen in release 2024-10
- Analytics and Matomo
- Registration forms
- How to change names of classes and fields?
- Responsible Disclosure Policy
- How to upload a blob in Velocity?
- Aanpassingen in release 2024-2
- Instances
- Google Analytics
- Street and City helper (postcodecheck)
- Responsible disclosure-beleid
- Postcode check service (straat en huisnummer) kosten
- Expressions
- Regular Expression Reference
Anonymization of personal data
To anonymize data of a class you have to take 2 steps:
- Select the fields and the method of anonymization
- Create the action to anonymize the (connected) records
Step 1. Select the fields and the method of anonymization
A) Define the columns in the table (mostly in the tabel with the person data) which you want to anonymize. E.g. Last name, email etc.
B) Define the way of anonymizing the content of that column. 3 possibilities: clear, fixed value (also with a script) or scramble.
Example: clear value
Example: clear value
Example fixed value (script)
Step 2. Create the action to anonymize the (connected) records
A) The helper type is called: anonymize record
If there are connected clazzes with (persistent) (personal) data it's possible to define the route to these clazzes. Anonymize the columns in these classes with personal data.
If you want to anonymize sent emails as well, choose the route to the mail class, from the recipient class.
Postscripts
If you want to do some postscripting it's possible to add this script to the action.
Anonymization in batch
It is also possible to anonymize records in a batch process. For this you will have to define the Anonymization filter on the class of the records you want to anonymize. You will find this setting on the Relevance tab page of the class.
Forced re-anonymization
In case of eventual replacement of personalized data of formerly anonymized records, for instance due to a backup restore, or raw import of data, it is possible to enforce re-anonymization in batch of all records in a selected class or classes. To do this, make sure you have the required Administrator status in your session, then select the option Force re-anonymization in the Deployment menu in the backstage. Select the class(es) for which records need to be re-anonymized and proceed.