Skip to main content
Informationssicherheit / NIS2

Encryption

Encryption is a cryptographic process that uses keys to transform data into an unreadable format, protecting it against unauthorised access both while stored and while transmitted.

Encryption refers to the conversion of plaintext into ciphertext using cryptographic algorithms and secret keys. Only those who hold the matching key can decrypt the data and make it legible again. A distinction is drawn between symmetric encryption, where the same key is used to encrypt and decrypt (for example AES), and asymmetric encryption, which relies on a key pair consisting of a public and a private key (for example RSA or ECC). In practice both methods are often combined: an asymmetrically exchanged session key then secures the actual data encryption symmetrically.

Information security distinguishes two central use cases: the encryption of data at rest, for instance on hard drives, in databases or in backups, and the encryption of data in transit, for instance via TLS during communication between systems. Encryption primarily safeguards the protection goal of confidentiality, but in combination with techniques such as digital signatures and message authentication codes it also supports integrity and authenticity. Beyond choosing strong, recognised algorithms, the decisive factor for its effectiveness is robust key management, which governs the generation, storage, rotation and destruction of keys across their entire lifecycle.

From a regulatory perspective, encryption is a central technical and organisational measure. The NIS2 Directive explicitly names policies and procedures regarding the use of cryptography and, where appropriate, encryption in Art. 21(2)(h) as part of the risk management of essential and important entities. The GDPR likewise cites encryption in Art. 32(1)(a) as an example of an appropriate measure to ensure the security of processing; effective encryption can also remove the obligation to notify data subjects of a breach under Art. 34(3)(a). The German BSI IT-Grundschutz specifies the requirements in module CON.1 Crypto Concept and provides guidance for a verifiable cryptographic concept.

Legal Basis

Art. 21(2)(h) NIS2 Directive (EU) 2022/2555; Art. 32(1)(a) GDPR; ISO/IEC 27001 Annex A 8.24; BSI IT-Grundschutz CON.1

Practical Example

A mid-sized mechanical engineering firm qualifies as an important entity under the NIS2 requirements. The information security officer draws up a crypto concept following BSI CON.1: the hard drives of all laptops are encrypted with BitLocker using AES-256, traffic between sites runs exclusively over TLS 1.3, and database backups are encrypted before being placed in cloud storage. The firm manages the associated keys in a hardware security module with documented rotation every twelve months. When a laptop is later stolen, the security officer can demonstrate that the data was encrypted and therefore inaccessible to third parties, making notification of affected individuals unnecessary.

FAQ

Symmetric encryption uses the same key to encrypt and decrypt, which is fast but tricky when exchanging the key. Asymmetric encryption uses a key pair of a public and a private key and solves the exchange problem, but is more computationally intensive. In practice both methods are combined in hybrid schemes.
NIS2 explicitly names policies and procedures for cryptography and, where appropriate, encryption in Art. 21(2)(h) as part of risk management. There is no rigid obligation to encrypt every processing operation, but there is a duty to assess its use on a risk basis and to implement it wherever it is appropriate.
Encryption is only as strong as the protection of the associated keys. If keys are stored insecurely, are not rotated or become compromised, even a strong algorithm is worthless. Documented key management governs the generation, distribution, storage, rotation and destruction of keys across the entire lifecycle.

How preeco supports you

Learn how our software supports you with this topic.

Learn more