リソース · 13

データライフサイクルガバナンス:証拠に基づいた保持、アーカイブ、削除

すべてのデータカテゴリを、実際に検証可能な目的、所有者、保持トリガー、削除プロセスに紐付けてください。

更新済み · 21 min

トレー上の損傷のないドライブ、封印されたケース、えんじ色の書類と抽象的な台帳画面を備えた架空の無人媒体廃止準備台 AIで生成した編集用イラスト

このガイドが達成するのに役立つこと

  • 用途が定義されていないデータを削減する。
  • ライフサイクルルールにバックアップとエクスポートを含める。
  • 保留と例外を追跡する。
  • 削除されたコンテンツを再公開することなく削除を証明する。

クイックチェック

  • 各カテゴリを正当化する目的とは何か?
  • コピーと派生データはどこに存在するのか?
  • 保持期間を延長できるのは誰か?
  • 削除はどのように伝播するのか?
  • パージ後に残る証拠とは何か?

手順

  1. 1

    カテゴリと用途のマッピング

    データ、目的、影響を受けるユーザー、システム、所有者、およびフローをインベントリ化する。 データベーステーブル名ではなく、運用ルールに基づいてグループ化する。

    成果物:カテゴリ、用途、システム、および所有者の登録簿。

  2. 2

    ライフサイクルイベントの定義

    作成、アクティブ使用、クローズ、アーカイブ、保留、および削除を観測可能なイベントに関連付ける。 義務が競合する場合に優先するルールを明記する。

    成果物:イベント、状態、およびアクションのマトリックス。

  3. 3

    すべてのコピーを含める

    キャッシュ、エクスポート、テスト環境、バックアップ、アーカイブ、デバイス、およびプロバイダーを追加する。 ライフサイクル変更が伝播する速度を文書化する。

    成果物:場所とレプリケーションマップ。

  4. 4

    例外の管理

    権限、範囲、期間、およびレビューに基づいて、法的保留、セクターの義務、および証拠要件を管理する。

    成果物:日付付き例外登録簿。

  5. 5

    自動化と制御

    バージョン管理ルールに基づいてアーカイブとパージをトリガーします。 削除されたコンテンツを証拠として保持することなく、ボリューム、障害、再試行をログに記録します。

    成果物:処理​​手順とログ

  6. 6

    サポート終了テスト

    期限を迎えたレコードをサンプルとして抽出し、システム間での欠落とバックアップ処理の遅延を確認し、ギャップを修復します。

    成果物:削除レポートと是正計画

架空の事例

具体的な状況

フォームによって顧客レコードが作成され、エクスポートおよびバックアップに複数のコピーが作成される。 チームは各コピーをその目的、開始イベント、および文書化された保持ルールにリンクする。

決定と期待される証拠

期限切れレコードのサンプルを用いて、削除、正当な例外、およびセカンダリシステムへの伝播を、削除されたデータをログにコピーすることなく確認する。

管理指標

指標測定対象最初のアクション
網羅性ルールと所有者に関連付けられたカテゴリ孤立データを優先的に処理する
期限が守られた期限切れアイテムが想定時間内に処理されたブロックされたキューと例外を分析する
コピーが制御されているライフサイクル伝播に含まれる場所忘れられたエクスポートとバックアップを追加する
パージ失敗削除アクションが失敗または未確認証拠に基づいて修正と再実行を行う

よくある間違い

  • 開始イベントなしで期間を設定する
  • エクスポートとテスト環境を忘れる
  • バックアップを永続アーカイブとして扱う
  • ログ内に削除されたデータを保持する

よくある質問

不変バックアップはすぐに削除する必要があるか?

必ずしもそうではない。 データのライフサイクルを記録し、通常の再利用を防止し、ローテーションまたは復元が可能になった時点で削除を適用する。

1つの期間で全てのデータカテゴリを網羅できるか?

まれである。 目的、カテゴリ、関係性、義務、および証拠の必要性に応じて、異なるトリガーが必要となる場合がある。

削除の証明方法は?

削除されたデータをログにコピーすることなく、技術識別子、適用されたルール、タイムスタンプ、結果、および制御情報を保持する。

参照資料:データ・用途・限界

資料確認日 .

この言語版の詳しい参照メモは英語で提供しています。

参照資料:データ・用途・限界
出典と目的確認済みのデータ・指標利用方法留意する限界
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

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.

証拠の確認項目を探す

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-SAN · 20
CIE reference and stageCIE review questionCIE evidence to examineNIST locator
CIE-SAN-01

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Destination 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

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

公式参照文献

参照文献はメソッドを裏付けるものです。 チェックは状況に合わせて調整してください。 これらは認証ではありません。 元の参照文献のタイトルやソース文書は別の言語で書かれている場合があります。

参照資料の確認日 .