GDPR’s Article 32 states:
Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, the controller and the processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate:
(a) the pseudonymisation and encryption of personal data;
…
So, I would like to store personal data in an encrypted form. The ORM/DAO should receive already encrypted struct, and it shouldn’t be handled transparently. Therefore, only needed use-cases (reasons of processing) would do decryption of data, explicitly. And, anything else would read this data as a “garbage”.
I have no prior experience with encryption applied on large scale data, and in persistent manner, ie. table rows. Only for transport streams, where there’s no persistence of data. However, I have read, that usage of the same key for all data is a bad practice, as the key can be easily extracted from multiple instances encrypted data (where original data is known).
What would be a good starting point for this kind of encryption? And, are there any libraries, which focus (at least partially) on this GDPR issue, or on structs encryption (ie. using reflection)?