Skip to content

Corrected some typos in the blacklist section of the readme #85

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Corrected some typos in the blacklist section of the readme #85

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -204,10 +204,9 @@ Read more about [data anonymization here](http://sunitspace.blogspot.in/2012/09/
## Anonymization Strategies

### Blacklist
This approach essentially leaves all fields unchanged with the exception of those specified by the user, which are scrambled/anonymized (hence the name blacklist).
For `Blacklist` create a copy of prod database and chooses the fields to be anonymized like e.g. username, password, email, name, geo location etc. based on user specification. Most of the fields have different rules e.g. password should be set to same value for all users, email needs to be valid.
This approach essentially leaves all fields unchanged, except for those specified by the user, which are scrambled/anonymized (hence the name "blacklist"). For the blacklist method, create a copy of the production database and choose the fields to be anonymized, such as username, password, email, name, geolocation, etc., based on user specifications. Most fields have different rules; for example, the password should be set to the same value for all users, and the email needs to be valid.

The problem with this approach is that when new fields are added they will not be anonymized by default. Human error in omitting users personal data could be damaging.
The problem with this approach is that when new fields are added, they will not be anonymized by default. Human error in omitting users' personal data could be damaging

```ruby
database 'DatabaseName' do
Expand Down