Risorse · 13
Gestione del ciclo di vita dei dati: conservare, archiviare ed eliminare con prove
Collegare ogni categoria di dati a uno scopo, un responsabile, un criterio di conservazione e un processo di eliminazione effettivamente verificabile.
Aggiornato · 9 min
Obiettivi di questa guida
- Riduci i dati senza un utilizzo definito.
- Includi backup ed esportazioni nelle regole del ciclo di vita.
- Traccia blocchi ed eccezioni.
- Dimostra la cancellazione senza esporre nuovamente il contenuto cancellato.
Verifica rapida
- Quale scopo giustifica ancora ciascuna categoria?
- Dove si trovano copie e derivati?
- Chi può estendere il periodo di conservazione?
- Come si propaga la cancellazione?
- Quali prove rimangono dopo la cancellazione?
Metodo passo passo
- 1
Mappa categorie e utilizzi
Dati di inventario, scopi, persone interessate, sistemi, proprietari e flussi. Raggruppare per regola operativa anziché per nome della tabella del database.
Risultato: registro di categoria, utilizzo, sistema e proprietario.
- 2
Definire gli eventi del ciclo di vita
Collegare creazione, utilizzo attivo, chiusura, archiviazione, blocco ed eliminazione a eventi osservabili. Indicare quale regola prevale in caso di conflitto tra obblighi.
Risultato: matrice eventi, stati e azioni.
- 3
Includere ogni copia
Aggiungere cache, esportazioni, ambienti di test, backup, archivi, dispositivi e provider. Documentare la velocità di propagazione delle modifiche del ciclo di vita.
Risultato: mappa di posizione e replica.
- 4
Gestire le eccezioni
Controllare i blocchi legali, gli obblighi di settore e le esigenze probatorie con autorità, ambito, durata e revisione.
Risultato: registro delle eccezioni con data.
- 5
Automatizzazione con controllo
Attivazione dell'archiviazione e della cancellazione dalle regole di versioning. Registrazione del volume, degli errori e dei tentativi senza conservare il contenuto eliminato come prova.
Risultato: procedura di elaborazione e registro.
- 6
Test di fine vita
Campionamento dei record che hanno raggiunto la scadenza, verifica dell'assenza nei sistemi e della gestione ritardata del backup, quindi correzione delle lacune.
Risultato: report di eliminazione e piano correttivo.
Esempio pratico fittizio
Situazione illustrativa
Un modulo crea un record cliente e diverse copie nelle esportazioni e nei backup. Il team collega ogni copia al suo scopo, all'evento di inizio e alla regola di conservazione documentata.
Decisione e prove attese
Un campione di record scaduti verifica la cancellazione, le eccezioni giustificate e la propagazione ai sistemi secondari senza copiare i dati cancellati nel log.
Indicatori di gestione
| Indicatore | Cosa misura | Prima azione |
|---|---|---|
| Copertura | Categorie collegate a una regola e a un proprietario | Gestire prima i dati orfani |
| Scadenze eseguite | Elementi scaduti gestiti entro i tempi previsti | Analizzare code bloccate ed eccezioni |
| Copie controllate | Posizioni incluse nella propagazione del ciclo di vita | Aggiungere esportazioni e backup dimenticati |
| Eliminazione degli errori | Azioni di eliminazione non riuscite o non confermate | Correggere e riprodurre con prove |
Errori comuni
- Impostare una durata senza un evento di inizio
- Dimenticare esportazioni e ambienti di test
- Trattare il backup come archivio permanente
- Conservare i dati eliminati nei log
Domande frequenti
I backup immutabili devono essere eliminati immediatamente?
Non sempre. Documentare il loro ciclo di vita, impedire il riutilizzo ordinario e applicare la cancellazione quando la rotazione o il ripristino lo rendono possibile.
Un singolo periodo può coprire tutte le categorie di dati?
Raramente. Scopo, categoria, relazione, obblighi e necessità di prove possono richiedere trigger diversi.
Come si può dimostrare la cancellazione?
Conservare un identificativo tecnico, la regola applicata, il timestamp, il risultato e il controllo senza copiare i dati cancellati nel log.
Riferimenti: dati, usi e limiti
Documentazione consultata il .
Le note dettagliate di questa edizione sono disponibili in inglese.
| Fonte e finalità | Dato o riferimento verificato | Come utilizzarlo | Limite da conservare |
|---|---|---|---|
| NIST · Privacy Framework Examine risks to people arising from data processing. |
The Privacy Framework is a voluntary privacy risk-management tool. It is distinct from a universal legal compliance checklist. | Describe actual processing: data, purposes, recipients, access and retention. Compare documents, settings and deletion or retrieval tests. | Using the framework alone does not determine compliance with applicable law. Processing context and jurisdiction still need examination. |
Supporti: bonifica e prove
Le note dettagliate di questa edizione sono disponibili in inglese.
Data retirement is more than deleting a file. Define the target data, copies, medium, destination and required protection. Media sanitization, application-level deletion and retention expiry answer related but different questions.
NIST SP 800-88 Revision 2 became final on 26 September 2025 and supersedes Revision 1, withdrawn on that date. The separate FAQ published on 16 July 2026 complements it. The 20 CIE-SAN points below are CIE editorial selection, not NIST control identifiers or an exhaustive compliance checklist.
NIST · SP 800-88 Rev. 2 · Guidelines for Media Sanitization · Final · 2025-09-26 · consulted 2026-10-23
NIST · SP 800-88 Rev. 1 · withdrawn edition · Withdrawn 2025-09-26 · superseded by Revision 2
Three methods, with techniques requiring qualification
| NIST method | Goal and media condition · synthesis | Reading limit |
|---|---|---|
| Clear | Logical techniques over user-addressable locations, protecting against simple recovery using the normal interface. | Does not establish coverage of non-addressable areas; not applicable to hard copy. |
| Purge | Logical or physical techniques making target-data recovery infeasible using state-of-the-art laboratory techniques, with media potentially reusable. | Select the technique for the medium and policy. Cryptographic erase is a conditional Purge technique, not a fourth method. |
| Destroy | Target-data recovery infeasible at the state-of-the-art laboratory level, leaving the medium unable to store data. | Damaging a device is insufficient. This method does not apply to logical or virtual storage as if it were an owned physical medium. |
Revision 2 mainly addresses the sanitization program and assurance. Apart from cryptographic erase, equipment-specific technique details are referred to relevant standards and those accepted by organisational policy. This page supplies neither an erasure command nor an automatic method recommendation.
NIST · SP 800-88r2 · full publication · September 2025 · printed pages distinguished from PDF viewer pages
Verify execution, then validate adequacy
| Layer | Question | Useful evidence |
|---|---|---|
| Verification · §4.5.1 | Did the technique complete correctly? | Status, errors and anomalies; suitable media, residue or equipment inspection according to the technique. |
| Validation · §4.5.2 | Is the result adequate for this data and scope? | Reasoned acceptance or rejection, considering sensitivity and observed limitations. |
| Documentation · §4.6 | Can the action be attributed to the correct medium and its destination tracked? | Identifiers, method, technique, tool, version, verification, validation and policy-appropriate personnel. |
A tool can report completion while technique or scope is unsuitable. Unless policy requires it, NIST does not call for elaborate content sampling after every Clear or Purge. Retain verification limitations and the validation decision; a check count does not replace that decision.
Esplora i punti di prova
Filter review questions by method and stage, or search text within the rows. These filters prepare evidence reading; they do not select a technique or operate on media. Method associations are editorial, not applicability decisions.
Riferimenti mostrati: 20 su 20.
Nessun riferimento corrisponde ai filtri.
| CIE reference and stage | CIE review question | CIE evidence to examine | NIST locator |
|---|---|---|---|
CIE-SAN-01Retention and authority Preparazione Clear · Purge · Destroy | Is retirement authorised for this data under applicable rules and validated retention needs? | Owner decision, rule and any documented hold before an operation. | SP 800-88r2 · 1.1 printed page 2 · PDF page 11 |
CIE-SAN-02Data sensitivity Preparazione Clear · Purge · Destroy | Are sensitivity and expected protection explicit for the target data? | Dated categorisation and organisational acceptance criteria. | SP 800-88r2 · 4.3.2 printed page 21 · PDF page 30 |
CIE-SAN-03Target data and copies Preparazione Clear · Purge · Destroy | Which media, caches, copies and derivatives contain the target data? | Scope inventory, justified exclusions and dependencies; a logical volume is not the whole storage system. | SP 800-88r2 · 2.3 printed page 6 · PDF page 15 |
CIE-SAN-04Reuse and control Preparazione Clear · Purge · Destroy | Will the medium be reused, and remain under the organisation’s defined control? | Intended destination, owner and transfer or maintenance conditions. | SP 800-88r2 · 4.3.3–4.3.4 printed page 22 · PDF page 31 |
CIE-SAN-05Media capabilities Preparazione Clear · Purge · Destroy | Does the vendor describe command coverage, excluded areas and relevant validation testing? | Model- and version-specific documentation, covered areas, limits and assurance evidence. | SP 800-88r2 · Appendix B printed page 35 · PDF page 44 |
CIE-SAN-06Clear scope Esecuzione Clear | Does the selected technique cover user-addressable locations within the target scope? | Media-appropriate procedure and execution result; pass count alone does not establish protection. | SP 800-88r2 · 3.1.1 printed page 8 · PDF page 17 |
CIE-SAN-07Flash and non-addressable areas Preparazione Clear · Purge | Do remapping, spare cells and abstraction limit the proposed technique? | Media characteristics and technical coverage rationale; do not transfer a magnetic-disk recipe to an SSD. | SP 800-88r2 · 3.1.1 printed page 9 · PDF page 18 |
CIE-SAN-08Purge scope Esecuzione Purge | Does the technique target the expected protection while potentially preserving reuse? | Organisationally accepted method, technique and standard, with media-specific restrictions. | SP 800-88r2 · 3.1.2 printed page 10 · PDF page 19 |
CIE-SAN-09Destroy scope Esecuzione Destroy | Does the result make target-data recovery infeasible at the expected level and leave the medium unusable? | Media-specific criteria, result inspection and residue destination; a merely damaged device is insufficient. | SP 800-88r2 · 3.1.3 printed page 11 · PDF page 20 |
CIE-SAN-10Encryption history Cancellazione crittografica Purge | Were target sensitive data encrypted under the required conditions throughout their presence on the medium? | Encryption history and coverage; late activation alone does not address earlier plaintext data. | SP 800-88r2 · 3.2.2 printed page 13 · PDF page 22 |
CIE-SAN-11Keys and recoverable copies Cancellazione crittografica Purge | Are target keys, copies and dependent keys identified, including outside the medium? | Key-management map, escrow, injection, backups and sanitization mechanism; do not copy secrets into the record. | SP 800-88r2 · 3.2.3 printed page 14 · PDF page 23 |
CIE-SAN-12Cryptographic assurance Cancellazione crittografica Purge | Is implementation and key-sanitization quality supported by evidence? | Relevant assurance or validation for generation, encryption, wrapping and sanitization; distinguish US federal requirements from local policy. | SP 800-88r2 · 3.2.4 printed page 15 · PDF page 24 |
CIE-SAN-13CE traceability Tracciabilità Purge | Does the record identify cryptographic-erase mechanisms, coverage, errors and commands? | Product and version references, cryptographic scope, key life cycle and error handling. | SP 800-88r2 · 3.2.5 printed page 16 · PDF page 25 |
CIE-SAN-14Logical or cloud storage Esecuzione Clear · Purge | What assurance covers the encrypted boundary, copies and key management when hardware is abstracted? | Provider commitments and evidence; deleting an object or API credential does not establish storage sanitization. | SP 800-88r2 · 3.1.2 printed page 10 · PDF page 19 |
CIE-SAN-15Technical verification Garanzia Clear · Purge · Destroy | Did the technique finish as expected, and what errors or anomalies remain? | Tool status, errors, media condition or suitable physical inspection; policy defines any additional checks. | SP 800-88r2 · 4.5.1 printed page 24 · PDF page 33 |
CIE-SAN-16Outcome validation Garanzia Clear · Purge · Destroy | Are verification results acceptable for the scope and sensitivity? | Reasoned acceptance or rejection and an identified decision owner, distinct from a completed status. | SP 800-88r2 · 4.5.2 printed page 24 · PDF page 33 |
CIE-SAN-17Anomalies and rework Garanzia Clear · Purge · Destroy | Are scope limits, unsuitable settings or inadequate outcomes examined before acceptance? | Gap analysis and rework or escalation decision; reassess whether the medium remains reusable. | SP 800-88r2 · 4.5.2 printed page 25 · PDF page 34 |
CIE-SAN-18Identify the operation Tracciabilità Clear · Purge · Destroy | Does the record connect the correct medium to its method, technique and tool version? | Media identifiers, type, origin, separate method and technique, tool and version. | SP 800-88r2 · 4.6 printed page 26 · PDF page 35 |
CIE-SAN-19Responsibilities and dates Tracciabilità Clear · Purge · Destroy | Can execution, verification and validation owners be identified with relevant dates and locations? | Policy-appropriate roles and records; limit personal information to evidence needs. | SP 800-88r2 · 4.6 printed page 26 · PDF page 35 |
CIE-SAN-20Destination and reconciliation Tracciabilità Clear · Purge · Destroy | Do final disposition and each medium’s tracking agree with the starting inventory? | Destination evidence and reconciliation of expected, processed, rejected or missing media. | SP 800-88r2 · Appendix C printed page 37 · PDF page 46 |
Cryptographic erase: four boundaries to document
| Boundary | What to establish | What the label alone does not prove |
|---|---|---|
| Encrypted data | Encryption history and coverage since data entered the medium, accounting for suitable prior sanitization. | Enabling encryption today alone does not address earlier sensitive plaintext data. |
| Keys and hierarchy | Target keys, copies, escrow, injection and dependencies that could enable decryption. | Deleting a service credential is not necessarily sanitizing a data-encryption key. |
| Implementation | Quality of encryption, generation, wrapping and key sanitization, with relevant assurance. | An encrypted label establishes neither coverage nor CE effectiveness. |
| Copies and cloud | Encrypted boundary, external copies and provider evidence where underlying hardware is abstracted. | A successful deletion API response alone does not establish sanitization of every copy. |
NIST · FAQ for SP 800-88r2 · Published 2026-07-16 · consulted 2026-10-23
Six educational situations: where evidence may be missing
| Fictional situation | Premature conclusion | Review to prepare |
|---|---|---|
| An SSD underwent multiple overwrite passes. | Pass count proves Purge. | Examine spare cells, remapping, technique scope and media assurance. |
| A drive no longer starts after a physical operation. | The medium is Destroy and its data unrecoverable. | Identify technique and applicable criteria; inoperability alone does not establish the outcome. |
| Encryption was enabled after earlier plaintext use. | Removing keys sanitizes the entire history. | Establish scope and history; examine a suitable technique for earlier data. |
| A cloud provider confirms object deletion. | Every physical copy is sanitized. | Review versions, replicas, backups, key boundaries and relevant contractual or technical evidence. |
| A tool reports completed despite an inaccessible area. | Validation follows from tool success. | Retain the anomaly, its scope effect and reasoned acceptance or rejection. |
| An attestation covers media delivered to a provider. | The entire starting inventory was processed. | Reconcile expected identifiers and attestations; record missing items, rejections, transfers and destination. |
Connect the operation to the correct medium
Section 4.6 and Appendix C’s example describe information to record. For internal review, link media identity, separate method and technique, tool and version, verification results, validation decision, personnel and destination. The NIST example is not NIST certification of an organisation.
Retain necessary evidence with suitable access and retention. A record can reference target data without copying it: do not attach cryptographic keys, deleted content or unnecessary personal data.
Sources: NIST SP 800-88r2 and its FAQ, consulted 23 October 2026. The publication states that it is not subject to copyright in the United States; attribution to Ramaswamy Chandramouli and Eric A. Hibbard, NIST, 2025. Questions, CIE-SAN references, filter associations and fictional situations are CIE editorial synthesis in French and English. No NIST endorsement of CIE, a product or a particular method is implied.
NIST · Copyrights & Disclaimers · Publication also states its copyright status in the front matter
Verified documentary editions
SP 800-88r2 · final 2025-09-26 · FAQ 2026-07-16 · reviewed 2026-10-23
Publication PDF SHA-256: 39bb805c72723ed74f08e5806cd8463ca2554a62abb4f97b9d19c0398a8a7c55
FAQ PDF SHA-256: 3f81228035aae09714d8e70962cdde45228bc421287068236d624ce40f44e3bf
Riferimenti ufficiali
I riferimenti supportano il metodo. Adattare i controlli al proprio contesto; non costituiscono una certificazione. I titoli dei riferimenti originali e i documenti di origine potrebbero essere in un'altra lingua.
Riferimenti consultati il .
- CNIL — Les durées de conservation des données
- NIST — SP 800-53A, Assessing Security and Privacy Controls
- NIST · Privacy Framework
- NIST · SP 800-88 Rev. 2 · Guidelines for Media Sanitization
- NIST · SP 800-88r2 · full publication
- NIST · FAQ for SP 800-88r2
- NIST · SP 800-88 Rev. 1 · withdrawn edition
- NIST · Copyrights & Disclaimers
