Recursos · 13

Gobernanza del ciclo de vida de los datos: retener, archivar y eliminar con evidencia

Conecte cada categoría de datos a un propósito, propietario, activador de retención y proceso de eliminación que realmente se pueda verificar.

Actualizado · 9 min

Escena ficticia sin personas: discos intactos en bandejas, maleta sellada, carpeta burdeos e inventario abstracto para preparar la retirada de soportes Ilustración editorial generada con IA

Lo que esta guía ayuda a lograr

  • Reducir datos sin uso definido
  • Incluir copias de seguridad y exportaciones en reglas de ciclo de vida
  • Retenciones y excepciones de seguimiento
  • Probar eliminación sin volver a exponer el contenido eliminado

Comprobación rápida

  • ¿Qué finalidad justifica aún cada categoría?
  • ¿Dónde existen copias y derivados?
  • ¿Quién puede prorrogar la retención?
  • ¿Cómo se propaga la eliminación?
  • ¿Qué evidencias quedan tras la purga?

Método paso a paso

  1. 1

    Categorías y usos del mapa

    Datos del inventario, finalidades, personas afectadas, sistemas, titulares y flujos. Agrupe por regla operativa en lugar de por nombre de tabla de base de datos.

    Entregable: categoría, uso, sistema y registro de propietarios.

  2. 2

    Definir eventos del ciclo de vida

    Conectar creación, uso activo, cierre, archivo, retención y eliminación a eventos observables. Indique qué norma prevalece cuando las obligaciones entran en conflicto.

    Entregable: matriz de eventos, estados y acciones.

  3. 3

    Incluir todas las copias

    Agregar cachés, exportaciones, entornos de prueba, copias de seguridad, archivos, dispositivos y proveedores. Documente la rapidez con la que se propagan los cambios en el ciclo de vida.

    Entregable: mapa de ubicación y replicación.

  4. 4

    Gestionar excepciones

    Controlar retenciones legales, obligaciones sectoriales y necesidades probatorias con autoridad, alcance, duración y revisión.

    Entregable: registro de excepción fechado.

  5. 5

    Automatizar con control

    Activar archivado y depuración de reglas versionadas. Registre el volumen, los fallos y los reintentos sin conservar el contenido eliminado como prueba.

    Entregable: procedimiento de procesamiento y log.

  6. 6

    Prueba fin de vida

    Muestra de registros que alcanzaron su fecha límite, confirma la ausencia en todos los sistemas y el manejo retrasado de las copias de seguridad, luego soluciona las brechas.

    Entregable: informe de eliminación y plan correctivo.

Ejemplo trabajado ficticio

Situación ilustrativa

Un formulario crea un registro de cliente y varias copias en exportaciones y respaldos. El equipo vincula cada copia con su propósito, evento de inicio y regla de retención documentada.

Decisión y pruebas esperadas

Una muestra de registros caducados comprueba la eliminación, las excepciones justificadas y la propagación a sistemas secundarios sin copiar los datos borrados en el registro.

Indicadores de gestión

IndicadorQué midePrimera acción
CoberturaCategorías conectadas a una regla y propietarioTratar primero los datos huérfanos
Plazos ejecutadosArtículos caducados manejados dentro del tiempo previstoAnalizar colas bloqueadas y excepciones
Copias controladasUbicaciones incluidas en la propagación del ciclo de vidaAgregar exportaciones y copias de seguridad olvidadas
Fallos de purgaAcciones de eliminación fallidas o sin confirmarArreglar y reproducir con evidencia

Errores comunes

  • Establecer una duración sin evento de inicio
  • Olvidar las exportaciones y los entornos de prueba
  • Tratar la copia de seguridad como un archivo permanente
  • Retener datos eliminados dentro de los registros

Preguntas frecuentes

¿Deben eliminarse inmediatamente las copias de seguridad inmutables?

No siempre. Documente su vida útil, evite la reutilización ordinaria y aplique la eliminación cuando la rotación o restauración lo haga posible.

¿Un período puede abarcar todas las categorías de datos?

Rara vez. El propósito, la categoría, la relación, las obligaciones y las necesidades de evidencia pueden requerir diferentes desencadenantes.

¿Cómo se puede acreditar la supresión?

Conservar un identificador técnico, regla aplicada, marca de tiempo, resultado y control sin copiar los datos eliminados en el registro.

Referencias: datos, usos y límites

Documentación consultada el .

Las notas detalladas de esta edición están disponibles en inglés.

Referencias: datos, usos y límites
Fuente y finalidadDato o referencia verificadaCómo utilizarlaLímite que debe conservarse
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.

Profundizar en el método →

Using the framework alone does not determine compliance with applicable law. Processing context and jurisdiction still need examination.

Soportes: saneamiento y pruebas

Las notas detalladas de esta edición están disponibles en inglés.

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

Three methods, with techniques requiring qualification
NIST methodGoal and media condition · synthesisReading limit
ClearLogical 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.
PurgeLogical 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.
DestroyTarget-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

Verify execution, then validate adequacy
LayerQuestionUseful evidence
Verification · §4.5.1Did the technique complete correctly?Status, errors and anomalies; suitable media, residue or equipment inspection according to the technique.
Validation · §4.5.2Is the result adequate for this data and scope?Reasoned acceptance or rejection, considering sensitivity and observed limitations.
Documentation · §4.6Can 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.

Explorar puntos de prueba

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.

Referencias mostradas: 20 / 20.

Explorar puntos de prueba · CIE-SAN · 20
CIE reference and stageCIE review questionCIE evidence to examineNIST locator
CIE-SAN-01

Retention and authority

Preparación

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-02

Data sensitivity

Preparación

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-03

Target data and copies

Preparación

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-04

Reuse and control

Preparación

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-05

Media capabilities

Preparación

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-06

Clear scope

Ejecución

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-07

Flash and non-addressable areas

Preparación

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-08

Purge scope

Ejecución

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-09

Destroy scope

Ejecución

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-10

Encryption history

Borrado criptográfico

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-11

Keys and recoverable copies

Borrado criptográfico

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-12

Cryptographic assurance

Borrado criptográfico

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-13

CE traceability

Trazabilidad

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-14

Logical or cloud storage

Ejecución

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-15

Technical verification

Garantía

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-16

Outcome validation

Garantía

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-17

Anomalies and rework

Garantía

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-18

Identify the operation

Trazabilidad

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-19

Responsibilities and dates

Trazabilidad

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-20

Destination and reconciliation

Trazabilidad

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

Cryptographic erase: four boundaries to document
BoundaryWhat to establishWhat the label alone does not prove
Encrypted dataEncryption 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 hierarchyTarget keys, copies, escrow, injection and dependencies that could enable decryption.Deleting a service credential is not necessarily sanitizing a data-encryption key.
ImplementationQuality of encryption, generation, wrapping and key sanitization, with relevant assurance.An encrypted label establishes neither coverage nor CE effectiveness.
Copies and cloudEncrypted 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

Six educational situations: where evidence may be missing
Fictional situationPremature conclusionReview 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

Referencias oficiales

Las referencias respaldan el método. Adapte los controles a su contexto; no constituyen certificación. Los títulos de referencia originales y los documentos fuente pueden estar en otro idioma.

Referencias consultadas el .