Encryption at rest: the clause the question tests
Whether stored data is encrypted, with what, and who controls the keys.
How the customer usually asks it
example"Do you encrypt customer data at rest? Specify the algorithm."
Anchor clauses
9 frameworks| Framework | Anchor clause |
|---|---|
| ISO/IEC 27001:2022 | 8.24 Use of cryptography |
| SOC 2 (Trust Services Criteria) | CC6.1 CC6.1 Logical access security over protected information assets |
| SIG (Shared Assessments) | domain D Asset and Information Management |
| CSA Cloud Controls Matrix v4.0.1 | CEK-03 Data Encryption |
| NIST Cybersecurity Framework 2.0 | PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected |
| NIST SP 800-53 Rev 5 | SC-28 Protection of information at rest |
| PCI DSS v4.0.1 | 3.5.1 Stored PAN rendered unreadable |
| HIPAA Security Rule (45 CFR 164) | 164.312(a)(2)(iv) Encryption and Decryption (Addressable) |
| GDPR, Regulation (EU) 2016/679 | Art. 32 Security of processing |
Every framework that anchors this family is listed here; a register shows the ones ticked for the customer.
Evidence expected
The cryptography standard naming the algorithms and key lengths, where stored data is encrypted, and who holds and rotates the keys.
The clauses, with what an assessor asks for
ISO 27001 8.24 Use of cryptographyDefine and implement rules for effective use of cryptography and key management.
Where answers usually fall short: Missing documented key lifecycle; Use of outdated or weak algorithms
Source: ISO/IEC 27001:2022
SOC 2 CC6.1 CC6.1 Logical access security over protected information assetsNamed only: the criteria are not stated here; see the official text.
Where answers usually fall short: Service accounts and API keys outside the access management process; Production network flat with no segmentation
Source: SOC 2 (Trust Services Criteria)
SIG domain D Asset and Information ManagementWhat it asks for, in one line (the standard's own text is not quoted here):
Maintain a complete and current inventory of information assets, data classification, ownership, and handling requirements throughout the asset lifecycle.
Where answers usually fall short: Inventory missing cloud assets; Classification labels inconsistent across systems
Source: SIG (Shared Assessments)
CSA CCM CEK-03 Data EncryptionWhat it asks for, in one line (the standard's own text is not quoted here):
Apply cryptographic protection to stored data and to data moving across networks, using libraries that hold certification against an approved standard.
Where answers usually fall short: Encryption at rest claimed from a provider default without verification per data store; Uncertified or self-built cryptographic implementations in use
Source: CSA Cloud Controls Matrix v4.0.1
NIST CSF PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protectedThe confidentiality, integrity, and availability of data-at-rest are protected.
Where answers usually fall short: Encryption inventory misses backup media; Key rotation manual and missed
Source: NIST Cybersecurity Framework 2.0
SP 800-53 SC-28 Protection of information at restRequires the confidentiality or integrity, as the organization determines, of organization-defined information at rest to be protected, so that stored information is safeguarded independently of the access controls in front of it.
Where answers usually fall short: Primary storage encrypted while backups, exports and logs are not; Encryption keys held beside the data they protect
Source: NIST SP 800-53 Rev 5
PCI DSS 3.5.1 Stored PAN rendered unreadableWhat it asks for, in one line (the standard's own text is not quoted here):
PAN must be made unreadable wherever it is stored, using one of these methods: (1) one-way hashes of the whole PAN based on strong cryptography; (2) truncation, where hashing may not substitute for the removed segment, and where hashed and truncated forms, or differing truncation formats, of the same PAN coexist in an environment, added controls must stop them being correlated to rebuild the original; (3) index tokens; (4) strong cryptography with supporting key-management processes and procedures. Applicability: covers PAN in primary storage (databases, flat files such as text files or spreadsheets) and non-primary storage (backups, audit, exception or troubleshooting logs); temporary files holding cleartext PAN during encryption and decryption are not prohibited. Customized approach objective: PAN held on any storage media is never readable in the clear.
Where answers usually fall short: Application or troubleshooting logs contain cleartext PAN while the database is encrypted; Hashed and truncated values held together with nothing preventing reconstruction
Source: PCI DSS v4.0.1
HIPAA 164.312(a)(2)(iv) Encryption and Decryption (Addressable)Implement a mechanism to encrypt and decrypt ePHI. NIST recommends FIPS 140-validated cryptography, encryption at rest for all ePHI stores, and key management aligned to SP 800-57.
Where answers usually fall short: Legacy databases unencrypted; Endpoint encryption not enforced
Source: HIPAA Security Rule (45 CFR 164)
GDPR Art. 32 Security of processingImplement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, taking into account the state of the art, the costs of implementation, the nature, scope, context and purposes of processing, and the risk of varying likelihood and severity for the rights and freedoms of natural persons. Those measures include, as appropriate, the pseudonymisation and encryption of personal data, the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services, the ability to restore the availability of and access to personal data in a timely manner after a physical or technical incident, and a process for regularly testing, assessing and evaluating the effectiveness of the technical and organisational measures. Assess the appropriate level of security against the risks presented by the processing, in particular accidental or unlawful destruction, loss, alteration, unauthorised disclosure of or access to personal data transmitted, stored or otherwise processed. Take steps to ensure that any person acting under the controller's or processor's authority who has access to personal data processes it only on instructions.
Where answers usually fall short: Risk assessed as impact to the business, so processing that is low risk to the organisation and high risk to individuals attracts weak measures; Backups taken and never restore tested, so the ability to restore in a timely manner is assumed rather than demonstrated
Source: GDPR, Regulation (EU) 2016/679