Commandline tool to anonymize PostgreSQL databases
Project description
A commandline tool to anonymize PostgreSQL databases for DSGVO/GDPR purposes.
It uses a YAML file to define which tables and fields should be anonymized and provides various methods of anonymization. The tool requires a direct PostgreSQL connection to perform the anonymization.
Features
Intentionally compatible with Python 2.7 (for old, productive platforms)
Anonymize PostgreSQL tables on data level entry with various providers (some examples in the table below)
Exclude data for anonymization depending on regular expressions or SQL WHERE clauses
Truncate entire tables for unwanted data
Field |
Value |
Provider |
Output |
---|---|---|---|
first_name |
John |
choice |
(Bob|Larry|Lisa) |
title |
Dr. |
clear |
|
street |
Irving St |
faker.street_name |
Miller Station |
password |
dsf82hFxcM |
mask |
XXXXXXXXXX |
credit_card |
1234-567-890 |
partial_mask |
1??????????0 |
md5 |
0cba00ca3da1b283a57287bcceb17e35 |
||
faker.unique.email |
|||
phone_num |
65923473 |
md5 as_number: True |
3948293448 |
ip |
157.50.1.20 |
set |
127.0.0.1 |
uuid_col |
00010203-0405-…… |
uuid4 |
f7c1bd87-4d…. |
Note: faker.unique.[provider] only supported on Python 3.6+ (Faker library min. supported python version)
Note: uuid4 - only for (native uuid4) columns
See the documentation for a more detailed description of the provided anonymization methods.
Installation
The default installation method is to use pip:
$ pip install pganonymize
Usage
usage: pganonymize [-h] [-v] [-l] [--schema SCHEMA] [--dbname DBNAME]
[--user USER] [--password PASSWORD] [--host HOST]
[--port PORT] [--dry-run] [--dump-file DUMP_FILE]
Anonymize data of a PostgreSQL database
optional arguments:
-h, --help show this help message and exit
-v, --verbose Increase verbosity
-l, --list-providers Show a list of all available providers
--schema SCHEMA A YAML schema file that contains the anonymization
rules
--dbname DBNAME Name of the database
--user USER Name of the database user
--password PASSWORD Password for the database user
--host HOST Database hostname
--port PORT Port of the database
--dry-run Don't commit changes made on the database
--dump-file DUMP_FILE
Create a database dump file with the given name
--dump-options DUMP_OPTIONS
Options to pass to the pg_dump command
--init-sql INIT_SQL SQL to run before starting anonymization
--parallel Data anonymization is done in parallel
Despite the database connection values, you will have to define a YAML schema file, that includes all anonymization rules for that database. Take a look at the schema documentation or the YAML sample schema.
Example calls:
$ pganonymize --schema=myschema.yml \
--dbname=test_database \
--user=username \
--password=mysecret \
--host=db.host.example.com \
-v
$ pganonymize --schema=myschema.yml \
--dbname=test_database \
--user=username \
--password=mysecret \
--host=db.host.example.com \
--init-sql "set search_path to non_public_search_path; set work_mem to '1GB';" \
-v
Database dump
With the --dump-file argument it is possible to create a dump file after anonymizing the database. Please note, that the pg_dump command from the postgresql-client-common library is necessary to create the dump file for the database, e.g. under Linux:
$ sudo apt-get install postgresql-client-common
Example call:
$ pganonymize --schema=myschema.yml \
--dbname=test_database \
--user=username \
--password=mysecret \
--host=db.host.example.com \
--dump-file=/tmp/dump.gz \
-v
So that the password for dumping does not have to be entered manually, it can also be entered as an environment var PGPASSWORD:
$ PGPASSWORD=password pganonymize --schema=myschema.yml \
--dbname=test_database \
--user=username \
--password=mysecret \
--host=db.host.example.com \
--dump-file=/tmp/dump.gz \
-v
Docker
If you want to run the anonymizer within a Docker container you first have to build the image:
$ docker build -t pganonymize .
After that you can pass a schema file to the container, using Docker volumes, and call the anonymizer:
$ docker run \
-v <path to your schema>:/schema.yml \
-it pganonymize \
/usr/local/bin/pganonymize \
--schema=/schema.yml \
--dbname=<database> \
--user=<user> \
--password=<password> \
--host=<host> \
-v
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file pganonymize-0.12.0.tar.gz
.
File metadata
- Download URL: pganonymize-0.12.0.tar.gz
- Upload date:
- Size: 18.5 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/5.1.0 CPython/3.12.4
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 9e776ffdeaebc5e0cee482fa230ffe97b7ebf6b976ced36302d2762245d838d0 |
|
MD5 | 60d6be2fa028d93e809151050869e4eb |
|
BLAKE2b-256 | 8793e09cc6cea668684184c37e62efea860fc4f2286a8922eb10cebe1593262c |
File details
Details for the file pganonymize-0.12.0-py2.py3-none-any.whl
.
File metadata
- Download URL: pganonymize-0.12.0-py2.py3-none-any.whl
- Upload date:
- Size: 16.0 kB
- Tags: Python 2, Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/5.1.0 CPython/3.12.4
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 80b3f85bbab1da2b3af250ea503d620df9758f9474cf222962937e8810f7abb3 |
|
MD5 | af5d9e57200f6556827a607c333a7b9e |
|
BLAKE2b-256 | 3310e3654b4b6e093bb6cd55ebe2b811f5b2c6cc5942f9fa6bfd26f3a1d27e5e |