Understand the protection encryption at rest provides
Encryption at rest converts stored information into a form that requires access to cryptographic keys to read it. It can reduce exposure from stolen laptops, removed disks, backup media and certain types of unauthorised storage access. The protection depends on correct implementation and separation of key access.
It does not necessarily prevent a compromised application or legitimate signed-in user from reading data. A full-disk encrypted server may expose plaintext to an attacker who obtains administrative access while the server is running. Encryption should therefore complement access controls, monitoring and secure backup practices.
Decide which data and devices need protection
Identify personal information, sensitive operational records, credentials, backups and other data relevant to covered services. Consider where copies exist, including endpoints, shared storage, cloud snapshots, databases and supplier-managed platforms. Use asset classification and impact assessment to determine safeguards.
Some environments require file-level or application-level encryption in addition to storage encryption, depending on who needs access and how data are processed. Avoid assuming that one cloud-provider setting protects every derivative copy.
Choose controls appropriate to the threat
Full-disk encryption can help protect portable devices and decommissioned media, while database or application-level encryption may address different threats. Assess the operating system, deployment model, administrative rights, recovery needs and vendor capabilities before selecting a solution.
For cloud services, clarify whether encryption and key management are provided by the platform or configured by the customer. Shared responsibility should be reflected in contracts, architecture records and operational procedures rather than implied by a generic service description.
Protect the keys and plan for recovery
Encrypting data without a dependable key-management process can create both confidentiality and availability risks. Control who can retrieve or use keys, how they are backed up, and what happens when a key is suspected of compromise. Separate duties where appropriate and log sensitive administrative actions.
Test restoration of encrypted backups and access to recovered data in a controlled environment. A successful storage restore is incomplete if the necessary cryptographic keys or identity systems are unavailable during a crisis.
Verify implementation and handle exceptions
Collect evidence from device-management reports, storage configurations, key-management settings and relevant test results. Check coverage against the asset inventory, including devices or systems that were offline during enforcement. Review exclusions, compensating safeguards and their owners.
Article 21(2)(h) requires policies and procedures regarding cryptography and, where appropriate, encryption, not the claim that all information must be encrypted by one technical method. Verify binding national rules and any relevant sector-specific implementing regulation before describing an internal design choice as mandatory.
Points of clarification
Does NIS2 require encryption of every file?
The Directive uses a risk-based formulation and refers to encryption where appropriate. Check applicable national and sector-specific rules and classify data before selecting measures.
Is full-disk encryption sufficient?
Not for every threat. It helps in certain loss or theft scenarios but does not replace application permissions, monitoring or key management.
What evidence is useful for an encryption-at-rest assessment?
Asset coverage, configuration records, key access controls, exception decisions and tested recovery evidence provide a more reliable picture than a policy alone.