참고 자료 · 13
데이터 수명 주기 관리: 증거를 통한 보존, 보관 및 삭제
모든 데이터 범주를 실제로 검증 가능한 목적, 소유자, 보존 트리거 및 삭제 프로세스에 연결합니다.
업데이트됨 · 20 min
이 가이드가 달성하는 목표
- 용도가 명확하지 않은 데이터 축소
- 수명주기 규칙에 백업 및 내보내기 포함
- 보존 및 예외 추적
- 삭제된 콘텐츠를 다시 노출하지 않고 삭제 입증
빠른 확인
- 각 범주를 정당화하는 목적은 무엇입니까?
- 사본 및 파생물은 어디에 존재합니까?
- 누가 보존 기간을 연장할 수 있습니까?
- 삭제는 어떻게 전파됩니까?
- 삭제 후 어떤 증거가 남아 있습니까?
단계별 방법
- 1
범주 및 사용 사례 매핑
데이터, 목적, 관련 담당자, 시스템, 소유자 및 흐름을 목록화합니다. 데이터베이스 테이블 이름이 아닌 운영 규칙별로 그룹화합니다.
산출물: 범주, 사용 사례, 시스템 및 소유자 등록부
- 2
수명주기 이벤트 정의
생성, 활성 사용, 종료, 보관, 보류 및 삭제를 관찰 가능한 이벤트와 연결합니다. 의무 사항이 충돌할 경우 어떤 규칙이 우선하는지 명시합니다.
산출물: 이벤트, 상태 및 조치 매트릭스
- 3
모든 사본 포함
캐시, 내보내기, 테스트 환경, 백업, 아카이브, 장치 및 공급자 추가. 수명주기 변경 사항이 전파되는 속도를 문서화합니다.
산출물: 위치 및 복제 맵
- 4
예외 관리
권한, 범위, 기간 및 검토를 통해 법적 보류, 부문별 의무 및 증거 요구 사항을 관리합니다.
산출물: 날짜별 예외 등록부
- 5
제어 기능을 통한 자동화
버전 관리 규칙에 따라 아카이브 및 삭제를 트리거합니다. 삭제된 콘텐츠를 증거로 보존하지 않고 볼륨, 실패 및 재시도 기록을 저장합니다.
결과물: 처리 절차 및 로그.
- 6
수명 종료 테스트
만료된 레코드를 샘플링하고, 시스템 전반에 걸쳐 누락된 레코드와 지연된 백업 처리를 확인한 후, 누락된 부분을 수정합니다.
산출물: 삭제 보고서 및 수정 계획
가상 예시
예시 상황
양식을 통해 고객 기록과 내보내기 및 백업에 여러 사본이 생성됩니다. 팀은 각 사본을 목적, 시작 이벤트 및 문서화된 보존 규칙에 연결합니다.
결정 및 예상 증거
만료된 기록 샘플을 사용하여 삭제된 데이터를 로그에 복사하지 않고 삭제, 정당한 예외 및 보조 시스템으로의 전파를 확인합니다.
관리 지표
| 지표 | 측정 대상 | 첫 번째 조치 |
|---|---|---|
| 범위 | 규칙 및 소유자에 연결된 범주 | 고아 데이터 우선 처리 |
| 마감일 실행 | 만료된 항목이 예상 시간 내에 처리됨 | 차단된 큐 및 예외 분석 |
| 복사본 관리 | 수명 주기 전파에 포함된 위치 | 누락된 내보내기 및 백업 추가 |
| 삭제 실패 | 삭제 작업 실패 또는 미확인 | 증거를 사용하여 수정 및 재실행 |
일반적인 실수
- 시작 이벤트 없이 기간 설정
- 내보내기 및 테스트 환경 제외
- 백업을 영구 아카이브로 처리
- 로그에 삭제된 데이터 보존
자주 묻는 질문
변경 불가능한 백업은 즉시 삭제해야 합니까?
항상 그런 것은 아닙니다. 데이터의 수명을 문서화하고, 일반적인 재사용을 방지하며, 순환 또는 복원이 가능한 경우 삭제를 적용합니다.
하나의 기간으로 모든 데이터 범주를 포괄할 수 있습니까?
드물게 가능합니다. 목적, 범주, 관계, 의무 및 증거 요구 사항에 따라 다른 트리거가 필요할 수 있습니다.
삭제를 어떻게 입증할 수 있습니까?
삭제된 데이터를 로그에 복사하지 않고 기술 식별자, 적용된 규칙, 타임스탬프, 결과 및 제어 정보를 유지합니다.
참고 자료: 데이터, 용도와 한계
문서 검토일 .
이 언어판의 상세 참고 설명은 영어로 제공됩니다.
| 출처와 목적 | 확인된 데이터 또는 기준 | 사용 방법 | 유지해야 할 한계 |
|---|---|---|---|
| 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. |
매체: 데이터 제거와 증거
이 언어판의 상세 참고 설명은 영어로 제공됩니다.
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.
증거 검토 항목 탐색
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.
20개 중 20개 항목 표시.
필터와 일치하는 항목이 없습니다.
| CIE reference and stage | CIE review question | CIE evidence to examine | NIST locator |
|---|---|---|---|
CIE-SAN-01Retention and authority 준비 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 준비 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 준비 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 준비 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 준비 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 실행 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 준비 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 실행 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 실행 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 암호학적 삭제 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 암호학적 삭제 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 암호학적 삭제 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 추적성 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 실행 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 보증 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 보증 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 보증 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 추적성 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 추적성 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 추적성 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
공식 참조
참조는 방법을 뒷받침합니다. 상황에 맞게 검사를 조정하십시오. 이는 인증이 아닙니다. 원본 참조 제목 및 소스 문서는 다른 언어로 작성되었을 수 있습니다.
참고 자료 확인일 .
- 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
