Django model fields encrypted using Pycryptodome AES-256 GCM.
Django Searchable Encrypted Fields
This package is for you if you would like to encrypt model field data "in app" - ie before it is sent to the database.
Why another encrypted field package?
- We use AES-256 encryption with GCM mode (via the Pycryptodome library).
- Encryption keys never leave the app.
- It is easy to generate appropriate encryption keys with
secrets.token_hex(32)from the standard library.
- You can make 'exact' search lookups when also using the SearchField.
Install & Setup
$ pip install django-searchable-encrypted-fields
# in settings.py INSTALLED_APPS += ["encrypted_fields"] # A list of hex-encoded 32 byte keys # You only need one unless/until rotating keys FIELD_ENCRYPTION_KEYS = [ "f164ec6bd6fbc4aef5647abc15199da0f9badcc1d2127bde2087ae0d794a9a0b" ]
This package provides two types of model field for Django.
- A series of EncryptedField classes which can be used by themselves and work just like their regular Django counterparts. Contents are transparently encrypted/decrypted.
- A SearchField which can be used in conjunction with any EncryptedField. Values are concatentaed with a
hash_keyand then hashed with SHA256 before storing in a separate field. This means 'exact' searches can be performed.
This is probably best demonstrated by example:
Using a stand-alone EncryptedField
from encrypted_fields import fields class Person(models.Model): favorite_number = fields.EncryptedIntegerField(help_text="Your favorite number.")
You can use all the usual field arguments and add validators as normal. Note, however, that primary_key, unique and db_index are not supported because they do not make sense for encrypted data.
Always add a new EncryptedField and do a data-migration, rather than alter an existing regular Django model field.
encrypted_fields_test app for an example.
Included EncryptedField classes
The following are included:
"EncryptedFieldMixin", "EncryptedTextField", "EncryptedCharField", "EncryptedEmailField", "EncryptedIntegerField", "EncryptedDateField", "EncryptedDateTimeField", "EncryptedBigIntegerField", "EncryptedPositiveIntegerField", "EncryptedPositiveSmallIntegerField", "EncryptedSmallIntegerField",
Note that, although untested, you should be able to extend other regular Django model field classes like this:
class EncryptedIPAddressField(EncryptedFieldMixin, models.GenericIPAddressField): pass
Using a SearchField along with an EncryptedField
The SearchField is responsible for:
- Providing the input for its EncryptedField
- Displaying (returning) the EncryptedField's value
- Storing the searchable hashed version of the input
The EncryptedField is the "real" field and so should be the appropriate field type for the expected input. It does all the under-the-hood things you would expect, eg:
- Providing validation/validators for the input
- Converting the input and database values to the appropriate python object
class Person(models.Model): _name_data = fields.EncryptedCharField(max_length=50, default="", null=True/False) name = fields.SearchField(hash_key="f164ec6bd...794a9a0b", encrypted_field_name="_name_data") favorite_number = fields.EncryptedIntegerField() city = models.CharField(max_length=255) # regular Django model field
You can then use it like:
# "Jo" is hashed and stored in 'name' as well as symmetrically encrypted and stored in '_name_data' Person.objects.create(name="Jo", favorite_number=7, city="London") person = Person.objects.get(name="Jo") assert person.name == "Jo" assert person.favorite_number == 7 person = Person.objects.get(city="London") assert person.name == "Jo" . # the data is taken from '_name_data', which decrypts it first.
You can safely update like this:
person.name = "Simon" person.save()
But when using
update() you need to provide the value to both fields:
A SearchField inherits the validators, default value and default formfield (widget) from its associated EncryptedField. So:
- Do not add validators (they will be ignored), add them to the associated EncryptedField instead.
default=on the EncryptedField, not the SearchField.
- Do not include the EncryptedField in forms, only include the SearchField.
- Typically you should avoid
editable=Falsein the EncryptedField - it prevents validation.
- You can override the SearchField widget in a
ModelFormas usual (see the
- By convention, declare the EncryptedField before the SearchField in your Model.
Note Although unique validation (and unique constraints at the database level) for an EncryptedField makes little sense, it is possible to add
unique=True to a SearchField.
An example of when this makes sense is in a custom user model, where the
username field is replaced with an
SearchField. Please see the custom user model in
encrypted_fields_test.models and its tests for an example.
Please let us know if you have problems when doing this.
Migrations: Add Search/EncryptedFields to your model, don't alter existing fields
You are encouraged to look at the demo migrations in the
Stand alone EncryptedFields:
Be careful not to change/alter a pre-existing regular django field to be an EncryptedField. The data for existing rows will be unencrypted in the database and appear 'corrupted' when trying to decrypt/fetch it. Instead, add the new EncryptedField to the model and do a data-migration to transfer data from the old field.
SearchField with EncryptedField:
The same goes for SearchFields: add the new SearchField and new Encrypted field to the model. Then do a data-migration to transfer data from the old field to the SearchField (the SearchField will populate the new EncryptedField automatically).
IMPORTANT! Never add a SearchField and point it to an existing EncryptedField, or your SearchField will have the wrong value, and you might lose all your data! How? Why? When adding a new field to a model, Django will update each existing row's new field to have the default value. Note that the default value might be
"" even if
default= is not defined in your field. If the new field is a SearchField then it will be saved with the EncryptedField's default value. This is almost certainly not what you want, even if you did define a default for it.
Generating Encryption Keys
You can use
secrets from the standard library. It will print appropriate hex-encoded keys to the terminal, ready to be used in
settings.FIELD_ENCRYPTION_KEYS or as a hash_key for a SearchField:
$ python manage.py shell >>> import secrets >>> secrets.token_hex(32)
Note: Thanks to Andrew Mendoza for the suggestion.
Note: encryption keys must be hex encoded and 32 bytes
Important: use different hash_key values for each SearchField and make sure they are different from any keys in
Rotating Encryption Keys
If you want to rotate the encryption key just prepend
settings.FIELD_ENCRYPTION_KEYS with a new key. This new key (the first in the list) will be used for encrypting/decrypting all data. If decrypting data fails (because it was encrypted with an older key), each key in the list is tried.
A model instance will start using the new encryption key the next time they are accessed.
You can do a data-migration, simply fetching and saving all objects, to force a complete rotation to the new encryption key.
encrypted_fields_test app for an example.
Be sure to keep all old encryption keys in the list until you are certain all objects have rotated to the new key.
django-searchable-encrypted-fields is tested with Django(2.1, 2.2, 3.0, 3.1) on Python(3.6, 3.7, 3.8) using SQLite and PostgreSQL (10 and 11).
Test coverage is at 96%.
More on testing
Please see the
encrypted_fields_test app (in the gitlab repo) for some example admin site and model form implementations. Just run
pip install -r requirements.txt,
python manage.py migrate and
python manage.py runserver to get started using SQLite.
There is also a basic DjangoRestFramework implementation with a
In our test app, the
User model uses a SearchField for the username. This means that when creating a superuser you must provide the
python manage.py createsuperuser --username bob to avoid an error.
Final note of interest: the tox test suite runs
python manage.py makemigrations for every environment with an empty initial migration directory. This helps ensure the test app will work as expected in all tested environments.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size django-searchable-encrypted-fields-0.1.9.tar.gz (9.5 kB)||File type Source||Python version None||Upload date||Hashes View|
Hashes for django-searchable-encrypted-fields-0.1.9.tar.gz