Data retention and secure deletion: the clause the question tests
How long the customer's data is kept and how it is destroyed or handed back.
How the customer usually asks it
example"How is customer data deleted or returned at the end of the contract?"
Anchor clauses
5 frameworks| Framework | Anchor clause |
|---|---|
| ISO/IEC 27001:2022 | 8.10 Information deletion |
| SIG (Shared Assessments) | domain D Asset and Information Management |
| CSA Cloud Controls Matrix v4.0.1 | DSP-16 Data Retention and Deletion |
| PCI DSS v4.0.1 | 3.2.1 Data retention and disposal minimise stored account data |
| GDPR, Regulation (EU) 2016/679 | Art. 28 Processor |
Every framework that anchors this family is listed here; a register shows the ones ticked for the customer.
Evidence expected
The retention schedule for the customer's data, the deletion method on each store including backups, and the deletion certificate template used at exit.
The clauses, with what an assessor asks for
ISO 27001 8.10 Information deletionDelete information in systems, devices and media when no longer required.
Where answers usually fall short: Retaining data beyond approved period; No evidence of secure erase verification
Source: ISO/IEC 27001:2022
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 DSP-16 Data Retention and DeletionWhat it asks for, in one line (the standard's own text is not quoted here):
Manage data retention, archiving and deletion against business requirements and applicable law, so data is neither kept longer nor destroyed sooner than allowed.
Where answers usually fall short: Retention schedule published with no technical enforcement; Data retained indefinitely because deletion was never built
Source: CSA Cloud Controls Matrix v4.0.1
PCI DSS 3.2.1 Data retention and disposal minimise stored account dataWhat it asks for, in one line (the standard's own text is not quoted here):
The entity limits stored account data through policies, procedures and processes governing how long data is kept and how it is disposed of, which address at minimum: (1) every location where account data is stored; (2) any sensitive authentication data (SAD) held before authorization completes; (3) restricting the volume held and the retention period to what legal, regulatory and/or business needs demand; (4) defined retention periods for stored account data, each with a documented business justification; (5) processes to securely delete account data, or make it unrecoverable, once the retention policy says it is no longer needed; and (6) a check performed at least every three months confirming that account data held beyond its retention period has been made unrecoverable or deleted securely. Applicability: where the data is stored by a third-party service provider such as a cloud provider, the entity is responsible for working with it to understand how the provider satisfies this requirement, with considerations including secure deletion of every geographic instance of a data element. Objective under the customized approach: account data is kept only where needed, for the shortest necessary time, and is securely removed or made unrecoverable afterwards. Future-dated (bullet covering SAD stored before authorization completes): treated as a best practice up to 31 March 2025 and mandatory since then.
Where answers usually fall short: Retention policy omits backups, log files or call-recording platforms where PAN also lands; Quarterly check is not performed or has gaps longer than three months
Source: PCI DSS v4.0.1
GDPR Art. 28 ProcessorUse only processors providing sufficient guarantees to implement appropriate technical and organisational measures such that the processing meets the Regulation's requirements and protects the rights of the data subject. A processor must not engage another processor without the controller's prior specific or general written authorisation, and under a general authorisation must inform the controller of intended additions or replacements so the controller can object. The processing must be governed by a written contract or other legal act binding the processor to the controller, setting out the subject matter and duration, the nature and purpose, the type of personal data, the categories of data subjects and the controller's obligations and rights, and stipulating that the processor processes only on documented controller instructions including as to transfers, ensures persons authorised to process are under a duty of confidentiality, takes all Article 32 measures, respects the sub-processor conditions, assists the controller in responding to data subject rights requests, assists with Articles 32 to 36, deletes or returns all personal data at the controller's choice at the end of the service and deletes existing copies unless law requires retention, and makes available all information needed to demonstrate compliance and allows for and contributes to audits and inspections. The processor must immediately inform the controller if it considers an instruction infringes data protection law. The same obligations must be imposed on any sub-processor, and the initial processor remains fully liable for the sub-processor's performance. A processor that determines purposes and means is a controller for that processing.
Where answers usually fall short: The processor's own standard terms accepted, which commonly omit the audit right, the deletion choice and the instruction infringement notice; A processor inventory that misses tools adopted directly by individual teams, which is where undocumented processing usually sits
Source: GDPR, Regulation (EU) 2016/679