GDPR and data: a practical guide for leadership
What the GDPR requires when exploiting data, what responsibility falls on leadership and how to work with sensitive data without losing control or compliance.
Read articleWhat encryption in transit and at rest is, why both are necessary, how keys are managed, and the role it plays in GDPR compliance.

Encryption is one of the most effective and least understood security measures. Many executives assume "our data is encrypted" without knowing what that means or whether the protection covers the whole data lifecycle.
Encryption transforms data into a format unreadable to anyone without the decryption key. It applies at two moments of the data lifecycle, and both are necessary for complete protection.
Protects data while it moves between systems — app to API, client to server, between data centres — relying on protocols like TLS. Without it, an attacker intercepting the communication could read the data in the clear.
Protects data while stored on disks, databases or backups. If someone accessed the storage or stole a medium, the data would remain unreadable without the key.
Encryption is only as strong as the protection of its keys. Secure management — storage in dedicated modules, periodic rotation, access control — is as important as the algorithm. Standards like ISO/IEC 27001 dedicate specific controls to it.
The GDPR cites encryption as an appropriate technical measure to protect personal data (Article 32). Though not mandatory in every case, it reduces risk and, in a breach, can ease notification obligations if the encrypted data is unintelligible.
Strong encryption with poorly protected keys is useless: key custody matters as much as the algorithm.
Encryption makes data unreadable without the key, in transit (while travelling) and at rest (while stored) — both necessary. Secure key management is as critical as the encryption itself, and encryption is a key GDPR measure that also limits the impact of a breach.
No. Data in transit must also be encrypted. Protecting only one of the two moments leaves a gap through which data could be exposed.
The GDPR cites it as an appropriate measure (Art. 32) but does not impose it in every case. It is a best practice to reduce risk and protect personal data.
Key management. Strong encryption with poorly protected keys is useless, so key custody and rotation are essential.
In transit protects data while moving between systems; at rest protects it while stored on disks, databases or backups.
It reduces the impact: if compromised data is encrypted and unintelligible, the GDPR can ease notification obligations. It limits the damage.
Encryption where data stays protected along its whole path and is only decrypted at authorised endpoints — the best-practice reference.
Tell us what you want to achieve. Data Layer connects, processes and delivers the result up and running, with no infrastructure for you to manage.